diff --git a/Sky Atlas/Sky Atlas.md b/Sky Atlas/Sky Atlas.md index 5a6c0c3d..8f77a7f9 100644 --- a/Sky Atlas/Sky Atlas.md +++ b/Sky Atlas/Sky Atlas.md @@ -1949,7 +1949,7 @@ During the Probationary Period, a Tier 1 (Procedural) breach (as defined in [A.1 #### A.1.5.1.5 - List Of Recognized Aligned Delegates [Active Data Controller] -The list of currently recognized Aligned Delegates is defined as Active Data in [A.1.5.1.4.0.6.1 - Current Aligned Delegates](5f584db8-f8d8-4118-988c-b2bc3f68ceb7). +The list of currently recognized Aligned Delegates is defined as Active Data in [A.1.5.1.5.0.6.1 - Current Aligned Delegates](5f584db8-f8d8-4118-988c-b2bc3f68ceb7). The Active Data is updated as follows: @@ -2036,7 +2036,7 @@ Each Level 1 Ranked Delegate is eligible for a budget of 400,000 USDS per year. ###### A.1.5.4.1.1.3 - Selection Of Level 1 Ranked Delegates [Core] -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 Current Level 1 Ranked Delegates. +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.5.4.1.1.3.1 - Current Level 1 Ranked Delegates](46c0f334-4421-4e1a-9130-501e3a246e2a). ###### A.1.5.4.1.1.3.1 - Current Level 1 Ranked Delegates [Core] @@ -2050,13 +2050,13 @@ Level 2 Ranked Delegates are eligible for an intermediate budget and are expecte There is one (1) Level 2 Ranked Delegate. -###### A.1.5.4.1.2.2 - Budget For Level 2 Ranked Delegates [Core] +###### A.1.5.4.1.2.2 - Budget For Level 2 Ranked Delegates [Core] Each Level 2 Ranked Delegate is eligible for a budget of 175,000 USDS per year. ###### A.1.5.4.1.2.3 - Selection Of Level 2 Ranked Delegates [Core] -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 Current Level 2 Ranked Delegates. +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.5.4.1.2.3.1 - Current Level 2 Ranked Delegates](ebe4da3b-2674-4ee1-b7a8-3d7a4b37fe75). ###### A.1.5.4.1.2.3.1 - Current Level 2 Ranked Delegates [Core] @@ -2070,7 +2070,7 @@ Level 3 Ranked Delegates are eligible for a lower budget and are expected to con There are three (3) Level 3 Ranked Delegates. -###### A.1.5.4.1.3.2 - Budget For Level 3 Ranked Delegates [Core] +###### A.1.5.4.1.3.2 - Budget For Level 3 Ranked Delegates [Core] Each Level 3 Ranked Delegate is eligible for a budget of 48,000 USDS per year. @@ -2088,25 +2088,25 @@ The budget for Ranked Delegates accrues on a continuous basis. #### A.1.5.4.3 - Budget Contingency [Core] -A Ranked Delegate's allocated budget can be reduced if they do not fully comply with the participation requirements defined in this Article at Voting-Activity Metrics, Voting-Communication Metrics, and Emergency Communications Requirement. +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.5.4.3.1 - Voting-Activity Metrics](ad1ef0f4-246f-4289-b5fc-ea5c91508ccf), [A.1.5.4.3.2 - Voting-Communication Metrics](f020d1bc-8905-46f8-b3a5-c31bcc0eec79), and [A.1.5.4.3.3 - Emergency Communications Requirement](43db9780-6c0a-458a-94c2-5951b5b80787). ##### A.1.5.4.3.1 - Voting-Activity Metrics [Core] 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). -If 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. +If 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. Should 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. -###### A.1.5.4.3.1.0.3.1 - Proportional Linear Scale - Element Annotation [Annotation] +###### A.1.5.4.3.1.0.3.1 - Proportional Linear Scale - Element Annotation [Annotation] -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). +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). ##### A.1.5.4.3.2 - Voting-Communication Metrics [Core] 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). -If 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. +If 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. Should 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. @@ -2124,7 +2124,7 @@ What are the risks of not having explicit criteria for voting-communications? On ###### A.1.5.4.3.2.0.3.1 - Proportional Linear Scale - Element Annotation [Annotation] -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). +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). ###### A.1.5.4.3.2.0.3.2 - Voting-Communication Metrics - Element Annotation [Annotation] @@ -2160,7 +2160,8 @@ This includes calculating: 2. the budget to be deposited into each Aligned Delegate's AD Buffer, which is modified pursuant to voting and communication metrics; 3. the balance of each Delegate's AD Buffer; and 4. the amount to be paid out to each Aligned Delegate. -5. Once calculated by the Core Facilitator, AD payouts are paid from the Aligned Delegates Buffer Multisig. See [A.2.3.1.4.1.2.1 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a). + +Once calculated by the Core Facilitator, AD payouts are paid from the Aligned Delegates Buffer Multisig. See [A.2.3.1.4.1.2.1 - Aligned Delegates Buffer](05fa5c41-26ca-4c25-94dd-834ef72c318a). ###### NR-10 - AD Budget Management [Needed Research] @@ -2168,9 +2169,9 @@ This includes calculating: Are 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? -###### A.1.5.4.4.1.1 - One Month's Budget Allocation [Core] +###### A.1.5.4.4.1.0.3.1 - One Month's Budget Allocation - Element Annotation [Annotation] -To arrive at the value of this one-month budget threshold in USDS, see Levels Of Ranked Delegates. +To arrive at the value of this one-month budget threshold in USDS, see [A.1.5.4.1 - Levels Of Ranked Delegates](f4857d86-f4e7-43c5-be50-fab9e82f0129). ##### A.1.5.4.4.2 - AD Buffer And Loss Of Budget [Core] @@ -2178,12 +2179,16 @@ If an AD is unranked for an entire month, any contents in its AD Buffer can be p ###### A.1.5.4.4.2.1 - Payout Limitations For ADs Triggering Atlas Edit Proposals [Core] -If an AD has triggered an Atlas Edit Weekly Cycle Proposal pursuant to [A.1.10.2.1.3 - Triggering Requirement](cef09d74-efc6-45cc-a75b-1132dae9e743), or [A.1.11.2.1.2 - Triggering Requirement](7bbfd3b1-99b5-4c60-9292-68d776e03886), respectively, no payouts may be made that would reduce their AD Buffer below the [A.1.5.4.4.2.1.1 - Triggering Threshold](2c2b201e-b95f-4852-8e76-6dfe4c3c6a4f) specified in Triggering Threshold until the Proposal has been voted on or rejected by the Core Facilitator for misalignment. +If an AD has triggered an Atlas Edit Weekly Cycle Proposal or Atlas Edit Monthly Cycle Proposal pursuant to [A.1.10.2.1.3 - Triggering Requirement](cef09d74-efc6-45cc-a75b-1132dae9e743), or [A.1.11.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.5.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. ###### A.1.5.4.4.2.1.1 - Triggering Threshold [Core] 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.10.2.1.3 - Triggering Requirement](cef09d74-efc6-45cc-a75b-1132dae9e743) and [A.1.11.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.5.4.1.3.2 - Budget For Level 3 Ranked Delegates](c51b75e1-8390-46c6-b455-3fd1b155af0d). +###### A.1.5.4.4.2.1.1.0.3.1 - One Month's Budget Allocation - Element Annotation [Annotation] + +See [A.1.5.4.4.1.0.3.1 - One Month’s Budget Allocation - Element Annotation](48a2c0f5-5f09-44d3-a930-47e6c12fb901). + ##### A.1.5.4.4.3 - Deduction Of Penalties From AD Buffer [Core] 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. @@ -3581,7 +3586,7 @@ The document uses different levels of Markdown headings to organize its content - 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. -- 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 a Prime spell or changes to market parameters. +- 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. This structured approach ensures that the document is both easy to navigate and comprehensive. @@ -4897,7 +4902,7 @@ The Solana LayerZero Freezer Multisig has a 2/4 signing requirement. ###### A.1.9.4.1.3.1.2.3 - Solana LayerZero Freezer Multisig Signers [Core] -The signers of the Solana LayerZero Freezer Multisig are two (2) addresses controlled by Amatsu and two (2) addresses controlled by Keel. +The signers of the Solana LayerZero Freezer Multisig are two (2) addresses controlled by Operational GovOps Soter Labs and two (2) addresses controlled by Keel. ###### A.1.9.4.1.3.1.2.4 - Solana LayerZero Freezer Multisig Usage Standards [Core] @@ -4909,13 +4914,11 @@ The Core Council must ensure that use of the multisig is generally aligned and s ###### A.1.9.4.1.3.1.2.5 - Solana LayerZero Freezer Multisig Modification [Core] -- Amatsu and Keel can change the signers of the Solana LayerZero Freezer Multisig so long as: - - ◦ there are four (4) signers; - - ◦ two (2) signers are required to execute transactions; and +Operational GovOps Soter Labs and Keel can change the signers of the Solana LayerZero Freezer Multisig so long as: - ◦ an equal number of signers are controlled by Amatsu and Keel. +- there are four (4) signers; +- two (2) signers are required to execute transactions; and +- an equal number of signers are controlled by Operational GovOps Soter Labs and Keel. ###### A.1.9.4.1.3.2 - Rate Limits [Core] @@ -6129,11 +6132,12 @@ Agents are responsible for maintaining their Artifacts in accordance with the Sk ##### A.1.13.2.10.1 - Responsibility To Maintain Agent Artifact [Core] Each Agent is responsible for maintaining its Artifact such that the following requirements are met: - -◦ the Artifact provides clear authorization for all actions taken by the Agent; -◦ the Artifact accurately reflects the current state of the Agent and its operations; -◦ 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.3](https://sky-atlas.powerhouse.io/A.2.2_Sky_Primitives/1b2f2ff0-8d73-8095-bb8f-ed052141f936%7C9e1f)); and -◦ the Artifact is free of significant ambiguities or contradictions. + +- the Artifact provides clear authorization for all actions taken by the Agent; +- the Artifact accurately reflects the current state of the Agent and its operations; +- 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 +- the Artifact is free of significant ambiguities or contradictions. + If the Agent has an Operational Executor Agent then this responsibility is shared by Operational GovOps and the Operational Facilitator. ##### A.1.13.2.10.2 - Review By Core GovOps [Core] @@ -7445,7 +7449,7 @@ The documents herein define the treasury management process. ###### A.2.2.8.1.2.1.4.3.1 - Near-Term Process [Core] -In the near term, Amatsu calculates the Distribution Reward on behalf of the Support Facilitators. The Accessibility Facilitators then pay the Distribution Reward from the Distribution Reward Controller Wallet located on the Ethereum Mainnet at `0x05F471262d15EECA4059DadE070e5BEd509a4e73` within seven (7) days of the end of every month. The balance of this wallet may be topped up to 3 million USDS. This funding is subject to an Executive Vote. +In the near term, Denna Labs calculates the Distribution Reward on behalf of the Support Facilitators. The Accessibility Facilitators then pay the Distribution Reward from the Distribution Reward Controller Wallet located on the Ethereum Mainnet at `0x05F471262d15EECA4059DadE070e5BEd509a4e73` within seven (7) days of the end of every month. The balance of this wallet may be topped up to 3 million USDS. This funding is subject to an Executive Vote. ###### A.2.2.8.1.2.1.4.3.2 - Long Term Process [Core] @@ -7945,9 +7949,7 @@ This process has no dependencies. The process flow for this process is defined herein: - Using the finalized `Atlas Edit Proposal` content, the Operational Facilitator sets up an offchain Snapshot vote. - - Prime Agent token holders vote on the proposal. - - After the voting concludes, the Operational Facilitator records the result of the vote in the Powerhouse system. ###### A.2.2.8.1.2.3.5.3 - Required Primitive Inputs [Core] @@ -7955,31 +7957,28 @@ The process flow for this process is defined herein: The required Primitive Inputs to this process are defined herein. - After Facilitator prepares Snapshot vote: - ◦ Edit `Artifact Edit Proposal` Document - - Updated fields - - Status - ◦ New value: set to `Pending Poll` - - Off-chain Snapshot - ◦ New value: Populate with link to the official Snapshot page - - Responsible party: Operational Facilitator - + - Edit `Artifact Edit Proposal` Document + - Updated fields + - Status + - New value: set to `Pending Poll` + - Off-chain Snapshot + - New value: Populate with link to the official Snapshot page + - Responsible party: Operational Facilitator - 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. - - ◦ Proposal Passes - - Edit `Artifact Edit Proposal` Document - - Update fields - ◦ Status - - New value: set to `Poll Approved` - - Responsible party: Operational Facilitator. - - Trigger - Required Output: Proposal Passes - - ◦ Proposal Fails - - Updated fields - - Edit `Artifact Edit Proposal` Document - ◦ Status - - New value: set to `Poll Rejected` - - Responsible party: Operational Facilitator. - - Trigger - Required Output: Proposal Fails + - Proposal Passes + - Edit `Artifact Edit Proposal` Document + - Update fields + - Status + - New value: set to `Poll Approved` + - Responsible party: Operational Facilitator. + - Trigger - Required Output: Proposal Passes + - Proposal Fails + - Updated fields + - Edit `Artifact Edit Proposal` Document + - Status + - New value: set to `Poll Rejected` + - Responsible party: Operational Facilitator. + - Trigger - Required Output: Proposal Fails ###### A.2.2.8.1.2.3.5.4 - Required Outputs [Core] @@ -7994,24 +7993,22 @@ No Sky Core Atlas documents are updated as the output of this process. The Agent Artifact documents specified herein are updated as the output of this process. The Output "sets" are mutually exclusive. - Proposal Passes - - ◦ Required Primitive Input Trigger: Proposal Passes see A.2.2.8.1.2.3.5.3 - Required Primitive Inputs - ◦ **Edit ****`Primitive Hub Document/In Progress Invocations Directory/Instance Name`** - - Updated fields - - Invocation Status - ◦ New value: set to `Proposal Approved` - - Responsible Party: Operational GovOps - - Trigger - Process: [A.2.2.8.1.2.3.6 - Process Definition For Artifact Update](b3ed1e74-7ec2-4537-8e1d-2098dc17d984) + - Required Primitive Input Trigger: Proposal Passes see [A.2.2.8.1.2.3.5.3 - Required Primitive Inputs](b593ff77-2c46-418d-a7b3-9730437ce804) + - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name` + - Updated fields + - Invocation Status + - New value: set to `Proposal Approved` + - Responsible Party: Operational GovOps + - Trigger - Process: [A.2.2.8.1.2.3.6 - Process Definition For Artifact Update](b3ed1e74-7ec2-4537-8e1d-2098dc17d984) - Proposal Fails - ◦ Required Primitive Input Trigger: Proposal Fails see A.2.2.8.1.2.3.5.3 - Required Primitive Inputs - ◦ **Edit ****`Primitive Hub Document/In Progress Invocations Directory/Instance Name`** - - Updated fields - - Invocation Status - ◦ New value: set to `Proposal Rejected` - - Other Document Operations: - - - `Instance Configuration Document` is `Archived` in Primitive Hub Document/Hub Data Repository - - Responsible Party: Operational GovOps + - Required Primitive Input Trigger: Proposal Fails see [A.2.2.8.1.2.3.5.3 - Required Primitive Inputs](b593ff77-2c46-418d-a7b3-9730437ce804) + - Edit `Primitive Hub Document/In Progress Invocations Directory/Instance Name` + - Updated fields + - Invocation Status + - New value: set to `Proposal Rejected` + - Other Document Operations: + - `Instance Configuration Document` is `Archived` in Primitive Hub Document/Hub Data Repository + - Responsible Party: Operational GovOps ###### A.2.2.8.1.2.3.6 - Process Definition For Artifact Update [Core] @@ -9980,41 +9977,41 @@ A single entity may serve as both the Integrator operating a frontend and the Pr The current eligible recipients for the Core Governance Reward Primitive are specified in the documents herein. -###### A.2.2.10.1.2.1 - Current Eligible Recipients [Core] +###### A.2.2.10.1.2.1 - Current Eligible Recipients [Core] The current eligible recipients for the Core Governance Reward Primitive are: -- 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. +- **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. ##### A.2.2.10.1.3 - Compliance Requirements [Core] Security and information standards for compliant frontends are specified in the documents herein. -###### A.2.2.10.1.3.1 - Security Standards [Core] +###### A.2.2.10.1.3.1 - Security Standards [Core] Specific security standards for compliant frontends will be specified in a future iteration of the Atlas. -###### A.2.2.10.1.3.2 - Information Standards [Core] +###### A.2.2.10.1.3.2 - Information Standards [Core] Specific information and disclosure standards for compliant frontends will be specified in a future iteration of the Atlas. -##### A.2.2.10.1.4 - Distribution Mechanism [Core] +##### A.2.2.10.1.4 - Distribution Mechanism [Core] The documents herein define how the total reward pool is distributed to individual recipients. -###### A.2.2.10.1.4.1 - Integration With Treasury Management Function [Core] +###### A.2.2.10.1.4.1 - Integration With Treasury Management Function [Core] Distributions of Core Governance Rewards are made on a monthly basis as part of the Treasury Management Function. -###### A.2.2.10.1.4.2 - Allocation Based On Staked SKY [Core] +###### A.2.2.10.1.4.2 - Allocation Based On Staked SKY [Core] 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. -###### A.2.2.10.1.4.2.1 - Tracking Via Reward Codes [Core] +###### A.2.2.10.1.4.2.1 - Tracking Via Reward Codes [Core] 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. -###### A.2.2.10.1.4.3 - Distribution Through Prime Agents [Core] +###### A.2.2.10.1.4.3 - Distribution Through Prime Agents [Core] 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. @@ -10373,7 +10370,7 @@ Relevant Ecosystem Actors must take all necessary actions to transfer all funds 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. -###### A.2.3.1.4.1.1.1.6.3 - Follow-Up Actions [Core] +###### A.2.3.1.4.1.1.1.6.4 - Follow-Up Actions [Core] Core GovOps must propose a subsequent Atlas Edit Proposal removing all references to Legacy Accounts from the Atlas and replacing them with the Core Council Buffer. @@ -11400,11 +11397,11 @@ The Grove Token Generation Event will occur on the first date that SKY Staking u 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. -###### A.2.8.2.2.2.8.1.2.1 - Token Launch Penalty Settlement Date [Core] +###### A.2.8.2.2.2.8.1.2.1 - Token Launch Penalty Settlement Date [Core] 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. -###### A.2.8.2.2.2.8.1.2.2 - Token Launch Penalty Settlement Mechanism [Core] +###### A.2.8.2.2.2.8.1.2.2 - Token Launch Penalty Settlement Mechanism [Core] 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. @@ -11671,7 +11668,7 @@ The subdocuments herein record the terms of agreement between Sky and Skybase as ##### A.2.8.2.7.1 - Accord Key Details [Core] -The subdocuments herein set out the key details of Ecosystem Accord 7, such as parties to the agreement and the duration of the Accord. +The subdocuments herein set out the key details of Ecosystem Accord 7, such as parties to the agreement and the duration of the Accord. ###### A.2.8.2.7.1.1 - Parties To The Accord [Core] @@ -11695,7 +11692,7 @@ The subdocuments herein set out the substantive terms of Ecosystem Accord 7. Add ###### A.2.8.2.7.2.1 - Tokenomics [Core] -The subdocuments herein set out agreed terms with respect to tokenomics. +The subdocuments herein set out agreed terms with respect to tokenomics. ###### A.2.8.2.7.2.1.1 - Total Token Supply [Core] @@ -11703,7 +11700,7 @@ The total token supply of SKYBASE will be specified in a future iteration of the ###### A.2.8.2.7.2.1.2 - Token Allocations [Core] -Specific token allocations are defined in the subdocuments herein. +Specific token allocations are defined in the subdocuments herein. ###### A.2.8.2.7.2.1.2.1 - Skybase Prime Treasury [Core] @@ -12626,7 +12623,7 @@ The `retainable` parameter specifies whether the whitehat hacker may retain the ###### A.2.11.1.2.2.3.3 - Chains Parameter [Core] -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 that should be specified are Ethereum Mainnet, Arbitrum, Base, and StarkNet. +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. ###### A.2.11.1.2.2.3.3.1 - Chain IDs [Core] @@ -13464,7 +13461,7 @@ Offchain lending through Anchorage Digital has a CRR of 3%. The maximum exposure The documents herein define the Instance Financial CRR applied to specific Morpho vault allocations. -###### A.3.2.2.1.1.1.1.3.8.1 - Morpho Grove x Steakhouse High Yield USDC Vault [Core] +###### A.3.2.2.1.1.1.1.3.8.1 - Morpho Grove x Steakhouse High Yield USDC Vault [Core] The CRRs for the following market allocations in the vault are: @@ -13477,11 +13474,11 @@ The CRRs for the following market allocations in the vault are: - mF-One / USDC – LLTV: 91.5% - CRR = 100% -###### A.3.2.2.1.1.1.1.3.8.2 - Morpho Grove x Steakhouse High Yield AUSD Vault [Core] +###### A.3.2.2.1.1.1.1.3.8.2 - Morpho Grove x Steakhouse High Yield AUSD Vault [Core] 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. - ###### A.3.2.2.1.1.1.1.3.9 - Uniswap V3 [Core] +###### A.3.2.2.1.1.1.1.3.9 - Uniswap V3 [Core] 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. @@ -14005,10 +14002,10 @@ The documents herein define exceptions to the calculation of Instance Financial ###### A.3.2.2.1.1.1.5.3.1 - Instance Financial CRRs For Specific Assets [Core] The following Instance Financial CRRs apply to specific assets listed: - -- BUIDL, JTRSY on Ethereum Mainnet, and USTB - 0% Instance Financial CRR -- JTRSY on Avalanche - 0.5% Instance Financial CRR -- JAAA on Ethereum Mainnet - 1.6% Instance Financial CRR + +- BUIDL, JTRSY on Ethereum Mainnet, and USTB - 0% Instance Financial CRR +- JTRSY on Avalanche - 0.5% Instance Financial CRR +- JAAA on Ethereum Mainnet - 1.6% Instance Financial CRR - JAAA on Avalanche - 2.1% Instance Financial CRR - STAC on Ethereum Mainnet - 1.6% Instance Financial CRR - GACLO-1 on Ethereum Mainnet - 0.85% Instance Financial CRR @@ -14018,9 +14015,9 @@ The following Instance Financial CRRs apply to specific assets listed: Investments in JTRSY and JAAA on Avalanche are subject to the following additional restrictions: -- The initial deployment of capital into JTRSY and JAAA on Avalanche may not exceed 20 million USDS in total; -- Each additional deployment of capital into JTRSY or JAAA must be approved by the Core Council Risk Advisor; -- 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 +- The initial deployment of capital into JTRSY and JAAA on Avalanche may not exceed 20 million USDS in total; +- Each additional deployment of capital into JTRSY or JAAA must be approved by the Core Council Risk Advisor; +- 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 - Total investments in JTRSY and JAAA on Avalanche may not exceed 250 million USDS. ###### A.3.2.2.1.1.1.5.3.2 - Restrictions On Investments On Plume [Core] @@ -15704,13 +15701,13 @@ The Aggregate Capital Buffer is the sum of (1) the Sky Surplus Buffer (see [A.3. ##### A.3.5.3.1.2 - Aggregate Backstop Capital [Core] -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. +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. ##### A.3.5.3.1.3 - Allocated Genesis Capital [Core] 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. -#### A.3.5.3.2 - Capital Types [Core] +#### A.3.5.3.2 - Capital Targets [Core] The documents herein define capital targets for Sky and processes for achieving those targets over time. @@ -16191,7 +16188,7 @@ The parameters for the Spark Allocator Vault are: ###### A.3.7.1.2.1.2 - ALLOCATOR-BLOOM-A Parameters [Core] -The parameters for the Grove Allocator Vault are: +The parameters for the Grove Allocator Vault are: - `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a). - `line`: controlled by DC-IAM @@ -16202,14 +16199,14 @@ The parameters for the Grove Allocator Vault are: ###### A.3.7.1.2.1.3 - ALLOCATOR-NOVA-A Parameters [Core] -The parameters for the Keel Allocator Vault are: +The parameters for the Keel Allocator Vault are: - `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a). - `line`: 0 USDS ###### A.3.7.1.2.1.4 - ALLOCATOR-OBEX-A Parameters [Core] -The parameters for the Obex Allocator Vault are: +The parameters for the Obex Allocator Vault are: - `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a). - `line`: controlled by DC-IAM @@ -16220,7 +16217,7 @@ The parameters for the Obex Allocator Vault are: ###### A.3.7.1.2.1.5 - ALLOCATOR-PATTERN-A Parameters [Core] -The parameters for the Pattern Allocator Vault are: +The parameters for the Pattern Allocator Vault are: - `duty`: set by the SP-BEAM specified in [A.3.7.1.3 - Stability Parameter Bounded External Access Module](47b8b035-8abd-42e6-86b8-33f852fa953a). - `line`: controlled by DC-IAM @@ -16231,7 +16228,7 @@ The parameters for the Pattern Allocator Vault are: ##### A.3.7.1.2.2 - Update Process [Core] -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 Prime Allocator Vault Risk Parameters. 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. +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. #### A.3.7.1.3 - Stability Parameter Bounded External Access Module [Core] @@ -16377,7 +16374,7 @@ The Stability Parameter Bounded External Access Module parameters for the ALLOCA - `max` - 3,000 basis points, - `min` - 0 basis points, - `step` - 400 basis points, -- `tau` - Globally defined in [A.3.7.1.2.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b). +- `tau` - Globally defined in [A.3.7.1.3.1.4.1 - Tau Current Value](dd9472e5-9796-4aff-a2b1-7a847e008c9b). ##### A.3.7.1.3.4 - Parameter Adjustments [Core] @@ -16581,10 +16578,10 @@ The Genesis Capital Backstop may not be invoked unless a "SKY Backstop Event" is ##### A.3.7.1.6.5 - Genesis Agents [Core] Genesis Agents are Agents that receive capital contributions from Sky, including, without limitation: - -- Spark -- Grove -- Keel + +- Spark +- Grove +- Keel - Skybase - Obex - Core Council Executor Agent 1 @@ -17068,21 +17065,21 @@ The parameters of the SKY Borrow Minimum Rate formula are further defined in the The liquidation parameters for SKY-backed loans funded via stUSDS are: -◦ Liquidation Ratio: 120% -◦ `Calc`: StairstepExponentialDecrease -◦ `Tau`: 0 days -◦ `Tolerance`: 0.5 -◦ `Cut`: 0.99 -◦ `Step`: 60 seconds -◦ `Buf`: 120% -◦ `Cusp`: 40% -◦ `Tail`: 6,000 seconds -◦ `Chip`: 0.1% -◦ `Stopped`: 3 -◦ `Tip`: 300 USDS -◦ `Chop`: 13% -◦ `Hole`: 250,000 -◦ `Dust`: 30,000 +- Liquidation Ratio: 120% +- `Calc`: StairstepExponentialDecrease +- `Tau`: 0 days +- `Tolerance`: 0.5 +- `Cut`: 0.99 +- `Step`: 60 seconds +- `Buf`: 120% +- `Cusp`: 40% +- `Tail`: 6,000 seconds +- `Chip`: 0.1% +- `Stopped`: 3 +- `Tip`: 300 USDS +- `Chop`: 13% +- `Hole`: 250,000 +- `Dust`: 30,000 ###### A.4.4.1.3.6.1 - Modification Of stUSDS Risk Parameters [Core] @@ -18130,7 +18127,7 @@ The documents herein define the parameters of the Amatsu Instance of the Executo ###### A.6.1.1.1.2.2.1.2.1.1.1 - Operational Executor Agent [Core] -In the near term Amatsu will take on the functions of an Operational Executor Agent, including both Operational GovOps and Operational Facilitator roles. +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). ###### A.6.1.1.1.2.2.1.2.1.1.2 - Custom Instance Parameters [Core] @@ -19879,7 +19876,7 @@ Ecosystem Actor Phoenix Labs can change the signers of the Prime Relayer Multisi ###### A.6.1.1.1.2.6.1.2.1.2.2.2 - Core Operator Relayer Multisig [Core] -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 Amatsu 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). +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). ###### A.6.1.1.1.2.6.1.2.1.2.2.2.1 - Address [Core] @@ -19893,7 +19890,7 @@ The Core Operator Relayer Multisig currently has a 2/5 signing requirement. The Core Operator Relayer Multisig comprises the following signers: -- Amatsu: 2 signers +- Operational GovOps Soter Labs: 2 signers - Spark Assets Foundation (SAF): 2 signers - Phoenix Labs (PL): 1 signer @@ -19905,7 +19902,7 @@ The signers of the Core Operator Relayer Multisig must use the multisig to exerc ###### A.6.1.1.1.2.6.1.2.1.2.2.2.5 - Modification [Core] -Ecosystem Actor Amatsu 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. +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. ###### A.6.1.1.1.2.6.1.2.1.2.2.3 - Freezer Multisig [Core] @@ -19929,7 +19926,7 @@ The Freezer Multisig has the following signers: ###### A.6.1.1.1.2.6.1.2.1.2.2.3.4 - Usage Standards [Core] -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 Ecosystem Actor Amatsu 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. Ecosystem Actor Amatsu may also ask the signers to exercise the Freezer Multisig in an emergency. The signers will work with Amatsu and, if necessary, other Ecosystem Actors, in good faith in determining whether to exercise their authority based on such request. +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. Each 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. @@ -23069,9 +23066,10 @@ The outflow rate limits are: ###### A.6.1.1.1.2.6.1.3.1.7.5.2.4.3 - Swap Rate Limits [Core] The swap rate limits are: + - `maxAmount`: 100 - `slope`: 1,000 per day -- Max slippage: 0.25% +- `Max slippage`: 0.25% ###### A.6.1.1.1.2.6.1.3.1.7.5.2.5 - Off-chain Operational Parameters [Core] @@ -28013,7 +28011,7 @@ The subdocuments herein define parameters used to specify loan terms. ###### A.6.1.1.1.3.8.2.4.1.1 - Duration [Core] -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. +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. ###### A.6.1.1.1.3.8.2.4.1.2 - Borrow Rate [Core] @@ -28464,15 +28462,15 @@ The Genesis Supply was minted to an account owned by the Grove Foundation. The a ###### A.6.1.1.2.2.1.4.2.1.2.2 - Transfer Of Tokens To Sky [Core] -The Grove Foundation transferred 7 billion GROVE tokens from the Grove Foundation account, specified in Minting Of Tokens To Grove Foundation, to the Sky Pause Proxy. +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. ###### A.6.1.1.2.2.1.4.2.1.2.3 - Transfer Of Tokens To Grove [Core] -The Grove Foundation transferred 3 billion GROVE tokens from the Grove Foundation account, specified in [Minting Of Tokens To Grove Foundation](a9bae1cc-2a92-4465-b7cf-9f97121f7aa7), to the Grove SubProxy. +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. ###### A.6.1.1.2.2.1.4.2.1.2.4 - Transfer Of Tokens To Grove Labs [Core] - 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`. +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`. ###### A.6.1.1.2.2.1.4.2.1.3 - Data Repository [Core] @@ -28560,7 +28558,7 @@ The documents herein define the parameters of the Amatsu Instance of the Executo ###### A.6.1.1.2.2.2.1.2.1.1.1 - Operational Executor Agent [Core] -In the near term Amatsu will take on the functions of an Operational Executor Agent, including both Operational GovOps and Operational Facilitator roles. +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). ###### A.6.1.1.2.2.2.1.2.1.1.2 - Custom Instance Parameters [Core] @@ -29396,15 +29394,15 @@ This Instance’s associated Instance Configuration Document is located at [A.6. ###### A.6.1.1.2.2.6.1.1.2.1.6.3 - Ethereum Mainnet - Curve AUSD/USDC Swaps Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Curve AUSD/USDC Swaps Instance Configuration Document](207cc62c-29ee-4a03-afd9-37f279b2c25b). +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). ###### A.6.1.1.2.2.6.1.1.2.1.6.4 - Ethereum Mainnet - Curve AUSD/USDC LP Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Curve AUSD/USDC LP Instance Configuration Document](6d7f468e-e32c-4077-8dbc-66095e7b8f84). +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). ###### A.6.1.1.2.2.6.1.1.2.1.6.5 - Ethereum Mainnet - Curve PYUSD/USDS Swaps Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Curve PYUSD/USDS Swaps Instance Configuration Document](f168c4a8-f526-471e-8410-4f3f339e99d5). +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). ###### A.6.1.1.2.2.6.1.1.2.1.7 - Morpho [Core] @@ -29416,19 +29414,19 @@ This Instance's associated Instance Configuration Document is located at [A.6.1. ###### A.6.1.1.2.2.6.1.1.2.1.7.2 - Ethereum Mainnet - Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Monad Morpho Grove x Steakhouse High Yield Vault AUSD Instance Configuration Document](27f06e65-8397-449a-b002-abaa0416badc). +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). -###### A.6.1.1.2.2.6.1.1.2.1.7.3 - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document Location [Core] +###### A.6.1.1.2.2.6.1.1.2.1.7.3 - Ethereum Mainnet - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Grove x Steakhouse USDC Morpho Vault v2 Instance Configuration Document](6ec606f0-bc47-4f36-8591-75784bb78b00). +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). -###### A.6.1.1.2.2.6.1.1.2.1.7.4 - Steakhouse PYUSD Morpho Vault Instance Configuration Document Location [Core] +###### A.6.1.1.2.2.6.1.1.2.1.7.4 - Ethereum Mainnet - Steakhouse PYUSD Morpho Vault Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Steakhouse PYUSD Morpho Vault Instance Configuration Document](0b7e1d3d-1f56-48a6-9729-88479aa5ff92). +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). ###### A.6.1.1.2.2.6.1.1.2.1.7.5 - Ethereum Mainnet - Grove x Steakhouse AUSD Morpho Vault V2 Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Grove x Steakhouse AUSD Morpho Vault V2 Instance Configuration Document](2c21462b-2925-48d8-9578-5fc21aa96563). +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). ###### A.6.1.1.2.2.6.1.1.2.1.8 - Securitize [Core] @@ -29444,9 +29442,9 @@ The Ethereum Mainnet Instances Directory of the Galaxy Protocol with `Active` St ###### A.6.1.1.2.2.6.1.1.2.1.9.1 - Ethereum Mainnet - Galaxy Arch CLOs Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Galaxy Arch CLOs Instance Configuration Document](61afae62-1210-4d80-aa6c-cdb26ef0a287). +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). -###### A.6.1.1.2.2.6.1.1.2.1.9.2 - Ethereum Mainnet - Ethereum Mainnet - Galaxy Warehouse Instance Configuration Document Location [Core] +###### A.6.1.1.2.2.6.1.1.2.1.9.2 - Ethereum Mainnet - Galaxy Warehouse Instance Configuration Document Location [Core] 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). @@ -29456,7 +29454,7 @@ The Ethereum Mainnet Instances Directory of the Ripple Protocol with `Active` St ###### A.6.1.1.2.2.6.1.1.2.1.10.1 - Ethereum Mainnet - Ripple RLUSD Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Ripple RLUSD Instance Configuration Document](2e28c162-c608-452c-b796-4654ac1139d8). +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). ###### A.6.1.1.2.2.6.1.1.2.1.11 - Agora [Core] @@ -29464,7 +29462,7 @@ The Ethereum Mainnet Instances Directory of the Agora Protocol with `Active` Sta ###### A.6.1.1.2.2.6.1.1.2.1.11.1 - Ethereum Mainnet - Agora AUSD Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Agora AUSD Instance Configuration Document](0d71b879-0dd7-4c37-9a42-f16d868c4482). +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). ###### A.6.1.1.2.2.6.1.1.2.1.12 - Uniswap [Core] @@ -29472,15 +29470,15 @@ The Ethereum Mainnet Instances Directory of the Uniswap Protocol with `Active` S ###### A.6.1.1.2.2.6.1.1.2.1.12.1 - Ethereum Mainnet - Monad Uniswap AUSD/USDC Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Monad Uniswap AUSD/USDC Instance Configuration Document](c4d60460-2694-4d88-bf96-4f4141482cb5). +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). ###### A.6.1.1.2.2.6.1.1.2.1.12.2 - Ethereum Mainnet - Uniswap v3 AUSD/USDC Swaps Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [Ethereum Mainnet - Uniswap v3 AUSD/USDC Swaps Instance Configuration Document](ffa0ca69-c416-4163-a1c6-b863f5d38c3f). +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). ###### A.6.1.1.2.2.6.1.1.2.1.12.3 - Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document](cca4236a-47f9-4b4f-81ef-c31a5ee624aa). +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). ###### A.6.1.1.2.2.6.1.1.2.2 - Avalanche [Core] @@ -29608,9 +29606,9 @@ The address of the Grove receiver on Base is: `0x5F5cfCB8a463868E37Ab27B5eFF3ba0 ###### A.6.1.1.2.2.6.1.2.1.1.1.1.2.3 - Circle CCTP v2 Mainnet To Base [Core] - The contract address of the Circle CCTP v2 Mainnet to Base is: `0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d`. +The contract address of the Circle CCTP v2 Mainnet to Base is: `0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d`. - ###### A.6.1.1.2.2.6.1.2.1.1.1.1.2.4 - Circle CCTP v2 Base To Mainnet [Core] +###### A.6.1.1.2.2.6.1.2.1.1.1.1.2.4 - Circle CCTP v2 Base To Mainnet [Core] The contract address of the Circle CCTP v2 Base to Mainnet is: `0x28b5a0e9C621a5BadaA536219b3a228C8168cf5d`. @@ -29872,7 +29870,7 @@ The documents herein list general on-chain parameters for the Grove Liquidity La ###### A.6.1.1.2.2.6.1.2.1.1.4.1 - Allocator Vault Parameters [Core] -The Allocator Vault parameters for ALLOCATOR-BLOOM-A are defined in [ALLOCATOR-BLOOM-A Parameters](53cba245-68c6-4af9-a280-b200dabebec7). +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). ###### A.6.1.1.2.2.6.1.2.1.2 - Governance Processes [Core] @@ -29936,7 +29934,7 @@ Grove can change the signers of the Prime Secondary Relayer Multisig at any time ###### A.6.1.1.2.2.6.1.2.1.2.2.3 - Core Operator Relayer Multisig [Core] -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 Amatsu. +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. ###### A.6.1.1.2.2.6.1.2.1.2.2.3.1 - Address [Core] @@ -29948,7 +29946,7 @@ The Core Operator Relayer Multisig currently has a 2/3 signing requirement. ###### A.6.1.1.2.2.6.1.2.1.2.2.3.3 - Signers [Core] -The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Amatsu. +The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs. ###### A.6.1.1.2.2.6.1.2.1.2.2.3.4 - Usage Standards [Core] @@ -29956,7 +29954,7 @@ The signers of the Core Operator Relayer Multisig must use the Multisig to exerc ###### A.6.1.1.2.2.6.1.2.1.2.2.3.5 - Modification [Core] -Operational GovOps Amatsu 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. +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. ###### A.6.1.1.2.2.6.1.2.1.2.2.4 - Freezer Multisig [Core] @@ -29972,7 +29970,7 @@ The Freezer Multisig currently has a 2/5 signing requirement. ###### A.6.1.1.2.2.6.1.2.1.2.2.4.3 - Signers [Core] -The signers of the Freezer Multisig are two (2) addresses controlled by Operational GovOps Amatsu, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Grove. +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. ###### A.6.1.1.2.2.6.1.2.1.2.2.4.4 - Usage Standards [Core] @@ -29998,7 +29996,7 @@ Grove Development Company will operate the Grove Liquidity Layer and agrees to s ###### A.6.1.1.2.2.6.1.2.1.3.2 - Grove Development Company’s Total Risk Capital (TRC) Management Processes [Core] -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. +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. ###### A.6.1.1.2.2.6.1.2.2 - Grove Liquidity Layer Operational Processes [Core] @@ -32095,7 +32093,7 @@ The documents herein define the Instance identifiers. Ethereum Mainnet -###### A.6.1.1.2.2.6.1.3.1.6.4.2.1.2 - Target Protocol +###### A.6.1.1.2.2.6.1.3.1.6.4.2.1.2 - Target Protocol [Core] Curve AUSD/USDC @@ -32160,11 +32158,11 @@ The swap rate limits are: - `slope`: 100,000,000 USDC/AUSD per day - `maxSlippage`: 0.1% -###### A.6.1.1.2.2.6.1.3.1.6.4.2.4.4 - Off-chain Operational Parameters [Core] +###### A.6.1.1.2.2.6.1.3.1.6.4.2.5 - Off-chain Operational Parameters [Core] The documents herein contain specific off-chain parameters for this Instance. -###### A.6.1.1.2.2.6.1.3.1.6.4.3 - Instance-specific Operational Parameters [Core] +###### A.6.1.1.2.2.6.1.3.1.6.4.3 - Instance-specific Operational Processes [Core] 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. @@ -32230,7 +32228,7 @@ The outflow RateLimitID is: `0x8b0ebe103264ec6caf8c9a6b03eeb13f101d3d1ece1fe8b70 ###### A.6.1.1.2.2.6.1.3.1.6.5.2.4 - Rate Limits [Core] -The current `maxAmount` and `slope` for this conduit’s inflow and outflow are defined in the subdocuments herein. +The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein. ###### A.6.1.1.2.2.6.1.3.1.6.5.2.4.1 - Deposit Rate Limits [Core] @@ -32580,7 +32578,7 @@ The deposit rate limits are: - `maxAmount`: 20,000,000 USDC - `slope`: 20,000,000 USDC per day -###### A.6.1.1.2.2.6.1.3.1.7.3.2.4.2 - Withdrawl Rate Limits [Core] +###### A.6.1.1.2.2.6.1.3.1.7.3.2.4.2 - Withdrawal Rate Limits [Core] The withdrawal rate limits are: @@ -32770,7 +32768,7 @@ The documents herein contain operational procedures or monitoring requirements u ###### A.6.1.1.2.2.6.1.3.1.7.5.4 - Instance-specific Operational Parameters [Core] -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. +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. ###### A.6.1.1.2.2.6.1.3.1.7.5.4.1 - Max Exchange Rate [Core] @@ -32929,7 +32927,7 @@ The outflow RateLimitID is: N/A. ###### A.6.1.1.2.2.6.1.3.1.9.1.2.4 - Rate Limits [Core] -The current maxAmount and slope for this conduit’s inflow and outflow are defined in the subdocuments herein. +The current `maxAmount` and `slope` for this conduit's inflow and outflow are defined in the subdocuments herein. ###### A.6.1.1.2.2.6.1.3.1.9.1.2.4.1 - Deposit Rate Limits [Core] @@ -32938,7 +32936,7 @@ The deposit rate limits are: - `maxAmount`: 50,000,000 USDC - `slope`: 50,000,000 USDC per day -###### A.6.1.1.2.2.6.1.3.1.9.1.2.4.1 - Withdrawal Rate Limits [Core] +###### A.6.1.1.2.2.6.1.3.1.9.1.2.4.2 - Withdrawal Rate Limits [Core] The withdrawal rate limits are: @@ -33090,7 +33088,7 @@ The documents herein define the Instance contract addresses. `0x8292Bb45bf1Ee4d140127049757C2E0fF06317eD` -###### A.6.1.1.2.2.6.1.3.1.10.1.2.2.2 - Underlying Asset Address [Core] +###### A.6.1.1.2.2.6.1.3.1.10.1.2.2.2 - Underlying Asset Address [Core] `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` @@ -33100,11 +33098,15 @@ The specific `RateLimitID`(s) for this conduit’s inflow and outflow are define ###### A.6.1.1.2.2.6.1.3.1.10.1.2.3.1 - Inflow RateLimitID [Core] -The inflow RateLimitID is: `0x1fd0baaf4707a3525f15888ddf89e29b1a008d0f3cf7fb75171233c72003a588`. +The inflow RateLimitID is: + +`0x1fd0baaf4707a3525f15888ddf89e29b1a008d0f3cf7fb75171233c72003a588`. ###### A.6.1.1.2.2.6.1.3.1.10.1.2.3.2 - Outflow RateLimitID [Core] -The outflow RateLimitID is: `0x786ff17c8a3c0f645317f91a3247bc843ba1ee4d248ab539acec8ba3bf4557ae`. +The outflow RateLimitID is: + +`0x786ff17c8a3c0f645317f91a3247bc843ba1ee4d248ab539acec8ba3bf4557ae`. ###### A.6.1.1.2.2.6.1.3.1.10.1.2.4 - Rate Limits [Core] @@ -33176,7 +33178,7 @@ The documents herein define the Instance contract addresses. `0x00000000eFE302BEAA2b3e6e1b18d08D69a9012a` -###### A.6.1.1.2.2.6.1.3.1.11.1.2.2.2 - Underlying Asset Address [Core] +###### A.6.1.1.2.2.6.1.3.1.11.1.2.2.2 - Underlying Asset Address [Core] `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` @@ -33184,7 +33186,7 @@ The documents herein define the Instance contract addresses. `0x748b66a6b3666311F370218Bc2819c0bEe13677e` -###### A.6.1.1.2.2.6.1.3.1.11.1.2.2.4 - Withdrawl Address [Core] +###### A.6.1.1.2.2.6.1.3.1.11.1.2.2.4 - Withdrawal Address [Core] `0xab8306d9FeFBE8183c3C59cA897A2E0Eb5beFE67` @@ -33280,7 +33282,9 @@ The specific `RateLimitID`(s) for this conduit’s inflow and outflow are define ###### A.6.1.1.2.2.6.1.3.1.12.1.2.3.1 - Inflow RateLimitID [Core] -The inflow RateLimitID is: `0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`. +The inflow RateLimitID is: + +`0x098ad67dc41c1a5892ec3ef5fd411198dc11962475e9ef2e0362e6cb7f5a2174`. ###### A.6.1.1.2.2.6.1.3.1.12.1.2.3.2 - Outflow RateLimitID [Core] @@ -33397,13 +33401,13 @@ The swap rate limits are: - `slope`: 100,000,000 AUSD/USDC per day - `maxSlippage`: 0.1% -###### A.6.1.1.2.2.6.1.3.1.12.2.2.4.4 - Off-chain Operational Parameters [Core] +###### A.6.1.1.2.2.6.1.3.1.12.2.2.5 - Off-chain Operational Parameters [Core] The documents herein contain specific off-chain parameters for this Instance. ###### A.6.1.1.2.2.6.1.3.1.12.2.3 - Instance-specific Operational Processes [Core] -The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes. +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. ###### A.6.1.1.2.2.6.1.3.1.12.2.4 - Instance-specific Operational Parameters [Core] @@ -33411,10 +33415,10 @@ The documents herein contain operational parameters or configuration details uni ###### A.6.1.1.2.2.6.1.3.1.12.2.4.1 - Parameters For Stable Stable Pools [Core] -- twapSecondsAgo: 600 -- maxTickDelta: 200 -- lowerTickBound: -10 -- upperTickBound: +10 +- `twapSecondsAgo`: 600 +- `maxTickDelta`: 200 +- `lowerTickBound`: -10 +- `upperTickBound`: +10 ###### A.6.1.1.2.2.6.1.3.1.12.3 - Ethereum Mainnet - Uniswap v3 AUSD/USDC LP Instance Configuration Document [Core] @@ -33507,7 +33511,7 @@ The documents herein contain specific off-chain parameters for this Instance. ###### A.6.1.1.2.2.6.1.3.1.12.3.3 - Instance-specific Operational Processes [Core] -The documents herein contain operational parameters or configuration details unique to this Instance that deviate from or otherwise supplement the general Grove Liquidity Layer processes. +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. ###### A.6.1.1.2.2.6.1.3.1.12.3.4 - Instance-specific Operational Parameters [Core] @@ -33515,10 +33519,10 @@ The documents herein contain operational parameters or configuration details uni ###### A.6.1.1.2.2.6.1.3.1.12.3.4.1 - Parameters For Stable Stable Pools [Core] -- twapSecondsAgo: 600 -- maxTickDelta: 200 -- lowerTickBound: -10 -- upperTickBound: +10 +- `twapSecondsAgo`: 600 +- `maxTickDelta`: 200 +- `lowerTickBound`: -10 +- `upperTickBound`: +10 ###### A.6.1.1.2.2.6.1.3.2 - Avalanche Instances [Core] @@ -34685,7 +34689,7 @@ The documents herein define the parameters of the Amatsu Instance of the Executo ###### A.6.1.1.3.2.2.1.2.1.1.1 - Operational Executor Agent [Core] -In the near term Amatsu will take on the functions of an Operational Executor Agent, including both Operational GovOps and Operational Facilitator roles. +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). ###### A.6.1.1.3.2.2.1.2.1.1.2 - Custom Instance Parameters [Core] @@ -36315,7 +36319,7 @@ The documents herein list general on-chain parameters for the Keel Liquidity Lay ###### A.6.1.1.3.2.6.1.2.1.1.4.1 - Allocator Vault Parameters [Core] -The Allocator Vault parameters for ALLOCATOR-NOVA-A are defined in [ALLOCATOR-NOVA-A Parameters](08321783-f31a-4a80-8f0c-898afb4d8f9b). +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). ###### A.6.1.1.3.2.6.1.2.1.1.4.2 - Whitelisting Of ALMProxy [Core] @@ -36375,7 +36379,7 @@ The Core Operator Relayer Multisig currently has a 2/3 signing requirement. ###### A.6.1.1.3.2.6.1.2.1.2.2.2.3 - Signers [Core] -The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Amatsu. +The signers of the Core Operator Relayer Multisig are three (3) addresses controlled by Operational GovOps Soter Labs. ###### A.6.1.1.3.2.6.1.2.1.2.2.2.4 - Usage Standards [Core] @@ -36383,7 +36387,7 @@ The signers of the Core Operator Relayer Multisig must use the Multisig to exerc ###### A.6.1.1.3.2.6.1.2.1.2.2.2.5 - Modification [Core] -Operational GovOps Amatsu 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. +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. ###### A.6.1.1.3.2.6.1.2.1.2.2.3 - Freezer Multisig [Core] @@ -36399,7 +36403,7 @@ The Freezer Multisig currently has a 2/5 signing requirement. ###### A.6.1.1.3.2.6.1.2.1.2.2.3.3 - Signers [Core] - The signers of the Freezer Multisig are two (2) addresses controlled by Operational GovOps Amatsu, two (2) addresses controlled by Operational Facilitator Endgame Edge, and one (1) address controlled by Keel. +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. ###### A.6.1.1.3.2.6.1.2.1.2.2.3.4 - Usage Standards [Core] @@ -36539,7 +36543,7 @@ Keel will operate the Keel Liquidity Layer and agrees to stay at or below a 90% ###### A.6.1.1.3.2.6.1.2.1.3.2 - Keel’s Total Risk Capital (TRC) Management Processes [Core] -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. +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. ###### A.6.1.1.3.2.6.1.2.2 - Keel Liquidity Layer Operational Processes [Core] @@ -38243,7 +38247,7 @@ Keel engaged in terms of agreement with Sky in Ecosystem Accord 3, located in [A #### A.6.1.1.4 - Skybase [Core] -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. +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. ##### A.6.1.1.4.1 - Introduction [Core] @@ -38259,11 +38263,11 @@ The documents herein implement the Genesis Primitives for Skybase. See [A.2.2.4 ###### A.6.1.1.4.2.1.1 - Agent Creation Primitive [Core] -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). +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). ###### A.6.1.1.4.2.1.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Agent Creation Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Agent Creation Primitive. ###### A.6.1.1.4.2.1.1.1.1 - Global Activation Status [Core] @@ -38323,11 +38327,11 @@ The name of the Agent is Skybase. ###### A.6.1.1.4.2.1.1.3.1.1.2 - SubProxy Account [Core] -The address of Skybase’s SubProxy Account on the Ethereum Mainnet is `0x08978E3700859E476201c1D7438B3427e3C81140`. +The address of Skybase's SubProxy Account on the Ethereum Mainnet is `0x08978E3700859E476201c1D7438B3427e3C81140`. ###### A.6.1.1.4.2.1.1.3.1.1.3 - StarGuard Contract [Core] -The address of Skybase’s StarGuard contract on the Ethereum Mainnet is `0xA170086AeF9b3b81dD73897A0dF56B55e4C2a1F7`. +The address of Skybase's StarGuard contract on the Ethereum Mainnet is `0xA170086AeF9b3b81dD73897A0dF56B55e4C2a1F7`. ###### A.6.1.1.4.2.1.1.3.1.1.3.1 - StarGuard Max Delay [Core] @@ -38335,7 +38339,7 @@ The Skybase StarGuard `maxDelay` is seven (7) days. ###### A.6.1.1.4.2.1.1.3.1.1.4 - Genesis Account [Core] -The address of Skybase’s Genesis Account will be specified in a future iteration of the Skybase Artifact. +The address of Skybase's Genesis Account will be specified in a future iteration of the Skybase Artifact. ###### A.6.1.1.4.2.1.1.3.1.1.5 - Custom Instance Parameters [Core] @@ -38347,7 +38351,7 @@ The Skybase Foundation is the Prime Foundation associated with Skybase. Its mand ###### A.6.1.1.4.2.1.1.3.1.1.5.2 - Development Company [Core] -Skybase’s Development Company will be updated in a future iteration of the Artifact. +Skybase's Development Company will be updated in a future iteration of the Artifact. ###### A.6.1.1.4.2.1.1.3.1.2 - Operational Process Definition [Core] @@ -38375,11 +38379,11 @@ Because the Agent Creation Primitive is deployed solely for the one-time creatio ###### A.6.1.1.4.2.1.2 - Prime Transformation Primitive [Core] -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). +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). ###### A.6.1.1.4.2.1.2.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Prime Transformation Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Prime Transformation Primitive. ###### A.6.1.1.4.2.1.2.1.1 - Global Activation Status [Core] @@ -38467,11 +38471,11 @@ Because the Prime Transformation Primitive is deployed solely for the one-time t ###### A.6.1.1.4.2.1.3 - Executor Transformation Primitive [Core] -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). +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). ###### A.6.1.1.4.2.1.3.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Executor Transformation Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Executor Transformation Primitive. ###### A.6.1.1.4.2.1.3.1.1 - Global Activation Status [Core] @@ -38519,11 +38523,11 @@ Because the Executor Transformation Primitive is deployed solely for the one-tim ###### A.6.1.1.4.2.1.4 - Agent Token Primitive [Core] -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). +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). ###### A.6.1.1.4.2.1.4.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Agent Token Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Agent Token Primitive. ###### A.6.1.1.4.2.1.4.1.1 - Global Activation Status [Core] @@ -38575,11 +38579,11 @@ The documents herein define the parameters of the Single Instance of the Agent T ###### A.6.1.1.4.2.1.4.2.1.1.1 - Token Name [Core] -The name of Skybase’s token is Skybase. +The name of Skybase's token is Skybase. ###### A.6.1.1.4.2.1.4.2.1.1.2 - Token Symbol [Core] -The symbol of Skybase’s token is SKYBASE. +The symbol of Skybase's token is SKYBASE. ###### A.6.1.1.4.2.1.4.2.1.1.3 - Genesis Supply [Core] @@ -38637,11 +38641,11 @@ The documents herein implement the Operational Primitives for Skybase. See [A.2. ###### A.6.1.1.4.2.2.1 - Executor Accord Primitive [Core] -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). +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). ###### A.6.1.1.4.2.2.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Executor Accord Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Executor Accord Primitive. ###### A.6.1.1.4.2.2.1.1.1 - Global Activation Status [Core] @@ -38729,11 +38733,11 @@ The in progress Invocations of the Executor Accord Primitive are contained herei ###### A.6.1.1.4.2.2.2 - Root Edit Primitive [Core] -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). +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). ###### A.6.1.1.4.2.2.2.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Root Edit Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Root Edit Primitive. ###### A.6.1.1.4.2.2.2.1.1 - Global Activation Status [Core] @@ -38793,7 +38797,7 @@ The documents herein define the process for using the Root Edit Primitive to upd ###### A.6.1.1.4.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] -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. +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. ###### A.6.1.1.4.2.2.2.2.1.2.1.1.1 - Root Edit Proposal Submission Requirements Exception [Core] @@ -38801,7 +38805,7 @@ For proposals that solely entail a buyback or a grant of SKYBASE tokens, the req ###### A.6.1.1.4.2.2.2.2.1.2.1.1.2 - Short-Term Transitionary Measures [Core] -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). +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). ###### A.6.1.1.4.2.2.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] @@ -38841,7 +38845,7 @@ The documents herein define the process for using the Root Edit Primitive to upd ###### A.6.1.1.4.2.2.2.2.1.2.3.1 - Root Edit Voting Process in Urgent and Emergency Situations [Core] -In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.8.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. +In an Urgent or Emergency Situation, as defined by the Sky Core Atlas in [A.1.8.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. ###### A.6.1.1.4.2.2.2.2.1.3 - Data Repository [Core] @@ -38869,11 +38873,11 @@ Because the Root Edit Primitive is deployed only once, no further Instances of t ###### A.6.1.1.4.2.2.3 - Light Agent Primitive [Core] -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). +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). ###### A.6.1.1.4.2.2.3.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Light Agent Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Light Agent Primitive. ###### A.6.1.1.4.2.2.3.1.1 - Global Activation Status [Core] @@ -38925,11 +38929,11 @@ The documents herein implement the Ecosystem Upkeep Primitives for Skybase. See ###### A.6.1.1.4.2.3.1 - Distribution Requirement Primitive [Core] -The documents herein contain all data and specifications for Skybase’s Instance of the Distribution Requirement Primitive. See [A.2.2.6.1 - Distribution Requirement Primitive](0804ab13-d276-4ad9-a935-dc9f7fc2e350). +The documents herein contain all data and specifications for Skybase's Instance of the Distribution Requirement Primitive. See [A.2.2.6.1 - Distribution Requirement Primitive](0804ab13-d276-4ad9-a935-dc9f7fc2e350). ###### A.6.1.1.4.2.3.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Distribution Requirement Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Distribution Requirement Primitive. ###### A.6.1.1.4.2.3.1.1.1 - Global Activation Status [Core] @@ -38997,7 +39001,7 @@ This document defines the protocol for routine ongoing management of the Single ###### A.6.1.1.4.2.3.1.2.1.2.1.1 - Process Definition For Buy Back And Distribution Obligation [Core] -The process to buy back and distribute 0.25% of Skybase’s tokens per year will be specified in future iterations of the Skybase Artifact. +The process to buy back and distribute 0.25% of Skybase's tokens per year will be specified in future iterations of the Skybase Artifact. ###### A.6.1.1.4.2.3.1.2.1.2.2 - Non-Routine Protocol [Core] @@ -39033,11 +39037,11 @@ Because the Distribution Requirement Primitive is deployed only once, no further ###### A.6.1.1.4.2.3.2 - Market Cap Fee Primitive [Core] -The documents herein contain all data and specifications for Skybase’s instances of the Market Cap Fee Primitive. See [A.2.2.6.2 - Market Cap Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28). +The documents herein contain all data and specifications for Skybase's instances of the Market Cap Fee Primitive. See [A.2.2.6.2 - Market Cap Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28). ###### A.6.1.1.4.2.3.2.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Market Cap Fee Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Market Cap Fee Primitive. ###### A.6.1.1.4.2.3.2.1.1 - Global Activation Status [Core] @@ -39085,11 +39089,11 @@ The in progress Invocations of the Market Cap Fee Primitive are contained herein ###### A.6.1.1.4.2.3.3 - Upkeep Rebate Primitive [Core] -The documents herein contain all data and specifications for Skybase’s instance of the Upkeep Rebate Primitive. See [A.2.2.6.3 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988). +The documents herein contain all data and specifications for Skybase's instance of the Upkeep Rebate Primitive. See [A.2.2.6.3 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988). ###### A.6.1.1.4.2.3.3.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Upkeep Rebate Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Upkeep Rebate Primitive. ###### A.6.1.1.4.2.3.3.1.1 - Global Activation Status [Core] @@ -39157,7 +39161,7 @@ When paying Ecosystem Upkeep fees, Skybase deducts the rebate from the fees it p ###### A.6.1.1.4.2.3.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] -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. +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. ###### A.6.1.1.4.2.3.3.2.1.2.2 - Non-Routine Protocol [Core] @@ -39197,11 +39201,11 @@ The documents herein implement the SkyLink Primitives for Skybase. See [A.2.2.7 ###### A.6.1.1.4.2.4.1 - Token SkyLink Primitive [Core] -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). +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). ###### A.6.1.1.4.2.4.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Token SkyLink Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Token SkyLink Primitive. ###### A.6.1.1.4.2.4.1.1.1 - Global Activation Status [Core] @@ -39253,11 +39257,11 @@ The documents herein implement the Demand Side Stablecoin Primitives for Skybase ###### A.6.1.1.4.2.5.1 - Distribution Reward Primitive [Core] -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). +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). ###### A.6.1.1.4.2.5.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Distribution Reward Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Distribution Reward Primitive. ###### A.6.1.1.4.2.5.1.1.1 - Global Activation Status [Core] @@ -39275,29 +39279,29 @@ This Instance’s associated Instance Configuration Document is located at [A.6. 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). -###### A.6.1.1.4.2.5.1.1.2.4 - DeFi Saver Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.3 - DeFi Saver Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.4 - DeFi Saver Instance Configuration Document](9907bb75-f389-42bb-8fe4-e03ff3039c46). +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). -###### A.6.1.1.4.2.5.1.1.2.5 - CoW Swap Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.4 - CoW Swap Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.5 - CoW Swap Instance Configuration Document](80f22d64-0ccf-4bb2-8da4-d170a95d2161). +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). -###### A.6.1.1.4.2.5.1.1.2.6 - ParaSwap Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.5 - ParaSwap Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.6 - ParaSwap Instance Configuration Document](d3f7f0e6-b912-4464-be3f-20b0c600bcfa). +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). -###### A.6.1.1.4.2.5.1.1.2.7 - Yearn (Gimme) Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.6 - Yearn (Gimme) Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.7 - Yearn (Gimme) Instance Configuration Document](f36ce752-38d1-4dd4-8a51-dd18f2151756). +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). -###### A.6.1.1.4.2.5.1.1.2.8 - MOM Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.7 - MOM Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.8 - MOM Instance Configuration Document](ee4f9b64-aeb7-4813-b187-996e8172fea1). +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). -###### A.6.1.1.4.2.5.1.1.2.9 - Lazy Summer Protocol Instance Configuration Document Location [Core] +###### A.6.1.1.4.2.5.1.1.2.8 - Lazy Summer Protocol Instance Configuration Document Location [Core] -This Instance’s associated Instance Configuration Document is located at [A.6.1.1.4.2.5.1.2.9 - Lazy Summer Protocol Instance Configuration Document](74db9986-5277-4c5f-8e27-f6a312ed591f). +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). ###### A.6.1.1.4.2.5.1.1.3 - Completed Instances Directory [Core] @@ -39506,67 +39510,67 @@ The Active Data is updated as follows: The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.4 - DeFi Saver Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.3 - DeFi Saver Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the DeFi Saver Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.4.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.3.1 - Parameters [Core] The documents herein define the parameters of the DeFi Saver Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.4.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.3.1.1 - Reward Code [Core] `1002`. -###### A.6.1.1.4.2.5.1.2.4.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.3.1.2 - Tracking Methodology [Core] 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). -###### A.6.1.1.4.2.5.1.2.4.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.3.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the DeFi Saver Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.4.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.3.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the DeFi Saver Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.4.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.3.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.4.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.3.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.4.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.3.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the DeFi Saver Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.4.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.3.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the DeFi Saver Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.4.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.3.3 - Data Repository [Core] The documents herein contain data relevant to the DeFi Saver Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.4.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.3.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.4.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.3.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.4.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.3.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.4.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.3.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the DeFi Saver Instance of the Distribution Reward Primitive are defined as Active Data. @@ -39575,20 +39579,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.4.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.3.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.4.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.3.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.4.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.3.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -39598,71 +39602,71 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.4.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.3.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] DeFi Saver - `0x6467e807dB1E71B9Ef04E0E3aFb962E4B0900B2B` -###### A.6.1.1.4.2.5.1.2.5 - CoW Swap Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.4 - CoW Swap Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the CoW Swap Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.5.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.4.1 - Parameters [Core] The documents herein define the parameters of the CoW Swap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.5.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.4.1.1 - Reward Code [Core] `1003`. -###### A.6.1.1.4.2.5.1.2.5.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.4.1.2 - Tracking Methodology [Core] -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) are checked for where they coincide perfectly with USDS deposit transactions into sUSDS. +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. -###### A.6.1.1.4.2.5.1.2.5.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.4.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the CoW Swap Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.5.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.4.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the CoW Swap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.5.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.4.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.5.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.4.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.5.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.4.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the CoW Swap Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.5.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.4.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the CoW Swap Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.5.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.4.3 - Data Repository [Core] The documents herein contain data relevant to the CoW Swap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.5.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.4.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.5.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.4.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.5.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.4.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.5.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.4.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the CoW Swap Instance of the Distribution Reward Primitive are defined as Active Data. @@ -39671,20 +39675,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.5.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.4.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.5.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.4.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.5.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.4.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -39694,71 +39698,71 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.5.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.4.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] CoW Swap - `0x616dE58c011F8736fa20c7Ae5352F7f6FB9F0669` -###### A.6.1.1.4.2.5.1.2.6 - ParaSwap Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.5 - ParaSwap Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the ParaSwap Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.6.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.5.1 - Parameters [Core] The documents herein define the parameters of the ParaSwap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.6.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.5.1.1 - Reward Code [Core] `1004`. -###### A.6.1.1.4.2.5.1.2.6.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.5.1.2 - Tracking Methodology [Core] 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). -###### A.6.1.1.4.2.5.1.2.6.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.5.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the ParaSwap Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.6.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.5.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the ParaSwap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.6.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.5.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.6.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.5.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.6.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.5.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the ParaSwap Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.6.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.5.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the ParaSwap Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.6.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.5.3 - Data Repository [Core] The documents herein contain data relevant to the ParaSwap Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.6.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.5.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.6.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.5.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.6.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.5.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.6.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.5.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the ParaSwap Instance of the Distribution Reward Primitive are defined as Active Data. @@ -39767,20 +39771,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.6.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.5.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.6.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.5.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.6.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.5.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -39790,71 +39794,71 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.6.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.5.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact. -###### A.6.1.1.4.2.5.1.2.7 - Yearn (Gimme) Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.6 - Yearn (Gimme) Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Yearn (Gimme) Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.7.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.6.1 - Parameters [Core] The documents herein define the parameters of the Yearn (Gimme) Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.7.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.6.1.1 - Reward Code [Core] `1007`. -###### A.6.1.1.4.2.5.1.2.7.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.6.1.2 - Tracking Methodology [Core] 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). -###### A.6.1.1.4.2.5.1.2.7.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.6.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the Yearn (Gimme) Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.7.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.6.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Yearn (Gimme) Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.7.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.6.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.7.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.6.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.7.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.6.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Yearn (Gimme) Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.7.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.6.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the Yearn (Gimme) Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.7.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.6.3 - Data Repository [Core] The documents herein contain data relevant to the Yearn (Gimme) Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.7.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.6.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.7.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.6.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.7.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.6.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.7.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.6.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the Yearn (Gimme) Instance of the Distribution Reward Primitive are defined as Active Data. @@ -39863,20 +39867,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.7.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.6.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.7.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.6.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.7.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.6.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -39886,71 +39890,71 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.7.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.6.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] Yearn (Gimme) - `0xFEB4acf3df3cDEA7399794D0869ef76A6EfAff52` -###### A.6.1.1.4.2.5.1.2.8 - MOM Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.7 - MOM Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the MOM Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.8.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.7.1 - Parameters [Core] The documents herein define the parameters of the MOM Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.8.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.7.1.1 - Reward Code [Core] `1015`. -###### A.6.1.1.4.2.5.1.2.8.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.7.1.2 - Tracking Methodology [Core] 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). -###### A.6.1.1.4.2.5.1.2.8.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.7.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the MOM Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.8.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.7.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the MOM Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.8.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.7.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.8.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.7.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.8.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.7.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the MOM Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.8.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.7.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the MOM Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.8.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.7.3 - Data Repository [Core] The documents herein contain data relevant to the MOM Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.8.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.7.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.8.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.7.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.8.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.7.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.8.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.7.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the MOM Instance of the Distribution Reward Primitive are defined as Active Data. @@ -39959,20 +39963,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.8.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.7.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.8.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.7.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.2.8.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.7.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -39982,93 +39986,93 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.8.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.7.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact. -###### A.6.1.1.4.2.5.1.2.9 - Lazy Summer Protocol Instance Configuration Document [Core] +###### A.6.1.1.4.2.5.1.2.8 - Lazy Summer Protocol Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Lazy Summer Protocol Distribution Reward Primitive Instance. -###### A.6.1.1.4.2.5.1.2.9.1 - Parameters [Core] +###### A.6.1.1.4.2.5.1.2.8.1 - Parameters [Core] The documents herein define the parameters of the Lazy Summer Protocol Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.9.1.1 - Reward Code [Core] +###### A.6.1.1.4.2.5.1.2.8.1.1 - Reward Code [Core] `1016`. -###### A.6.1.1.4.2.5.1.2.9.1.2 - Tracking Methodology [Core] +###### A.6.1.1.4.2.5.1.2.8.1.2 - Tracking Methodology [Core] This parameter will be defined in a future iteration of the Skybase Artifact. -###### A.6.1.1.4.2.5.1.2.9.1.3 - Custom Instance Parameters [Core] +###### A.6.1.1.4.2.5.1.2.8.1.3 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the Lazy Summer Protocol Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.2.9.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.2.8.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Lazy Summer Protocol Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.9.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.8.2.1 - Routine Protocol [Core] -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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). +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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.2.9.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.2.8.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.2.9.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.2.8.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Lazy Summer Protocol Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.9.2.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.2.8.2.3 - Emergency Protocol [Core] 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. -###### A.6.1.1.4.2.5.1.2.9.3 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.2.8.3 - Data Repository [Core] The documents herein contain data relevant to the Lazy Summer Protocol Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.2.9.3.1 - Initial Planning [Core] +###### A.6.1.1.4.2.5.1.2.8.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.9.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.4.2.5.1.2.8.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.9.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.4.2.5.1.2.8.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.4.2.5.1.2.9.3.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.8.3.4 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the Lazy Summer Protocol Instance of the Distribution Reward Primitive are defined as Active Data. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. -- The Update Process must follow the protocol for ‘Direct Edit’. +- The Update Process must follow the protocol for `Direct Edit`. -###### A.6.1.1.4.2.5.1.2.9.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.2.8.3.4.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.2.9.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.2.8.3.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. -- The Update Process must follow the protocol for ‘Direct Edit’. +- The Update Process must follow the protocol for `Direct Edit`. -###### A.6.1.1.4.2.5.1.2.9.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.2.8.3.5.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: @@ -40079,7 +40083,7 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.2.9.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.2.8.3.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] The payment address of this Third Party Partner will be defined in a future iteration of the Skybase Artifact. @@ -40107,47 +40111,35 @@ This Instance uses the Tracking Methodology specified in [A.2.2.8.1.2.1.2.2.1 - The documents herein define the custom parameters of the Summer.fi Instance of the Distribution Reward Primitive, if any. -###### A.6.1.1.4.2.5.1.3.1.1.2 - Operational Process Definition [Core] +###### A.6.1.1.4.2.5.1.3.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Summer.fi Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.3.1.1.2.1 - Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.3.1.2.1 - Routine Protocol [Core] 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.4.3.1 - Near-Term Process](05fb732b-de55-4886-81a7-7c5d4c13d2d2). Modifications 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. -###### A.6.1.1.4.2.5.1.3.1.1.2.1.1 - Agent Customizations [Core] +###### A.6.1.1.4.2.5.1.3.1.2.1.1 - Agent Customizations [Core] 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. [No customization presently.] -###### A.6.1.1.4.2.5.1.3.1.2 - Non-Routine Protocol [Core] +###### A.6.1.1.4.2.5.1.3.1.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Summer.fi Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.3.1.3 - Emergency Protocol [Core] +###### A.6.1.1.4.2.5.1.3.1.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the Summer.fi Instance of this Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.3.1.4 - Data Repository [Core] +###### A.6.1.1.4.2.5.1.3.1.3 - Data Repository [Core] The documents herein contain data relevant to the Summer.fi Instance of the Distribution Reward Primitive. -###### A.6.1.1.4.2.5.1.3.1.4.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.4.2.5.1.3.1.4.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.4.2.5.1.3.1.4.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.4.2.5.1.3.1.4.4 - Distribution Reward Payments [Active Data Controller] +###### A.6.1.1.4.2.5.1.3.1.3.1 - Distribution Reward Payments [Active Data Controller] The Distribution Reward payments for the Summer.fi Instance of the Distribution Reward Primitive are defined as Active Data. @@ -40156,20 +40148,20 @@ The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.3.1.4.4.0.6.1 - List Of Distribution Reward Payments [Active Data] +###### A.6.1.1.4.2.5.1.3.1.3.1.0.6.1 - List Of Distribution Reward Payments [Active Data] The Distribution Reward Payments are: -###### A.6.1.1.4.2.5.1.3.1.4.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] +###### A.6.1.1.4.2.5.1.3.1.3.2 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. - The Update Process must follow the protocol for ‘Direct Edit’. -###### A.6.1.1.4.2.5.1.3.1.4.5.0.6.1 - Payment Details Per Reward Period [Active Data] +###### A.6.1.1.4.2.5.1.3.1.3.2.0.6.1 - Payment Details Per Reward Period [Active Data] The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: - Reward Period @@ -40179,10 +40171,22 @@ The payment details consist of a table where each entry represents a single paym - Transaction Hash - Transaction Date -###### A.6.1.1.4.2.5.1.3.1.4.5.0.6.2 - Third Party Partner Payment Addresses [Active Data] +###### A.6.1.1.4.2.5.1.3.1.3.2.0.6.2 - Third Party Partner Payment Addresses [Active Data] Summer.fi - `0xC7b548AD9Cf38721810246C079b2d8083aba8909` +###### A.6.1.1.4.2.5.1.3.1.3.3 - Initial Planning [Core] + +The materials associated with initial planning of the Invocation of this Instance are contained herein. + +###### A.6.1.1.4.2.5.1.3.1.3.4 - Operational GovOps Review [Core] + +The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. + +###### A.6.1.1.4.2.5.1.3.1.3.5 - Artifact Edit Proposal [Core] + +The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. + ###### A.6.1.1.4.2.5.1.4 - In Progress Invocations [Core] 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). @@ -40266,7 +40270,7 @@ The Distribution Reward Payments are: ###### A.6.1.1.4.2.5.1.4.1.4.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: @@ -40366,7 +40370,7 @@ The Distribution Reward Payments are: ###### A.6.1.1.4.2.5.1.4.2.4.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: @@ -40466,7 +40470,7 @@ The Distribution Reward Payments are: ###### A.6.1.1.4.2.5.1.4.3.4.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: @@ -40565,7 +40569,7 @@ The Distribution Reward Payments are: ###### A.6.1.1.4.2.5.1.4.4.4.5 - Third Party Partner Payment Addresses And Transaction Records [Active Data Controller] -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. +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. The Active Data is updated as follows: - The Responsible Party is Operational GovOps. @@ -40587,11 +40591,11 @@ The payment address of this Third Party Partner will be defined in a future iter ###### A.6.1.1.4.2.5.2 - Integration Boost Primitive [Core] -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). +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). ###### A.6.1.1.4.2.5.2.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Integration Boost Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Integration Boost Primitive. ###### A.6.1.1.4.2.5.2.1.1 - Global Activation Status [Core] @@ -40675,7 +40679,7 @@ The payment cadence for the Euler Integration Boost is weekly. ###### A.6.1.1.4.2.5.2.2.1.1.5 - Integration Boost Data Submission Format [Core] -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/. +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/). ###### A.6.1.1.4.2.5.2.2.1.1.6 - Integration Boost Data Submission Responsible Actor [Core] @@ -40966,7 +40970,7 @@ The payment cadence for the Compound Integration Boost is weekly. ###### A.6.1.1.4.2.5.2.4.1.2.5 - Integration Boost Data Submission Format [Core] -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/. +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/). ###### A.6.1.1.4.2.5.2.4.1.2.6 - Integration Boost Data Submission Responsible Actor [Core] @@ -41035,11 +41039,11 @@ The Integration Boost Payments are: ###### A.6.1.1.4.2.5.3 - Pioneer Chain Primitive [Core] -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). +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). ###### A.6.1.1.4.2.5.3.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Pioneer Chain Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Pioneer Chain Primitive. ###### A.6.1.1.4.2.5.3.1.1 - Global Activation Status [Core] @@ -41091,11 +41095,11 @@ The documents herein implement the Supply Side Stablecoin Primitives for Skybase ###### A.6.1.1.4.2.6.1 - Allocation System Primitive [Core] -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). +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). ###### A.6.1.1.4.2.6.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Allocation System Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Allocation System Primitive. ###### A.6.1.1.4.2.6.1.1.1 - Global Activation Status [Core] @@ -41147,11 +41151,11 @@ The in progress Invocations of the Allocation System Primitive are contained her ###### A.6.1.1.4.2.6.2 - Junior Risk Capital Rental Primitive [Core] -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). +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). ###### A.6.1.1.4.2.6.2.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Junior Risk Capital Rental Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Junior Risk Capital Rental Primitive. ###### A.6.1.1.4.2.6.2.1.1 - Global Activation Status [Core] @@ -41199,11 +41203,11 @@ The in progress Invocations of the Junior Risk Capital Rental Primitive are cont ###### A.6.1.1.4.2.6.3 - Asset Liability Management Rental Primitive [Core] -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). +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). ###### A.6.1.1.4.2.6.3.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Asset Liability Management Rental Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Asset Liability Management Rental Primitive. ###### A.6.1.1.4.2.6.3.1.1 - Global Activation Status [Core] @@ -41255,11 +41259,11 @@ The documents herein implement the Core Governance Primitives for Skybase. See [ ###### A.6.1.1.4.2.7.1 - Core Governance Reward Primitive [Core] -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). +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). ###### A.6.1.1.4.2.7.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Skybase’s usage of the Core Governance Reward Primitive. +The documents herein organize all base information relevant to Skybase's usage of the Core Governance Reward Primitive. ###### A.6.1.1.4.2.7.1.1.1 - Global Activation Status [Core] @@ -41269,6 +41273,10 @@ The documents herein organize all base information relevant to Skybase’s usage This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`. +###### A.6.1.1.4.2.7.1.1.2.1 - Sky.money Frontend Instance Configuration Document Location [Core] + +This Instance's associated Instance Configuration Document is located at [Sky.money Frontend Instance Configuration Document](33a977ad-77eb-45f6-850e-4d00eed8d049). + ###### A.6.1.1.4.2.7.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`. @@ -41297,6 +41305,58 @@ The subtrees for Instances of the Core Governance Reward Primitive with `Suspend The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein. +###### A.6.1.1.4.2.7.1.2.1 - Sky.money Frontend Instance Configuration Document [Core] + +The documents herein contain the Instance Configuration Document for the Sky.money Frontend Core Governance Reward Primitive Instance. + +###### A.6.1.1.4.2.7.1.2.1.1 - Parameters [Core] + +The documents herein define the parameters of the Sky.money Frontend Instance of the Core Governance Reward Primitive. + +###### A.6.1.1.4.2.7.1.2.1.1.1 - Reward Code [Core] + +`1`. + +###### A.6.1.1.4.2.7.1.2.1.1.2 - Tracking Methodology [Core] + +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). + +###### A.6.1.1.4.2.7.1.2.1.1.3 - Custom Instance Parameters [Core] + +The documents herein define the custom parameters of the Sky.money Frontend Instance of the Core Governance Reward Primitive, if any. + +###### A.6.1.1.4.2.7.1.2.1.1.3.1 - Integrator Recipient [Core] + +The Integrator is Sky.money Frontend, which is controlled by Skybase. As such, no additional Integrator payment will be made. + +###### A.6.1.1.4.2.7.1.2.1.2 - Data Repository [Core] + +The documents herein contain data relevant to the Sky.money Frontend Instance of the Core Governance Reward Primitive. + +###### A.6.1.1.4.2.7.1.2.1.2.1 - Core Governance Reward Payments And Transaction Records [Active Data Controller] + +This Document records information pertaining to payments received by Skybase for Governance Rewards associated with this Instance. This information is defined as Active Data. + +The Active Data is updated as follows: + +- The Responsible Party is Operational GovOps. +- The Update Process must follow the protocol for 'Direct Edit'. + +###### A.6.1.1.4.2.7.1.2.1.2.1.0.6.1 - List Of Core Governance Reward Payments [Active Data] + +The payment details consist of a table where each entry represents a single payment. Each entry has the following fields: + +- Reward Period +- Payee (Skybase) +- Payment Address +- Amount Paid +- Transaction Hash +- Transaction Date + +###### A.6.1.1.4.2.7.1.2.1.2.1.0.6.2 - Governance Reward Payment Address [Active Data] + +The Sky.money Frontend Governance Reward payment address is Skybase's SubProxy Account on Ethereum Mainnet: `0x08978E3700859E476201c1D7438B3427e3C81140`. + ###### A.6.1.1.4.2.7.1.3 - Completed Instances [Core] The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein. @@ -41307,7 +41367,7 @@ The in progress Invocations of the Core Governance Reward Primitive are containe ##### A.6.1.1.4.3 - Omni Documents [Core] -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. +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. ###### A.6.1.1.4.3.1 - Governance Information Unrelated To Root Edit Primitive [Core] @@ -41315,27 +41375,27 @@ The documents herein specify Skybase governance information that is unrelated to ###### A.6.1.1.4.3.1.1 - Sky Forum [Core] -Skybase uses the Sky Forum for governance-related discussion. Posts should use the “Skybase Prime” category. +Skybase uses the Sky Forum for governance-related discussion. Posts should use the "Skybase Prime" category. ###### A.6.1.1.4.3.1.2 - Discord [Core] -Skybase also uses Discord for more immediate communication. The Sky Discord is located at https://t.co/v6zG0MZtak. +Skybase also uses Discord for more immediate communication. The Sky Discord is located at [https://t.co/v6zG0MZtak](https://t.co/v6zG0MZtak). ###### A.6.1.1.4.3.1.3 - Sky Ecosystem Emergency Response [Core] -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. +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. ###### A.6.1.1.4.3.1.4 - Agent-Specific Emergency Response [Core] -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. +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. ###### A.6.1.1.4.3.2 - Sky Primitives Strategy [Core] -The documents herein define Skybase’s strategic intent with respect to certain Sky Primitives. +The documents herein define Skybase's strategic intent with respect to certain Sky Primitives. ###### A.6.1.1.4.3.2.1 - Distribution Reward Strategy [Core] -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. +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. The guiding criteria are as follows: @@ -41346,7 +41406,7 @@ The guiding criteria are as follows: ###### A.6.1.1.4.3.2.2 - Integration Boost Strategy [Core] -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. +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. The guiding criteria are as follows: @@ -41356,12 +41416,12 @@ The guiding criteria are as follows: ###### A.6.1.1.4.3.2.3 - Core Governance Reward Strategy [Core] -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. +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. The guiding criteria are as follows: - **Security & Reliability:** The Prime Agent will uphold robust security measures and maintain high availability to prevent disruptions or unauthorized access. -- **Governance Framework Alignment:** Any updates to the frontend should integrate smoothly with Skybase’s existing governance mechanisms, preserving uninterrupted voting and proposal workflows. +- **Governance Framework Alignment:** Any updates to the frontend should integrate smoothly with Skybase's existing governance mechanisms, preserving uninterrupted voting and proposal workflows. ###### A.6.1.1.4.3.3 - Ecosystem Accords [Core] @@ -41369,7 +41429,7 @@ Skybase has formally agreed to the Ecosystem Accords herein. ###### A.6.1.1.4.3.3.1 - Ecosystem Accord 7 [Core] -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. +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). ###### A.6.1.1.4.3.4 - USDS Demand Subsidies [Core] @@ -41377,7 +41437,7 @@ Skybase uses capital to provide Subsidies to incentivize strategic markets to pr ###### A.6.1.1.4.3.4.1 - USDS Demand Subsidies Capital [Core] -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. +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. ###### A.6.1.1.4.3.4.2 - USDS Demand Subsidies Multisig [Core] @@ -42787,7 +42847,7 @@ The documents herein list general on-chain parameters for the Obex Liquidity Lay ###### A.6.1.1.5.2.6.1.2.1.1.4.1 - Allocator Vault Parameters [Core] -The Allocator Vault parameters for ALLOCATOR-OBEX-A are defined in [ALLOCATOR-OBEX-A Parameters](1ee3efd3-fe75-4766-bc6a-ec204f6a3bca). +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). ###### A.6.1.1.5.2.6.1.2.1.1.4.2 - Whitelisting Of ALMProxy [Core] @@ -43827,15 +43887,15 @@ The documents herein implement the Sky Primitives for Pattern. See [A.2.2 - Sky ###### A.6.1.1.6.2.1 - Genesis Primitives [Core] -The documents herein implement the Genesis Primitives for Pattern. See A.2.2.4 - Genesis Primitives. +The documents herein implement the Genesis Primitives for Pattern. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5). ###### A.6.1.1.6.2.1.1 - Agent Creation Primitive [Core] -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. +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). ###### A.6.1.1.6.2.1.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Pattern's usage of the Agent Creation Primitive. +The documents herein organize all base information relevant to Pattern's usage of the Agent Creation Primitive. ###### A.6.1.1.6.2.1.1.1.1 - Global Activation Status [Core] @@ -43851,7 +43911,7 @@ This document contains a Directory of all Instances of the Agent Creation Primit ###### A.6.1.1.6.2.1.1.1.3.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at Single Instance Configuration Document. +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). ###### A.6.1.1.6.2.1.1.1.4 - In Progress Invocations Directory [Core] @@ -43859,7 +43919,7 @@ Because the Agent Creation Primitive is deployed solely for the one-time creatio ###### A.6.1.1.6.2.1.1.1.5 - Hub Data Repository [Core] -The document herein contains the Data Repository for the Primitive Hub Document. +The document herein contains the Data Repository for the Primitive Hub Document. ###### A.6.1.1.6.2.1.1.1.5.1 - Archived Invocations/Instances [Core] @@ -43877,7 +43937,7 @@ The subtrees for Instances of the Agent Creation Primitive with `Suspended` Stat The Instances of the Agent Creation Primitive with `Active` Status are stored herein. -###### A.6.1.1.6.2.1.1.3 - Completed Instances [Core] +###### A.6.1.1.6.2.1.1.3 - Completed Instances Directory [Core] The Instances of the Agent Creation Primitive with `Completed` Status are contained herein. @@ -43899,7 +43959,7 @@ The address of Pattern's SubProxy Account on the Ethereum Mainnet is `0xbC8959Ae ###### A.6.1.1.6.2.1.1.3.1.1.3 - StarGuard Contract [Core] -The address of Pattern’s StarGuard contract on the Ethereum Mainnet is `0x2fb18b28fB39Ec3b26C3B5AF5222e2ca3B8B2269`. +The address of Pattern's StarGuard contract on the Ethereum Mainnet is `0x2fb18b28fB39Ec3b26C3B5AF5222e2ca3B8B2269`. ###### A.6.1.1.6.2.1.1.3.1.1.3.1 - StarGuard Max Delay [Core] @@ -43959,7 +44019,7 @@ This document contains a Directory of all Instances of the Prime Transformation ###### A.6.1.1.6.2.1.2.1.3.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at Single Instance Configuration Document. +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). ###### A.6.1.1.6.2.1.2.1.4 - In Progress Invocations Directory [Core] @@ -44025,7 +44085,7 @@ The materials associated with Operational GovOps Review during the Invocation of The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.1.2.3 - In Progress Invocations [Core] +###### A.6.1.1.6.2.1.2.4 - In Progress Invocations [Core] 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. @@ -44099,7 +44159,7 @@ This document contains a Directory of all Instances of the Agent Token Primitive ###### A.6.1.1.6.2.1.4.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](0667a9c2-6fe1-456e-bd0a-3cf367fac480). +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). ###### A.6.1.1.6.2.1.4.1.3 - Completed Instances Directory [Core] @@ -44107,7 +44167,7 @@ This document contains a Directory of all Instances of the Agent Token Primitive ###### A.6.1.1.6.2.1.4.1.4 - In Progress Invocations Directory [Core] -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. +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. ###### A.6.1.1.6.2.1.4.1.5 - Hub Data Repository [Core] @@ -44159,7 +44219,7 @@ The token Admin will be specified in a future iteration of the Pattern Artifact. ###### A.6.1.1.6.2.1.4.2.1.1.6 - Token Emissions [Core] -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](55999acf-75fe-4adf-8584-9746ef50d3e4). +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). ###### A.6.1.1.6.2.1.4.2.1.1.7 - Custom Instance Parameters [Core] @@ -44193,7 +44253,7 @@ The Instances of the Agent Token Primitive with `Completed` Status are contained ###### A.6.1.1.6.2.1.4.4 - In Progress Invocations [Core] -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. +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. ###### A.6.1.1.6.2.2 - Operational Primitives [Core] @@ -44217,7 +44277,7 @@ This document contains a Directory of all Instances of the Executor Accord Primi ###### A.6.1.1.6.2.2.1.1.2.1 - Ozone Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ozone Instance Configuration Document](960445d5-4b1c-406e-b05a-470e0cca6e71). +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). ###### A.6.1.1.6.2.2.1.1.3 - Completed Instances Directory [Core] @@ -44225,7 +44285,7 @@ This document contains a Directory of all Instances of the Executor Accord Primi ###### A.6.1.1.6.2.2.1.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.2.1.1.5 - Hub Data Repository [Core] @@ -44243,241 +44303,241 @@ The subtrees for failed Invocations of the Executor Accord Primitive are stored The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here. -###### A.6.1.1.6.2.2.1.1.5.1.3 - Active Instances [Core] +###### A.6.1.1.6.2.2.1.2 - Active Instances [Core] The Instances of the Executor Accord Primitive with `Active` Status are stored herein. -###### A.6.1.1.6.2.2.1.1.5.1.3.1 - Ozone Instance Configuration Document [Core] +###### A.6.1.1.6.2.2.1.2.1 - Ozone Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.1 - Parameters [Core] +###### A.6.1.1.6.2.2.1.2.1.1 - Parameters [Core] The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.1.1 - Operational Executor Agent [Core] +###### A.6.1.1.6.2.2.1.2.1.1.1 - Operational Executor Agent [Core] 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). -###### A.6.1.1.6.2.2.1.1.5.1.3.1.1.2 - Custom Instance Parameters [Core] +###### A.6.1.1.6.2.2.1.2.1.1.2 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.2 - Operational Process Definition [Core] +###### A.6.1.1.6.2.2.1.2.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.3 - Data Repository [Core] +###### A.6.1.1.6.2.2.1.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.3.1 - Initial Planning [Core] +###### A.6.1.1.6.2.2.1.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.6.2.2.1.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.1.3.1.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.6.2.2.1.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.1.4 - Completed Instances [Core] +###### A.6.1.1.6.2.2.1.3 - Completed Instances [Core] The Instances of the Executor Accord Primitive with `Completed` Status are stored herein. -###### A.6.1.1.6.2.2.1.1.5.1.5 - In Progress Invocations [Core] +###### A.6.1.1.6.2.2.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). -###### A.6.1.1.6.2.2.1.1.5.2 - Root Edit Primitive [Core] +###### A.6.1.1.6.2.2.2 - Root Edit Primitive [Core] 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). -###### A.6.1.1.6.2.2.1.1.5.2.1 - Primitive Hub Document [Core] +###### A.6.1.1.6.2.2.2.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Pattern's usage of the Root Edit Primitive. -###### A.6.1.1.6.2.2.1.1.5.2.1.1 - Global Activation Status [Core] +###### A.6.1.1.6.2.2.2.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.6.2.2.1.1.5.2.1.2 - Active Instances Directory [Core] +###### A.6.1.1.6.2.2.2.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`. -###### A.6.1.1.6.2.2.1.1.5.2.1.2.1 - Single Instance Configuration Document Location [Core] +###### A.6.1.1.6.2.2.2.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](a53a7f47-1c80-4ab8-bf86-d32dc0e21ccc). +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). -###### A.6.1.1.6.2.2.1.1.5.2.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.6.2.2.2.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`. -###### A.6.1.1.6.2.2.1.1.5.2.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.6.2.2.2.1.4 - In Progress Invocations Directory [Core] Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.6.2.2.1.1.5.2.1.5 - Hub Data Repository [Core] +###### A.6.1.1.6.2.2.2.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.6.2.2.1.1.5.2.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.6.2.2.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here. -###### A.6.1.1.6.2.2.1.1.5.2.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.6.2.2.2.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Root Edit Primitive are stored here. -###### A.6.1.1.6.2.2.1.1.5.2.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.6.2.2.2.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here. -###### A.6.1.1.6.2.2.1.1.5.2.2 - Active Instances [Core] +###### A.6.1.1.6.2.2.2.2 - Active Instances [Core] The Instances of the Root Edit Primitive with `Active` Status are stored herein. -###### A.6.1.1.6.2.2.1.1.5.2.2.1 - Single Instance Configuration Document [Core] +###### A.6.1.1.6.2.2.2.2.1 - Single Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.1 - Parameters [Core] +###### A.6.1.1.6.2.2.2.2.1.1 - Parameters [Core] -The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in Operational Process Definition. +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). -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2 - Operational Process Definition [Core] +###### A.6.1.1.6.2.2.2.2.1.2 - Operational Process Definition [Core] -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 [Governance Information Unrelated To Root Edit Primitive](df8e7155-ba1f-4606-8a4a-0619c06da12b). +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). -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1 - Routine Protocol [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1 - Routine Protocol [Core] 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). -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] 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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.1.1 - Short-Term Transitionary Measures [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.1.1 - Short-Term Transitionary Measures [Core] -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 Root Edit Proposal Submission. +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). -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] A future iteration of the Pattern Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.3 - Root Edit Proposal Review By Operational Facilitator [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.3 - Root Edit Proposal Review By Operational Facilitator [Core] Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment. If 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. -If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. +If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] 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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.5 - Root Edit Artifact Update [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.5 - Root Edit Artifact Update [Core] 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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.5.1 - Short-Term Transitionary Measures [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.5.1 - Short-Term Transitionary Measures [Core] 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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.1.6 - Artifact Edit Restrictions [Core] +###### A.6.1.1.6.2.2.2.2.1.2.1.6 - Artifact Edit Restrictions [Core] 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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.6.2.2.2.2.1.2.2 - Non-Routine Protocol [Core] The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact in non-routine conditions. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.3 - Emergency Protocol [Core] +###### A.6.1.1.6.2.2.2.2.1.2.3 - Emergency Protocol [Core] The documents herein define the process for using the Root Edit Primitive to update the Pattern Agent Artifact in emergency situations. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.2.3.1 - Root Edit Voting Process In Emergency Situations [Core] +###### A.6.1.1.6.2.2.2.2.1.2.3.1 - Root Edit Voting Process In Emergency Situations [Core] In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.8.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. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.3 - Data Repository [Core] +###### A.6.1.1.6.2.2.2.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Single Instance of the Root Edit Primitive. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.3.1 - Initial Planning [Core] +###### A.6.1.1.6.2.2.2.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.6.2.2.2.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.2.2.1.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.6.2.2.2.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.2.1.1.5.2.3 - Completed Instances [Core] +###### A.6.1.1.6.2.2.2.3 - Completed Instances [Core] The Instances of the Root Edit Primitive with `Completed` Status are contained herein. -###### A.6.1.1.6.2.2.1.1.5.2.4 - In Progress Invocations [Core] +###### A.6.1.1.6.2.2.2.4 - In Progress Invocations [Core] Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.6.2.2.1.1.5.3 - Light Agent Primitive [Core] +###### A.6.1.1.6.2.2.3 - Light Agent Primitive [Core] 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). -###### A.6.1.1.6.2.2.1.1.5.3.1 - Primitive Hub Document [Core] +###### A.6.1.1.6.2.2.3.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Pattern's usage of the Light Agent Primitive. -###### A.6.1.1.6.2.2.1.1.5.3.1.1 - Global Activation Status [Core] +###### A.6.1.1.6.2.2.3.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.6.2.2.1.1.5.3.1.2 - Active Instances Directory [Core] +###### A.6.1.1.6.2.2.3.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`. -###### A.6.1.1.6.2.2.1.1.5.3.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.6.2.2.3.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`. -###### A.6.1.1.6.2.2.1.1.5.3.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.6.2.2.3.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). -###### A.6.1.1.6.2.2.1.1.5.3.1.5 - Hub Data Repository [Core] +###### A.6.1.1.6.2.2.3.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.6.2.2.3.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.6.2.2.3.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Light Agent Primitive are stored here. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.6.2.2.3.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.2 - Active Instances [Core] +###### A.6.1.1.6.2.2.3.2 - Active Instances [Core] The Instances of the Light Agent Primitive with `Active` Status are stored herein. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.3 - Completed Instances [Core] +###### A.6.1.1.6.2.2.3.3 - Completed Instances [Core] The Instances of the Light Agent Primitive with `Completed` Status are contained herein. -###### A.6.1.1.6.2.2.1.1.5.3.1.5.4 - In Progress Invocations [Core] +###### A.6.1.1.6.2.2.3.4 - In Progress Invocations [Core] - The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.3 - Ecosystem Upkeep Primitives [Core] @@ -44501,7 +44561,7 @@ This document contains a Directory of all Instances of the Distribution Requirem ###### A.6.1.1.6.2.3.1.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](d8b7f338-3318-462c-a65d-4e49a29398b2). +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). ###### A.6.1.1.6.2.3.1.1.3 - Completed Instances Directory [Core] @@ -44547,39 +44607,39 @@ Pattern will buy back and distribute 0.25% of its total token supply per year. The documents herein define the custom parameters of the Single Instance of the Distribution Requirement Primitive, if any. -###### A.6.1.1.6.2.3.1.2.2 - Operational Process Definition [Core] +###### A.6.1.1.6.2.3.1.2.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Single Instance of the Distribution Requirement Primitive. -###### A.6.1.1.6.2.3.1.2.2.1 - Routine Protocol [Core] +###### A.6.1.1.6.2.3.1.2.1.2.1 - Routine Protocol [Core] This document defines the protocol for routine ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.6.2.3.1.2.2.1.1 - Process Definition [Core] +###### A.6.1.1.6.2.3.1.2.1.2.1.1 - Process Definition For Buy Back And Distribution Obligation [Core] The process to buy back and distribute 0.25% of Pattern's tokens per year will be specified in future iterations of the Pattern Artifact. -###### A.6.1.1.6.2.3.1.2.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.6.2.3.1.2.1.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.6.2.3.1.2.2.3 - Emergency Protocol [Core] +###### A.6.1.1.6.2.3.1.2.1.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.6.2.3.1.2.3 - Data Repository [Core] +###### A.6.1.1.6.2.3.1.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Single Instance of the Distribution Requirement Primitive. -###### A.6.1.1.6.2.3.1.2.3.1 - Initial Planning [Core] +###### A.6.1.1.6.2.3.1.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.3.1.2.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.6.2.3.1.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.6.2.3.1.2.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.6.2.3.1.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. @@ -44613,7 +44673,7 @@ This document contains a Directory of all Instances of the Market Cap Fee Primit ###### A.6.1.1.6.2.3.2.1.4 - In Progress Invocations Directory [Core] -This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.6.2.3.2.1.2 - Active Instances Directory](89506029-ceca-46b8-9be2-1ecef5996573), whereas failed Invocations are Archived in [A.6.1.1.6.2.3.2.1.5 - Hub Data Repository](4311c910-72a4-495c-9c96-50e37e0ef8d5). ###### A.6.1.1.6.2.3.2.1.5 - Hub Data Repository [Core] @@ -44641,7 +44701,7 @@ The Instances of the Market Cap Fee Primitive with `Completed` Status are stored ###### A.6.1.1.6.2.3.2.4 - In Progress Invocations [Core] -The in progress Invocations of the Market Cap Fee Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +The in progress Invocations of the Market Cap Fee Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.6.2.3.2.2 - Active Instances](41bd6957-da44-40b4-a84f-ad0f4b4600bf). ###### A.6.1.1.6.2.3.3 - Upkeep Rebate Primitive [Core] @@ -44661,7 +44721,7 @@ This document contains a Directory of all Instances of the Upkeep Rebate Primiti ###### A.6.1.1.6.2.3.3.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](77bd8e6f-aad2-4830-8822-1abc3281bfa8). +This Instance's associated Instance Configuration Document is located at [A.6.1.1.6.2.3.3.2.1 - Single Instance Configuration Document](77bd8e6f-aad2-4830-8822-1abc3281bfa8). ###### A.6.1.1.6.2.3.3.1.3 - Completed Instances Directory [Core] @@ -44669,7 +44729,7 @@ This document contains a Directory of all Instances of the Upkeep Rebate Primiti ###### A.6.1.1.6.2.3.3.1.4 - In Progress Invocations Directory [Core] -This document contains a Directory of all prospective Instances of the Upkeep Rebate Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked. ###### A.6.1.1.6.2.3.3.1.5 - Hub Data Repository [Core] @@ -44715,7 +44775,7 @@ Pattern keeps all tokens of other Agents it holds in its SubProxy account. When paying Ecosystem Upkeep fees, Pattern deducts the rebate from the fees it pays. -###### A.6.1.1.6.2.3.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] +###### A.6.1.1.6.2.3.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] 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. @@ -44745,11 +44805,11 @@ The materials associated with preparing the Artifact Edit Proposal during the In ###### A.6.1.1.6.2.3.3.3 - Completed Instances [Core] -The Instances of the Upkeep Rebate Primitive with `Completed` Status are stored herein. +The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein. ###### A.6.1.1.6.2.3.3.4 - In Progress Invocations [Core] -The in progress Invocations of the Upkeep Rebate Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked. ###### A.6.1.1.6.2.4 - SkyLink Primitives [Core] @@ -44777,7 +44837,7 @@ This document contains a Directory of all Instances of the Token SkyLink Primiti ###### A.6.1.1.6.2.4.1.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.4.1.1.5 - Hub Data Repository [Core] @@ -44805,7 +44865,7 @@ The Instances of the Token SkyLink Primitive with `Completed` Status are stored ###### A.6.1.1.6.2.4.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.5 - Demand Side Stablecoin Primitives [Core] @@ -44833,7 +44893,7 @@ This document contains a Directory of all Instances of the Distribution Reward P ###### A.6.1.1.6.2.5.1.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.5.1.1.5 - Hub Data Repository [Core] @@ -44861,7 +44921,7 @@ The Instances of the Distribution Reward Primitive with `Completed` Status are s ###### A.6.1.1.6.2.5.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.5.2 - Integration Boost Primitive [Core] @@ -44885,7 +44945,7 @@ This document contains a Directory of all Instances of the Integration Boost Pri ###### A.6.1.1.6.2.5.2.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.5.2.1.5 - Hub Data Repository [Core] @@ -44909,11 +44969,11 @@ The Instances of the Integration Boost Primitive with `Active` Status are stored ###### A.6.1.1.6.2.5.2.3 - Completed Instances [Core] -The Instances of the Integration Boost Primitive with `Completed` Status are stored herein. +The Instances of the Integration Boost Primitive with `Completed` Status are contained herein. ###### A.6.1.1.6.2.5.2.4 - In Progress Invocations [Core] -The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.5.3 - Pioneer Chain Primitive [Core] @@ -44937,7 +44997,7 @@ This document contains a Directory of all Instances of the Pioneer Chain Primiti ###### A.6.1.1.6.2.5.3.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.5.3.1.5 - Hub Data Repository [Core] @@ -44965,7 +45025,7 @@ The Instances of the Pioneer Chain Primitive with `Completed` Status are stored ###### A.6.1.1.6.2.5.3.4 - In Progress Invocations [Core] -The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.6 - Supply Side Stablecoin Primitives [Core] @@ -44993,7 +45053,7 @@ This document contains a Directory of all Instances of the Allocation System Pri ###### A.6.1.1.6.2.6.1.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.6.1.1.5 - Hub Data Repository [Core] @@ -45013,7 +45073,7 @@ The subtrees for Instances of the Allocation System Primitive with `Suspended` S ###### A.6.1.1.6.2.6.1.2 - Multi-Instance Coordinator Document [Core] -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. +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. ###### A.6.1.1.6.2.6.1.2.1 - General Specifications [Core] @@ -45053,7 +45113,7 @@ The Instances of the Allocation System Primitive with `Completed` Status are sto ###### A.6.1.1.6.2.6.1.5 - In Progress Invocations [Core] -The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to Active Instances. +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). ###### A.6.1.1.6.2.6.2 - Junior Risk Capital Rental Primitive [Core] @@ -45077,7 +45137,7 @@ This document contains a Directory of all Instances of the Junior Risk Capital R ###### A.6.1.1.6.2.6.2.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.6.2.1.5 - Hub Data Repository [Core] @@ -45105,7 +45165,7 @@ The Instances of the Junior Risk Capital Rental Primitive with `Completed` Statu ###### A.6.1.1.6.2.6.2.4 - In Progress Invocations [Core] -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 Active Instances. +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). ###### A.6.1.1.6.2.6.3 - Asset Liability Management Rental Primitive [Core] @@ -45129,7 +45189,7 @@ This document contains a Directory of all Instances of the Asset Liability Manag ###### A.6.1.1.6.2.6.3.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.6.3.1.5 - Hub Data Repository [Core] @@ -45157,7 +45217,7 @@ The Instances of the Asset Liability Management Rental Primitive with `Completed ###### A.6.1.1.6.2.6.3.4 - In Progress Invocations [Core] -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 Active Instances. +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). ###### A.6.1.1.6.2.7 - Core Governance Primitives [Core] @@ -45185,7 +45245,7 @@ This document contains a Directory of all Instances of the Core Governance Rewar ###### A.6.1.1.6.2.7.1.1.4 - In Progress Invocations Directory [Core] -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 Active Instances Directory, whereas failed Invocations are Archived in Hub Data Repository. +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). ###### A.6.1.1.6.2.7.1.1.5 - Hub Data Repository [Core] @@ -45213,7 +45273,7 @@ The Instances of the Core Governance Reward Primitive with `Completed` Status ar ###### A.6.1.1.6.2.7.1.4 - In Progress Invocations [Core] -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 Active Instances. +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). ##### A.6.1.1.6.3 - Omni Documents [Core] @@ -45221,7 +45281,7 @@ The documents herein define Pattern's strategic intent and operational processes ###### A.6.1.1.6.3.1 - Governance Information Unrelated To Root Edit Primitive [Core] -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 Root Edit Primitive. +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). ###### A.6.1.1.6.3.1.1 - Sky Forum [Core] @@ -45241,15 +45301,15 @@ The documents herein specify all of the logic for Launch Agent 6, including Laun ##### A.6.1.1.7.1 - Introduction [Core] -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. +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. ##### A.6.1.1.7.2 - Sky Primitives [Core] -The documents herein implement the Sky Primitives for Launch Agent 6. See [A.2.2 - Sky Primitives](cde2604-a138-4c1b-9d9a-14895835c907). +The documents herein implement the Sky Primitives for Launch Agent 6. See [A.2.2.1.5 - Primitives](947a5b27-d2dc-41e4-b6fd-696e35e2929d). ###### A.6.1.1.7.2.1 - Genesis Primitives [Core] -The documents herein implement the Genesis Primitives for Launch Agent 6. See A.2.2.4 - Genesis Primitives. +The documents herein implement the Genesis Primitives for Launch Agent 6. See [A.2.2.4 - Genesis Primitives](3d5e3668-8333-4908-adcc-5784cfe7f6b5). ###### A.6.1.1.7.2.1.1 - Agent Creation Primitive [Core] @@ -45257,7 +45317,7 @@ The documents herein contain all data and specifications for Launch Agent 6's In ###### A.6.1.1.7.2.1.1.1 - Primitive Hub Document [Core] -The documents herein organize all base information relevant to Launch Agent 6's usage of the Agent Creation Primitive. +The documents herein organize all base information relevant to Launch Agent 6's usage of the Agent Creation Primitive. ###### A.6.1.1.7.2.1.1.1.1 - Global Activation Status [Core] @@ -45273,7 +45333,7 @@ This document contains a Directory of all Instances of the Agent Creation Primit ###### A.6.1.1.7.2.1.1.1.3.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](a4cd3e49-84c9-44e6-86f2-6a1b34162d50). +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). ###### A.6.1.1.7.2.1.1.1.4 - In Progress Invocations Directory [Core] @@ -45281,7 +45341,7 @@ Because the Agent Creation Primitive is deployed solely for the one-time creatio ###### A.6.1.1.7.2.1.1.1.5 - Hub Data Repository [Core] -The document herein contains the Data Repository for the Primitive Hub Document. +The document herein contains the Data Repository for the Primitive Hub Document. ###### A.6.1.1.7.2.1.1.1.5.1 - Archived Invocations/Instances [Core] @@ -45373,7 +45433,7 @@ This document contains a Directory of all Instances of the Prime Transformation ###### A.6.1.1.7.2.1.2.1.3.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](9bfd222e-7d6f-4ad3-a248-bf87900f4993). +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). ###### A.6.1.1.7.2.1.2.1.4 - In Progress Invocations Directory [Core] @@ -45439,7 +45499,7 @@ The materials associated with Operational GovOps Review during the Invocation of The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.2.3 - In Progress Invocations [Core] +###### A.6.1.1.7.2.1.2.4 - In Progress Invocations [Core] 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. @@ -45513,7 +45573,7 @@ This document contains a Directory of all Instances of the Agent Token Primitive ###### A.6.1.1.7.2.1.4.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](80dc8fe6-5c4e-44aa-b9fb-89350ac4e5bf). +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). ###### A.6.1.1.7.2.1.4.1.3 - Completed Instances Directory [Core] @@ -45521,7 +45581,7 @@ This document contains a Directory of all Instances of the Agent Token Primitive ###### A.6.1.1.7.2.1.4.1.4 - In Progress Invocations Directory [Core] -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. +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. ###### A.6.1.1.7.2.1.4.1.5 - Hub Data Repository [Core] @@ -45573,7 +45633,7 @@ The token Admin will be specified in a future iteration of the Launch Agent 6 Ar ###### A.6.1.1.7.2.1.4.2.1.1.6 - Token Emissions [Core] -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](55999acf-75fe-4adf-8584-9746ef50d3e4). +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). ###### A.6.1.1.7.2.1.4.2.1.1.7 - Custom Instance Parameters [Core] @@ -45607,999 +45667,999 @@ The Instances of the Agent Token Primitive with `Completed` Status are contained ###### A.6.1.1.7.2.1.4.4 - In Progress Invocations [Core] -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. +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. -###### A.6.1.1.7.2.1.5 - Operational Primitives [Core] +###### A.6.1.1.7.2.2 - Operational Primitives [Core] The documents herein implement the Operational Primitives for Launch Agent 6. See [A.2.2.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad). -###### A.6.1.1.7.2.1.5.1 - Executor Accord Primitive [Core] +###### A.6.1.1.7.2.2.1 - Executor Accord Primitive [Core] 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). -###### A.6.1.1.7.2.1.5.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.2.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Executor Accord Primitive. -###### A.6.1.1.7.2.1.5.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.2.1.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.5.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.2.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.5.1.1.2.1 - Ozone Instance Configuration Document Location [Core] +###### A.6.1.1.7.2.2.1.1.2.1 - Ozone Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Ozone Instance Configuration Document](c41fe115-5145-438e-bcaf-9924996b4fcd). +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). -###### A.6.1.1.7.2.1.5.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.2.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.5.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.2.1.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](a1260e19-86fc-4ebe-a53a-501e4baf9752), whereas failed Invocations are Archived in [Hub Data Repository](10c951e0-3200-4359-a76e-c1ff9ccb9105). +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). -###### A.6.1.1.7.2.1.5.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.2.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.5.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.2.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.2.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Executor Accord Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.2.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.1.3 - Active Instances [Core] +###### A.6.1.1.7.2.2.1.2 - Active Instances [Core] The Instances of the Executor Accord Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1 - Ozone Instance Configuration Document [Core] +###### A.6.1.1.7.2.2.1.2.1 - Ozone Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Ozone Executor Accord Primitive Instance. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.1 - Parameters [Core] +###### A.6.1.1.7.2.2.1.2.1.1 - Parameters [Core] The documents herein define the parameters of the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.1.1 - Operational Executor Agent [Core] +###### A.6.1.1.7.2.2.1.2.1.1.1 - Operational Executor Agent [Core] 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) -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.1.2 - Custom Instance Parameters [Core] +###### A.6.1.1.7.2.2.1.2.1.1.2 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the Ozone Instance of the Executor Accord Primitive, if any. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.2 - Operational Process Definition [Core] +###### A.6.1.1.7.2.2.1.2.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.3 - Data Repository [Core] +###### A.6.1.1.7.2.2.1.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Ozone Instance of the Executor Accord Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.3.1 - Initial Planning [Core] +###### A.6.1.1.7.2.2.1.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.7.2.2.1.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.1.3.1.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.7.2.2.1.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.1.4 - Completed Instances [Core] +###### A.6.1.1.7.2.2.1.3 - Completed Instances [Core] The Instances of the Executor Accord Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.5.1.1.5.1.5 - In Progress Invocations [Core] +###### A.6.1.1.7.2.2.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](d5f4610a-9cd1-4a6e-96de-5ea617463152). +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). -###### A.6.1.1.7.2.1.5.1.1.5.2 - Root Edit Primitive [Core] +###### A.6.1.1.7.2.2.2 - Root Edit Primitive [Core] 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). -###### A.6.1.1.7.2.1.5.1.1.5.2.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.2.2.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Root Edit Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.2.2.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.5.1.1.5.2.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.2.2.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.2.1 - Single Instance Configuration Document Location [Core] +###### A.6.1.1.7.2.2.2.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](db6cb28a-c001-404d-b630-6ea755499ed3). +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). -###### A.6.1.1.7.2.1.5.1.1.5.2.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.2.2.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.2.2.1.4 - In Progress Invocations Directory [Core] Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.2.2.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.2.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.2.2.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Root Edit Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.2.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.2.2.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.2.2 - Active Instances [Core] +###### A.6.1.1.7.2.2.2.2 - Active Instances [Core] The Instances of the Root Edit Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1 - Single Instance Configuration Document [Core] +###### A.6.1.1.7.2.2.2.2.1 - Single Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.1 - Parameters [Core] +###### A.6.1.1.7.2.2.2.2.1.1 - Parameters [Core] -The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [Operational Process Definition](cfd923fb-0a53-4dd2-bb4f-5e840bda69c6). +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). -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2 - Operational Process Definition [Core] +###### A.6.1.1.7.2.2.2.2.1.2 - Operational Process Definition [Core] -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 [Governance Information Unrelated To Root Edit Primitive](a472d201-3dfd-4939-9789-5cedce9ea37a). +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). -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1 - Routine Protocol [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1 - Routine Protocol [Core] 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). -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] 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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.1.1 - Short-Term Transitionary Measures [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.1.1 - Short-Term Transitionary Measures [Core] -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 [Root Edit Proposal Submission](70c91853-b74b-4c6b-befb-8446f00c9691). +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). -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] A future iteration of the Launch Agent 6 Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.3 - Root Edit Proposal Review By Operational Facilitator [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.3 - Root Edit Proposal Review By Operational Facilitator [Core] Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment. If 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. -If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. +If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] 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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.5 - Root Edit Artifact Update [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.5 - Root Edit Artifact Update [Core] 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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.5.1 - Short-Term Transitionary Measures [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.5.1 - Short-Term Transitionary Measures [Core] 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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.1.6 - Artifact Edit Restrictions [Core] +###### A.6.1.1.7.2.2.2.2.1.2.1.6 - Artifact Edit Restrictions [Core] 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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.7.2.2.2.2.1.2.2 - Non-Routine Protocol [Core] The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact in non-routine conditions. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.3 - Emergency Protocol [Core] +###### A.6.1.1.7.2.2.2.2.1.2.3 - Emergency Protocol [Core] The documents herein define the process for using the Root Edit Primitive to update the Launch Agent 6 Agent Artifact in emergency situations. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.2.3.1 - Root Edit Voting Process In Emergency Situations [Core] +###### A.6.1.1.7.2.2.2.2.1.2.3.1 - Root Edit Voting Process In Emergency Situations [Core] In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.8.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. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.3 - Data Repository [Core] +###### A.6.1.1.7.2.2.2.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Single Instance of the Root Edit Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.3.1 - Initial Planning [Core] +###### A.6.1.1.7.2.2.2.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.7.2.2.2.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.2.2.1.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.7.2.2.2.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.2.3 - Completed Instances [Core] +###### A.6.1.1.7.2.2.2.3 - Completed Instances [Core] The Instances of the Root Edit Primitive with `Completed` Status are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.2.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.2.2.4 - In Progress Invocations [Core] Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.5.1.1.5.3 - Light Agent Primitive [Core] +###### A.6.1.1.7.2.2.3 - Light Agent Primitive [Core] 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). -###### A.6.1.1.7.2.1.5.1.1.5.3.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.2.3.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Light Agent Primitive. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.2.3.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.5.1.1.5.3.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.2.3.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.2.3.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.2.3.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](e04cf30c-cb79-4b5c-902a-c75e6387dadb), whereas failed Invocations are Archived in [Hub Data Repository](29a0cd95-500c-45ce-b5a5-66ea10493545). +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). -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.2.3.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.2.3.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.2.3.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Light Agent Primitive are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.2.3.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.2 - Active Instances [Core] +###### A.6.1.1.7.2.2.3.2 - Active Instances [Core] The Instances of the Light Agent Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.3 - Completed Instances [Core] +###### A.6.1.1.7.2.2.3.3 - Completed Instances [Core] The Instances of the Light Agent Primitive with `Completed` Status are contained herein. -###### A.6.1.1.7.2.1.5.1.1.5.3.1.5.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.2.3.4 - In Progress Invocations [Core] - The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](a2e69b89-5ac1-43bf-8841-ecfe17ad8d84). +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). -###### A.6.1.1.7.2.1.6 - Ecosystem Upkeep Primitives [Core] +###### A.6.1.1.7.2.3 - Ecosystem Upkeep Primitives [Core] 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). -###### A.6.1.1.7.2.1.6.1 - Distribution Requirement Primitive [Core] +###### A.6.1.1.7.2.3.1 - Distribution Requirement Primitive [Core] The documents herein contain all data and specifications for Launch Agent 6's Instance of the Distribution Requirement Primitive. See [A.2.2.6.1 - Distribution Requirement Primitive](0804ab13-d276-4ad9-a935-dc9f7fc2e350). -###### A.6.1.1.7.2.1.6.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.3.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.3.1.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.6.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.3.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Distribution Requirement Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.6.1.1.2.1 - Single Instance Configuration Document Location [Core] +###### A.6.1.1.7.2.3.1.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](8cd599cd-d6f1-4ef4-86cd-94aaf842d62e). +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). -###### A.6.1.1.7.2.1.6.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.3.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Distribution Requirement Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.6.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.3.1.1.4 - In Progress Invocations Directory [Core] Because the Distribution Requirement Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.6.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.3.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.6.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.3.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Distribution Requirement Primitive are stored here. -###### A.6.1.1.7.2.1.6.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.3.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Distribution Requirement Primitive are stored here. -###### A.6.1.1.7.2.1.6.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.3.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Distribution Requirement Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.6.1.2 - Active Instances [Core] +###### A.6.1.1.7.2.3.1.2 - Active Instances [Core] The Instances of the Distribution Requirement Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.6.1.2.1 - Single Instance Configuration Document [Core] +###### A.6.1.1.7.2.3.1.2.1 - Single Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Single Distribution Requirement Primitive Instance. -###### A.6.1.1.7.2.1.6.1.2.1.1 - Parameters [Core] +###### A.6.1.1.7.2.3.1.2.1.1 - Parameters [Core] The documents herein define the parameters of the Single Instance of the Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.1.1.1 - Terms [Core] +###### A.6.1.1.7.2.3.1.2.1.1.1 - Terms [Core] Launch Agent 6 will buy back and distribute 0.25% of its total token supply per year. -###### A.6.1.1.7.2.1.6.1.2.1.1.2 - Custom Instance Parameters [Core] +###### A.6.1.1.7.2.3.1.2.1.1.2 - Custom Instance Parameters [Core] The documents herein define the custom parameters of the Single Instance of the Distribution Requirement Primitive, if any. -###### A.6.1.1.7.2.1.6.1.2.2 - Operational Process Definition [Core] +###### A.6.1.1.7.2.3.1.2.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Single Instance of the Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.2.1 - Routine Protocol [Core] +###### A.6.1.1.7.2.3.1.2.1.2.1 - Routine Protocol [Core] This document defines the protocol for routine ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.2.1.1 - Process Definition For Buy Back And Distribution Obligation [Core] +###### A.6.1.1.7.2.3.1.2.1.2.1.1 - Process Definition For Buy Back And Distribution Obligation [Core] The process to buy back and distribute 0.25% of Launch Agent 6's tokens per year will be specified in future iterations of the Launch Agent 6 Artifact. -###### A.6.1.1.7.2.1.6.1.2.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.7.2.3.1.2.1.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.2.3 - Emergency Protocol [Core] +###### A.6.1.1.7.2.3.1.2.1.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.3 - Data Repository [Core] +###### A.6.1.1.7.2.3.1.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Single Instance of the Distribution Requirement Primitive. -###### A.6.1.1.7.2.1.6.1.2.3.1 - Initial Planning [Core] +###### A.6.1.1.7.2.3.1.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.1.2.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.7.2.3.1.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.1.2.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.7.2.3.1.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.1.3 - Completed Instances [Core] +###### A.6.1.1.7.2.3.1.3 - Completed Instances [Core] The Instances of the Distribution Requirement Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.6.1.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.3.1.4 - In Progress Invocations [Core] Because the Distribution Requirement Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.6.2 - Market Cap Fee Primitive [Core] +###### A.6.1.1.7.2.3.2 - Market Cap Fee Primitive [Core] The documents herein contain all data and specifications for Launch Agent 6's instances of the Market Cap Fee Primitive. See [A.2.2.6.2 - Market Cap Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28). -###### A.6.1.1.7.2.1.6.2.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.3.2.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Market Cap Fee Primitive. -###### A.6.1.1.7.2.1.6.2.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.3.2.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.6.2.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.3.2.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Market Cap Fee Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.6.2.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.3.2.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Market Cap Fee Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.6.2.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.3.2.1.4 - In Progress Invocations Directory [Core] -This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [Active Instances Directory](b3a39e9a-9acc-43c7-a774-2221912f3a8d), whereas failed Invocations are Archived in [Hub Data Repository](a319de1d-bc18-4b5a-b970-58ee5491b3c9). +This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.7.2.3.2.1.2 - Active Instances Directory](b3a39e9a-9acc-43c7-a774-2221912f3a8d), whereas failed Invocations are Archived in [A.6.1.1.7.2.3.2.1.5 - Hub Data Repository](a319de1d-bc18-4b5a-b970-58ee5491b3c9). -###### A.6.1.1.7.2.1.6.2.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.3.2.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.6.2.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.3.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Market Cap Fee Primitive are stored here. -###### A.6.1.1.7.2.1.6.2.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.3.2.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Market Cap Fee Primitive are stored here. -###### A.6.1.1.7.2.1.6.2.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.3.2.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Market Cap Fee Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.6.2.2 - Active Instances [Core] +###### A.6.1.1.7.2.3.2.2 - Active Instances [Core] The Instances of the Market Cap Fee Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.6.2.3 - Completed Instances [Core] +###### A.6.1.1.7.2.3.2.3 - Completed Instances [Core] The Instances of the Market Cap Fee Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.6.2.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.3.2.4 - In Progress Invocations [Core] -The in progress Invocations of the Market Cap Fee Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](2ee1b59c-a1cc-452e-bf6f-bcbc11527506). +The in progress Invocations of the Market Cap Fee Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [A.6.1.1.7.2.3.2.2 - Active Instances](2ee1b59c-a1cc-452e-bf6f-bcbc11527506). -###### A.6.1.1.7.2.1.6.3 - Upkeep Rebate Primitive [Core] +###### A.6.1.1.7.2.3.3 - Upkeep Rebate Primitive [Core] -The documents herein contain all data and specifications for Launch Agent 6's instances of the Upkeep Rebate Primitive. See [A.2.2.6.3 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988). +The documents herein contain all data and specifications for Launch Agent 6's instance of the Upkeep Rebate Primitive. See [A.2.2.6.3 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988). -###### A.6.1.1.7.2.1.6.3.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.3.3.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.3.3.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.6.3.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.3.3.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.6.3.1.2.1 - Single Instance Configuration Document Location [Core] +###### A.6.1.1.7.2.3.3.1.2.1 - Single Instance Configuration Document Location [Core] -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document](6e734cc1-a07e-42d7-afac-31ffa3cfd5dc). +This Instance's associated Instance Configuration Document is located at [A.6.1.1.7.2.3.3.2.1 - Single Instance Configuration Document](6e734cc1-a07e-42d7-afac-31ffa3cfd5dc). -###### A.6.1.1.7.2.1.6.3.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.3.3.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.6.3.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.3.3.1.4 - In Progress Invocations Directory [Core] Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.6.3.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.3.3.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.6.3.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.3.3.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here. -###### A.6.1.1.7.2.1.6.3.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.3.3.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here. -###### A.6.1.1.7.2.1.6.3.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.3.3.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.6.3.2 - Active Instances [Core] +###### A.6.1.1.7.2.3.3.2 - Active Instances [Core] The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.6.3.2.1 - Single Instance Configuration Document [Core] +###### A.6.1.1.7.2.3.3.2.1 - Single Instance Configuration Document [Core] The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance. -###### A.6.1.1.7.2.1.6.3.2.1.1 - Parameters [Core] +###### A.6.1.1.7.2.3.3.2.1.1 - Parameters [Core] 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. -###### A.6.1.1.7.2.1.6.3.2.1.2 - Operational Process Definition [Core] +###### A.6.1.1.7.2.3.3.2.1.2 - Operational Process Definition [Core] The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.2.1.2.1 - Routine Protocol [Core] +###### A.6.1.1.7.2.3.3.2.1.2.1 - Routine Protocol [Core] This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.2.1.2.1.1 - Launch Agent 6 Holds Tokens Of Other Agents In Its SubProxy Account [Core] +###### A.6.1.1.7.2.3.3.2.1.2.1.1 - Launch Agent 6 Holds Tokens Of Other Agents In Its SubProxy Account [Core] Launch Agent 6 keeps all tokens of other Agents it holds in its SubProxy account. -###### A.6.1.1.7.2.1.6.3.2.1.2.1.2 - Launch Agent 6 Deducts Rebate From Ecosystem Upkeep Fees [Core] +###### A.6.1.1.7.2.3.3.2.1.2.1.2 - Launch Agent 6 Deducts Rebate From Ecosystem Upkeep Fees [Core] When paying Ecosystem Upkeep fees, Launch Agent 6 deducts the rebate from the fees it pays. -###### A.6.1.1.7.2.1.6.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] +###### A.6.1.1.7.2.3.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] 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. -###### A.6.1.1.7.2.1.6.3.2.1.2.2 - Non-Routine Protocol [Core] +###### A.6.1.1.7.2.3.3.2.1.2.2 - Non-Routine Protocol [Core] The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.2.1.2.3 - Emergency Protocol [Core] +###### A.6.1.1.7.2.3.3.2.1.2.3 - Emergency Protocol [Core] The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.2.1.3 - Data Repository [Core] +###### A.6.1.1.7.2.3.3.2.1.3 - Data Repository [Core] The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive. -###### A.6.1.1.7.2.1.6.3.2.1.3.1 - Initial Planning [Core] +###### A.6.1.1.7.2.3.3.2.1.3.1 - Initial Planning [Core] The materials associated with initial planning of the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.3.2.1.3.2 - Operational GovOps Review [Core] +###### A.6.1.1.7.2.3.3.2.1.3.2 - Operational GovOps Review [Core] The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.3.2.1.3.3 - Artifact Edit Proposal [Core] +###### A.6.1.1.7.2.3.3.2.1.3.3 - Artifact Edit Proposal [Core] The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.7.2.1.6.3.3 - Completed Instances [Core] +###### A.6.1.1.7.2.3.3.3 - Completed Instances [Core] -The Instances of the Upkeep Rebate Primitive with `Completed` Status are stored herein. +The Instances of the Upkeep Rebate Primitive with `Completed` Status are contained herein. -###### A.6.1.1.7.2.1.6.3.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.3.3.4 - In Progress Invocations [Core] -The in progress Invocations of the Upkeep Rebate Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](288c1b34-5986-4a83-abc1-56efa6af6500). +Because the Upkeep Rebate Primitive is deployed only once, no further Instances of the Primitive can be Invoked. -###### A.6.1.1.7.2.1.7 - SkyLink Primitives [Core] +###### A.6.1.1.7.2.4 - SkyLink Primitives [Core] The documents herein implement the SkyLink Primitives for Launch Agent 6. See [A.2.2.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f). -###### A.6.1.1.7.2.1.7.1 - Token SkyLink Primitive [Core] +###### A.6.1.1.7.2.4.1 - Token SkyLink Primitive [Core] 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). -###### A.6.1.1.7.2.1.7.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.4.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Token SkyLink Primitive. -###### A.6.1.1.7.2.1.7.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.4.1.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.7.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.4.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.7.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.4.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.7.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.4.1.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](5697d516-fc74-40a8-a2c7-7f00c534f3a6), whereas failed Invocations are Archived in [Hub Data Repository](dff4750a-bf17-475d-8741-049e00083d5f). +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). -###### A.6.1.1.7.2.1.7.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.4.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.7.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.4.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here. -###### A.6.1.1.7.2.1.7.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.4.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Token SkyLink Primitive are stored here. -###### A.6.1.1.7.2.1.7.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.4.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.7.1.2 - Active Instances [Core] +###### A.6.1.1.7.2.4.1.2 - Active Instances [Core] The Instances of the Token SkyLink Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.7.1.3 - Completed Instances [Core] +###### A.6.1.1.7.2.4.1.3 - Completed Instances [Core] The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.7.1.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.4.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](9e0bbf6f-a71c-4db1-80a2-b3a5991a072b). +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). -###### A.6.1.1.7.2.1.8 - Demand Side Stablecoin Primitives [Core] +###### A.6.1.1.7.2.5 - Demand Side Stablecoin Primitives [Core] 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). -###### A.6.1.1.7.2.1.8.1 - Distribution Reward Primitive [Core] +###### A.6.1.1.7.2.5.1 - Distribution Reward Primitive [Core] 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). -###### A.6.1.1.7.2.1.8.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.5.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Distribution Reward Primitive. -###### A.6.1.1.7.2.1.8.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.5.1.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.8.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.5.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.8.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.5.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.8.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.5.1.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](ef465153-3408-49f2-8b39-761c445e7a8a), whereas failed Invocations are Archived in [Hub Data Repository](aad36c3f-431d-4a1d-942b-a583805618c1). +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). -###### A.6.1.1.7.2.1.8.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.5.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.8.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.5.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here. -###### A.6.1.1.7.2.1.8.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.5.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Distribution Reward Primitive are stored here. -###### A.6.1.1.7.2.1.8.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.5.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.8.1.2 - Active Instances [Core] +###### A.6.1.1.7.2.5.1.2 - Active Instances [Core] The Instances of the Distribution Reward Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.8.1.3 - Completed Instances [Core] +###### A.6.1.1.7.2.5.1.3 - Completed Instances [Core] The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.8.1.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.5.1.4 - In Progress Invocations [Core] -The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](464695e4-744c-48fd-a023-565096dc9144). +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). -###### A.6.1.1.7.2.1.8.2 - Integration Boost Primitive [Core] +###### A.6.1.1.7.2.5.2 - Integration Boost Primitive [Core] 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). -###### A.6.1.1.7.2.1.8.2.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.5.2.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Integration Boost Primitive. -###### A.6.1.1.7.2.1.8.2.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.5.2.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.8.2.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.5.2.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.8.2.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.5.2.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.8.2.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.5.2.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](cdbc02f2-7ec8-4ae4-b027-8938f0824864), whereas failed Invocations are Archived in [Hub Data Repository](ed0542a2-e910-4caa-9d1a-e96381aed48d). +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). -###### A.6.1.1.7.2.1.8.2.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.5.2.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.8.2.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.5.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here. -###### A.6.1.1.7.2.1.8.2.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.5.2.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Integration Boost Primitive are stored here. -###### A.6.1.1.7.2.1.8.2.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.5.2.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.8.2.2 - Active Instances [Core] +###### A.6.1.1.7.2.5.2.2 - Active Instances [Core] The Instances of the Integration Boost Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.8.2.3 - Completed Instances [Core] +###### A.6.1.1.7.2.5.2.3 - Completed Instances [Core] -The Instances of the Integration Boost Primitive with `Completed` Status are stored herein. +The Instances of the Integration Boost Primitive with `Completed` Status are contained herein. -###### A.6.1.1.7.2.1.8.2.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.5.2.4 - In Progress Invocations [Core] -The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](2628525c-6956-49dd-9a48-e3de403a0597). +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). -###### A.6.1.1.7.2.1.8.3 - Pioneer Chain Primitive [Core] +###### A.6.1.1.7.2.5.3 - Pioneer Chain Primitive [Core] 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). -###### A.6.1.1.7.2.1.8.3.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.5.3.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Pioneer Chain Primitive. -###### A.6.1.1.7.2.1.8.3.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.5.3.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.8.3.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.5.3.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.8.3.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.5.3.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.8.3.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.5.3.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](04a6899a-8b0c-4b3d-873a-69325cc5bf50), whereas failed Invocations are Archived in [Hub Data Repository](5cd1f6cd-7349-429d-9f3d-42aaca039b69). +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). -###### A.6.1.1.7.2.1.8.3.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.5.3.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.8.3.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.5.3.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here. -###### A.6.1.1.7.2.1.8.3.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.5.3.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here. -###### A.6.1.1.7.2.1.8.3.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.5.3.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.8.3.2 - Active Instances [Core] +###### A.6.1.1.7.2.5.3.2 - Active Instances [Core] The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.8.3.3 - Completed Instances [Core] +###### A.6.1.1.7.2.5.3.3 - Completed Instances [Core] The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.8.3.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.5.3.4 - In Progress Invocations [Core] -The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](1cf22b6c-83d7-4ddf-8b4c-13059f4ec555). +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). -###### A.6.1.1.7.2.1.9 - Supply Side Stablecoin Primitives [Core] +###### A.6.1.1.7.2.6 - Supply Side Stablecoin Primitives [Core] 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). -###### A.6.1.1.7.2.1.9.1 - Allocation System Primitive [Core] +###### A.6.1.1.7.2.6.1 - Allocation System Primitive [Core] 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). -###### A.6.1.1.7.2.1.9.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.6.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Allocation System Primitive. -###### A.6.1.1.7.2.1.9.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.6.1.1.1 - Global Activation Status [Core] `Active` -###### A.6.1.1.7.2.1.9.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.6.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.9.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.6.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.9.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.6.1.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](57de5036-2c56-4cb6-b1dd-8e2dc1b214f6), whereas failed Invocations are Archived in [Hub Data Repository](7936954e-cfc9-4491-9432-842450e86af3). +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). -###### A.6.1.1.7.2.1.9.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.6.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.9.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.6.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here. -###### A.6.1.1.7.2.1.9.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.6.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Allocation System Primitive are stored here. -###### A.6.1.1.7.2.1.9.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.6.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.9.1.2 - Multi-Instance Coordinator Document [Core] +###### A.6.1.1.7.2.6.1.2 - Multi-Instance Coordinator Document [Core] 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. -###### A.6.1.1.7.2.1.9.1.3 - Active Instances [Core] +###### A.6.1.1.7.2.6.1.3 - Active Instances [Core] The Instances of the Allocation System Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.9.1.4 - Completed Instances [Core] +###### A.6.1.1.7.2.6.1.4 - Completed Instances [Core] The Instances of the Allocation System Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.9.1.5 - In Progress Invocations [Core] +###### A.6.1.1.7.2.6.1.5 - In Progress Invocations [Core] -The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances](6f8a8e14-13be-4893-9bb1-17c88e984426). +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). -###### A.6.1.1.7.2.1.9.2 - Junior Risk Capital Rental Primitive [Core] +###### A.6.1.1.7.2.6.2 - Junior Risk Capital Rental Primitive [Core] 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). -###### A.6.1.1.7.2.1.9.2.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.6.2.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Junior Risk Capital Rental Primitive. -###### A.6.1.1.7.2.1.9.2.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.6.2.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.9.2.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.6.2.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.9.2.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.6.2.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.9.2.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.6.2.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](997d4b26-65c5-4ad3-bbde-3441df9491ff), whereas failed Invocations are Archived in [Hub Data Repository](2c163402-c55f-4995-8866-a0074ff01df6). +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). -###### A.6.1.1.7.2.1.9.2.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.6.2.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.9.2.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.6.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here. -###### A.6.1.1.7.2.1.9.2.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.6.2.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here. -###### A.6.1.1.7.2.1.9.2.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.6.2.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.9.2.2 - Active Instances [Core] +###### A.6.1.1.7.2.6.2.2 - Active Instances [Core] The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.9.2.3 - Completed Instances [Core] +###### A.6.1.1.7.2.6.2.3 - Completed Instances [Core] The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.9.2.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.6.2.4 - In Progress Invocations [Core] -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 [Active Instances](d48fecab-0528-4d96-b760-49ca8568be85). +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). -###### A.6.1.1.7.2.1.9.3 - Asset Liability Management Rental Primitive [Core] +###### A.6.1.1.7.2.6.3 - Asset Liability Management Rental Primitive [Core] 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). -###### A.6.1.1.7.2.1.9.3.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.6.3.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Asset Liability Management Rental Primitive. -###### A.6.1.1.7.2.1.9.3.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.6.3.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.9.3.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.6.3.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.9.3.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.6.3.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.9.3.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.6.3.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](f6266454-9845-44e8-a079-851ddd576e8f), whereas failed Invocations are Archived in [Hub Data Repository](50250f92-7f80-4685-b94d-f1ed639c9c98). +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). -###### A.6.1.1.7.2.1.9.3.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.6.3.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.9.3.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.6.3.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here. -###### A.6.1.1.7.2.1.9.3.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.6.3.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here. -###### A.6.1.1.7.2.1.9.3.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.6.3.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.9.3.2 - Active Instances [Core] +###### A.6.1.1.7.2.6.3.2 - Active Instances [Core] The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.9.3.3 - Completed Instances [Core] +###### A.6.1.1.7.2.6.3.3 - Completed Instances [Core] The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.9.3.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.6.3.4 - In Progress Invocations [Core] -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 [Active Instances](d5f275e5-98b9-4ef7-90dd-f81e786252df). +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). -###### A.6.1.1.7.2.1.10 - Core Governance Primitives [Core] +###### A.6.1.1.7.2.7 - Core Governance Primitives [Core] 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). -###### A.6.1.1.7.2.1.10.1 - Core Governance Reward Primitive [Core] +###### A.6.1.1.7.2.7.1 - Core Governance Reward Primitive [Core] 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). -###### A.6.1.1.7.2.1.10.1.1 - Primitive Hub Document [Core] +###### A.6.1.1.7.2.7.1.1 - Primitive Hub Document [Core] The documents herein organize all base information relevant to Launch Agent 6's usage of the Core Governance Reward Primitive. -###### A.6.1.1.7.2.1.10.1.1.1 - Global Activation Status [Core] +###### A.6.1.1.7.2.7.1.1.1 - Global Activation Status [Core] `Inactive` -###### A.6.1.1.7.2.1.10.1.1.2 - Active Instances Directory [Core] +###### A.6.1.1.7.2.7.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`. -###### A.6.1.1.7.2.1.10.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.7.2.7.1.1.3 - Completed Instances Directory [Core] This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`. -###### A.6.1.1.7.2.1.10.1.1.4 - In Progress Invocations Directory [Core] +###### A.6.1.1.7.2.7.1.1.4 - In Progress Invocations Directory [Core] -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 [Active Instances Directory](3269b582-af99-475b-b3e2-9d25a079c5ec), whereas failed Invocations are Archived in [Hub Data Repository](5b09155b-063c-41c0-b714-4a5d275d7b57). +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). -###### A.6.1.1.7.2.1.10.1.1.5 - Hub Data Repository [Core] +###### A.6.1.1.7.2.7.1.1.5 - Hub Data Repository [Core] The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.7.2.1.10.1.1.5.1 - Archived Invocations/Instances [Core] +###### A.6.1.1.7.2.7.1.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here. -###### A.6.1.1.7.2.1.10.1.1.5.1.1 - Failed Invocations [Core] +###### A.6.1.1.7.2.7.1.1.5.1.1 - Failed Invocations [Core] The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here. -###### A.6.1.1.7.2.1.10.1.1.5.1.2 - Suspended Instances [Core] +###### A.6.1.1.7.2.7.1.1.5.1.2 - Suspended Instances [Core] The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here. -###### A.6.1.1.7.2.1.10.1.2 - Active Instances [Core] +###### A.6.1.1.7.2.7.1.2 - Active Instances [Core] The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein. -###### A.6.1.1.7.2.1.10.1.3 - Completed Instances [Core] +###### A.6.1.1.7.2.7.1.3 - Completed Instances [Core] The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein. -###### A.6.1.1.7.2.1.10.1.4 - In Progress Invocations [Core] +###### A.6.1.1.7.2.7.1.4 - In Progress Invocations [Core] -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 [Active Instances](b4954eea-0108-4820-bdbf-402e74ea1407). +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). ##### A.6.1.1.7.3 - Omni Documents [Core] @@ -46607,15 +46667,7 @@ The documents herein define Launch Agent 6's strategic intent and operational pr ###### A.6.1.1.7.3.1 - Governance Information Unrelated To Root Edit Primitive [Core] -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 Root Edit Primitive. - -###### A.6.1.1.7.3.2 - Ecosystem Accords [Core] - -Launch Agent 6 has formally agreed to the Ecosystem Accords herein. - -###### A.6.1.1.7.3.2.1 - Ecosystem Accord 6 [Core] - -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). +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). ###### A.6.1.1.7.3.1.1 - Sky Forum [Core] @@ -46629,6 +46681,14 @@ The documents herein specify Launch Agent 6's emergency response protocol in sit 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. +###### A.6.1.1.7.3.2 - Ecosystem Accords [Core] + +Launch Agent 6 has formally agreed to the Ecosystem Accords herein. + +###### A.6.1.1.7.3.2.1 - Ecosystem Accord 6 [Core] + +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). + #### A.6.1.1.8 - Launch Agent 7 [Core] 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. @@ -46657,11 +46717,11 @@ The documents herein organize all base information relevant to Launch Agent 7's `Completed` -###### A.6.1.1.8.2.1.1.1.2 - Active Intances Directory [Core] +###### A.6.1.1.8.2.1.1.1.2 - Active Instances Directory [Core] This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`. -###### A.6.1.1.8.2.1.1.1.3 - Completed Instances Directory [Core] +###### A.6.1.1.8.2.1.1.1.3 - Completed Instances [Core] This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`. @@ -47031,7 +47091,7 @@ This Instance’s associated Instance Configuration Document is located at [A.6. This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`. -###### A.6.1.1.8.2.2.1.1.4 - In Progress Invocactions Directory [Core] +###### A.6.1.1.8.2.2.1.1.4 - In Progress Invocations Directory [Core] 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). @@ -47181,7 +47241,7 @@ Within seven (7) days of the proposal being submitted, the Operational Facilitat If 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. -If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. +If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. ###### A.6.1.1.8.2.2.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] @@ -47227,11 +47287,11 @@ The materials associated with Operational GovOps Review during the Invocation of The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. -###### A.6.1.1.8.2.2.2.2.3 - Completed Instances [Core] +###### A.6.1.1.8.2.2.2.3 - Completed Instances [Core] The Instances of the Root Edit Primitive with `Completed` Status are contained herein. -###### A.6.1.1.8.2.2.2.2.4 - In Progress Invocations [Core] +###### A.6.1.1.8.2.2.2.4 - In Progress Invocations [Core] Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. @@ -47421,7 +47481,7 @@ This document contains a Directory of all Instances of the Market Cap Fee Primit ###### A.6.1.1.8.2.3.2.1.4 - In Progress Invocations Directory [Core] -This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.3.2.1.2 Active Instances Directory](524d791c-8402-4d2a-ab42-e06c3dd5caef), whereas failed Invocations are Archived in [A.6.1.1.8.2.3.2.1.5 - Hub Data Repository](527bf1a7-eff1-423d-af04-19b76dd33798). +This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [A.6.1.1.8.2.3.2.1.2 - Active Instances Directory](524d791c-8402-4d2a-ab42-e06c3dd5caef), whereas failed Invocations are Archived in [A.6.1.1.8.2.3.2.1.5 - Hub Data Repository](527bf1a7-eff1-423d-af04-19b76dd33798). ###### A.6.1.1.8.2.3.2.1.5 - Hub Data Repository [Core] @@ -47863,7 +47923,7 @@ This document contains a Directory of all prospective Instances of the Junior Ri The documents herein contain the Data Repository for the Primitive Hub Document. -###### A.6.1.1.8.2.6.2.1.5.1 - Archived Invoecations/Instances [Core] +###### A.6.1.1.8.2.6.2.1.5.1 - Archived Invocations/Instances [Core] The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here. @@ -48011,7 +48071,7 @@ Launch Agent 7 uses the Sky Forum for governance-related discussion. Posts shoul 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. -###### A.6.1.1.8.2.3.1.3 - Agent-Specific Emergency Response [Core] +###### A.6.1.1.8.3.1.3 - Agent-Specific Emergency Response [Core] 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. @@ -48021,15 +48081,15 @@ The documents herein each set out the Artifacts for Executor Agents. Executor Ag #### A.6.1.2.1 - Operational Executor Agent Amatsu [Core] -The Agent Artifact for Amatsu will be specified in a future iteration of the Atlas. In the interim, the subdocuments herein contain key information regarding Amatsu. +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. ##### A.6.1.2.1.1 - Operational Executor Facilitator [Core] -The Operational Facilitator for Amatsu is Endgame Edge. +The Operational Facilitator for Operational Executor Agent Amatsu is Endgame Edge. ##### A.6.1.2.1.2 - Operational GovOps [Core] -Operational GovOps for Amatsu is Amatsu GovOps. +Operational GovOps for Operational Executor Agent Amatsu is Soter Labs. #### A.6.1.2.2 - Operational Executor Agent Ozone [Core] @@ -48053,4 +48113,4 @@ The Facilitator for Core Council Executor Agent 1 is JanSky. ##### A.6.1.2.3.2 - Core GovOps [Core] -GovOps for Core Council Executor Agent 1 is Atlas Axis. \ No newline at end of file +GovOps for Core Council Executor Agent 1 is Atlas Axis. diff --git a/helpers/templates/Launch Agent Artifact Template.md b/helpers/templates/Launch Agent Artifact Template.md deleted file mode 100644 index 90311baa..00000000 --- a/helpers/templates/Launch Agent Artifact Template.md +++ /dev/null @@ -1,1385 +0,0 @@ -#### A.6.1.1.$LaunchAgentDocNumber - $LaunchAgentName [Core] - -The documents herein specify all of the logic for $LaunchAgentName, including $LaunchAgentName's strategy and how it uses the Sky Primitives to operationalize this strategy. - -##### A.6.1.1.$LaunchAgentDocNumber.1 - Introduction [Core] - -$LaunchAgentName is an Agent $LaunchAgentIntroduction - -##### A.6.1.1.$LaunchAgentDocNumber.2 - Sky Primitives [Core] - -The documents herein implement the Sky Primitives for $LaunchAgentName. See [A.2.3 - Sky Primitives](cde2604-a138-4c1b-9d9a-14895835c907). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1 - Genesis Primitives [Core] - -The documents herein implement the Genesis Primitives for $LaunchAgentName. See A.2.3.4 - Genesis Primitives. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1 - Agent Creation Primitve [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instance of the Agent Creation Primitive. See [A.2.3.4.1 - Agent Creation Primitive](82b95f6d-4883-4f08-ac3a-9d8189013fbe). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Agent Creation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.1 - Global Activation Status [Core] - -`$AgentCreationActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Agent Creation Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.3.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.4 - In Progress Invocations Directory [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.5 - Hub Data Repository [Core] - -The document herein contains the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.5.1 - Archived Invocations/Instances [Core] < - -The subtrees for archived Invocations and Instances of the Agent Creation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Agent Creation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Agent Creation Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.2 - Active Instances [Core] - -The Instances of the Agent Creation Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3 - Completed Instances [Core] - -The Instances of the Agent Creation Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Agent Creation Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.1 - Parameters [Core] - -The documents herein define the parameters of the Single Instance of the Agent Creation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.1.1 - Name [Core] - -The name of the Agent is $LaunchAgentName. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.1.2 - SubProxy Account [Core] - -The address of $LaunchAgentName's SubProxy Account will be specified in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.1.3 - Genesis Account [Core] - -The address of $LaunchAgentName's Genesis Account will be specified in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.1.4 - Custom Instance Parameters [Core] - -The documents herein define the custom parameters of the Single Instance of the Agent Creation Primitive, if any. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.2 - Operational Process Definition [Core] - -Because the Agent Creation Primitive is deployed solely for the one-time creation of the Agent, no further operational process is needed post-deployment. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Agent Creation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.3.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.1.4 - In Progress Invocations Directory [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2 - Prime Transformation Primitve [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's instance of the Prime Transformation Primitive. See [A.2.3.4.2 - Prime Transformation Primitive](81411106-fd6d-4f9c-b3ae-7af7b5e62482). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Prime Transformation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.1 - Global Activation Status [Core] - -`$PrimeTransformationActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Prime Transformation Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.3.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.4 - In Progress Invocations Directory [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Prime Transformation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Prime Transformation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Prime Transformation Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.2 - Active Instances [Core] - -The Instances of the Prime Transformation Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3 - Completed Instances [Core] - -The Instances of the Prime Transformation Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Prime Transformation Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.1 - Parameters [Core] - -The documents herein define the parameters of the Single Instance of the Prime Transformation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.1.1 - Agent Type [Core] - -$LaunchAgentName is a Prime Agent. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.1.2 - Custom Instance Parameters [Core] - -The documents herein define the custom parameters of the Single Instance of the Prime Transformation Primitive, if any. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.2 - Operational Process Definition [Core] - -Because the Prime Transformation Primitive is deployed solely for the one-time transformation of the Agent, no further operational process is needed post-deployment. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Prime Transformation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.2.3 - In Progress Invocations [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3 - Executor Transformation Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's instance of the Executor Transformation Primitive. See [A.2.3.4.3 - Executor Transformation Primitive](2f249be5-8edb-41e4-b429-734e1ba2cbc7). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Executor Transformation Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.1 - Global Activation Status [Core] - -`$ExecutorTransformationActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Executor Transformation Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.4 - In Progress Invocations Directory [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Executor Transformation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Executor Transformation Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Executor Transformation Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.2 - Active Instances [Core] - -The Instances of the Executor Transformation Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.3 - Completed Instances [Core] - -The Instances of the Executor Transformation Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.3.4 - In Progress Invocations [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4 - Agent Token Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instance of the Agent Token Primitive. See [A.2.3.4.4 - Agent Token Primitive](2047c361-db28-4952-a70c-83d07b562064). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Agent Token Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.1 - Global Activation Status [Core] - -`$AgentTokenActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.2.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Agent Token Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.4 - In Progress Invocations Directory [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Agent Token Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Agent Token Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Agent Token Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2 - Active Instances [Core] - -The Instances of the Agent Token Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Agent Token Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1 - Parameters [Core] - -The documents herein define the parameters of the Single Instance of the Agent Token Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.1 - Token Name [Core] - -The name of $LaunchAgentName's token is $LaunchAgentName. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.2 - Token Symbol [Core] - -The symbol of $LaunchAgentName's token is $TokenSymbol. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.3 - Genesis Supply [Core] - -The Genesis Supply of $TokenSymbol is 10 billion. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.4 - Token Address [Core] - -The address of $TokenSymbol will be specified in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.5 - Token Admin [Core] - -The token Admin will be specified in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.6 - Token Emissions [Core] - -Token emissions beyond the Genesis Supply are permanently disabled; this cannot be reverted by $LaunchAgentName Governance. Sky Governance retains the ability to revert where $LaunchAgentName is in violation of Risk Capital requirements and emissions are required by the Risk Framework. See [A.3.2](55999acf-75fe-4adf-8584-9746ef50d3e4). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.1.7 - Custom Instance Parameters [Core] - -The documents herein define the custom parameters of the Single Instance of the Agent Token Primitive, if any. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.2 - Operational Process Definition [Core] - -The documents herein define the operational processes for minting and initial distribution of the tokens from the Genesis Supply. - -- These processes will be defined in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Agent Token Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.2.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.3 - Completed Instances [Core] - -The Instances of the Agent Token Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.4.4 - In Progress Invocations [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5 - Operational Primitives [Core] - -The documents herein implement the Operational Primitives for $LaunchAgentName. See [A.2.3.5 - Operational Primitives](0192ec95-9207-480e-8c51-88d2a1da95ad). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1 - Executor Accord Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Executor Accord Primitive. See [A.2.3.5.1 - Executor Accord Primitive](88017877-3ec1-4c43-a035-6bebdf11d9bb). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Executor Accord Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.1 - Global Activation Status [Core] - -`$ExecutorAccordActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.2.1 - $OEAName Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [$OEAName Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Executor Accord Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Executor Accord Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Executor Accord Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Executor Accord Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3 - Active Instances [Core] - -The Instances of the Executor Accord Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1 - $OEAName Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the $OEAName Executor Accord Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.1 - Parameters [Core] - -The documents herein define the parameters of the $OEAName Instance of the Executor Accord Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.1.1 - Operational Executor Agent [Core] - -In the near term $OEAName will take on the functions of an Operational Executor Agent, including both Operational GovOps and Operational Facilitator roles. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.1.2 - Custom Instance Parameters [Core] - -The documents herein define the custom parameters of the $OEAName Instance of the Executor Accord Primitive, if any. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.2 - Operational Process Definition [Core] - -The documents herein define the process for the ongoing management of the $OEAName Instance of the Executor Accord Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the $OEAName Instance of the Executor Accord Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.3.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.4 - Completed Instances [Core] - -The Instances of the Executor Accord Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.1.5 - In Progress Invocations [Core] - -The in progress Invocations of the Executor Accord Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2 - Root Edit Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instance of the Root Edit Primitive. See [A.2.3.5.2 - Root Edit Primitive](78488c6b-d77f-4344-b954-476e415a2c7d). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Root Edit Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.1 - Global Activation Status [Core] - -`$RootEditActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.2.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Root Edit Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.4 - In Progress Invocations Directory [Core] - -Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Root Edit Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Root Edit Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Root Edit Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2 - Active Instances [Core] - -The Instances of the Root Edit Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Root Edit Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.1 - Parameters [Core] - -The parameters of the Root Edit Primitive are fully specified by the Operational Process Definition in [Operational Process Definition]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2 - Operational Process Definition [Core] - -The documents herein define the process for using the Root Edit Primitive to update the $LaunchAgentName Agent Artifact. Information on $LaunchAgentName governance that is unrelated to the use of the Root Edit Primitive is located at [Governance Information Unrelated To Root Edit Primitive]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1 - Routine Protocol [Core] - -The documents herein define the process for using the Root Edit Primitive to update the $LaunchAgentName Agent Artifact in routine or normal conditions (i.e., non-emergency situations). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.1 - Root Edit Proposal Submission [Core] - -The Root Edit process begins with an $TokenSymbol token holder submitting a proposal through the Powerhouse system containing a draft Artifact Edit Proposal. An $TokenSymbol 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 "$LaunchAgentName Prime" category. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.1.1 - Short-Term Transitionary Measures [Core] - -Until the Powerhouse system supports submitting Artifact Edit Proposals, $TokenSymbol token holders may submit Artifact Edit Proposals by posting them to the Sky Forum under the "$LaunchAgentName Prime" category. The title of the post must include the text "$LaunchAgentName Artifact Edit Proposal". The post must include cryptographic proof that the author controls an account holding the required percentage of the total $TokenSymbol token supply specified in [Root Edit Proposal Submission]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.2 - Root Edit Expert Advisor Review [Core] - -A future iteration of the $LaunchAgentName Artifact will specify guidelines for obtaining specialized review of proposals requiring advanced technical or financial analysis. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.3 - Root Edit Proposal Review By Operational Facilitator [Core] - -Within seven (7) days of the proposal being submitted, the Operational Facilitator must review the Root Edit Proposal for alignment. - -If 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. - -If the proposal is misaligned, the Operational Facilitator must respond to the Forum post to announce their finding and provide the reasoning for it. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.4 - Root Edit Token Holder Vote [Core] - -Where their review of the proposal results in a finding of alignment with the Sky Core Atlas and $LaunchAgentName 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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.5 - Root Edit Artifact Update [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.5.1 - Short-Term Transitionary Measures [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.1.6 - Artifact Edit Restrictions [Core] - -The $LaunchAgentName 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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.2 - Non-Routine Protocol [Core] - -The documents herein define the process for using the Root Edit Primitive to update the $LaunchAgentName Agent Artifact in non-routine conditions. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.3 - Emergency Protocol [Core] - -The documents herein define the process for using the Root Edit Primitive to update the $LaunchAgentName Agent Artifact in emergency situations. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.2.3.1 - Root Edit Voting Process In Emergency Situations [Core] - -In an Emergency Situation, as defined by the Sky Core Atlas in [A.1.8.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 "$LaunchAgentName Prime" category), unless doing so would endanger $LaunchAgentName or its users. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Root Edit Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.2.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.3 - Completed Instances [Core] - -The Instances of the Root Edit Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.2.4 - In Progress Invocations [Core] - -Because the Root Edit Primitive is deployed only once, no further Instances of the Primitive can be Invoked. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3 - Light Agent Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Light Agent Primitive. See [A.2.3.5.3 - Light Agent Primitive](44028423-2cd1-40cb-89ac-3f762b602b90). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Light Agent Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.1 - Global Activation Status [Core] - -`$LightAgentActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Light Agent Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Light Agent Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Light Agent Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Light Agent Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.2 - Active Instances [Core] - -The Instances of the Light Agent Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.3 - Completed Instances [Core] - -The Instances of the Light Agent Primitive with `Completed` Status are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.5.1.1.5.3.1.5.4 - In Progress Invocations [Core] - - The in progress Invocations of the Light Agent Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6 - Ecosystem Upkeep Primitives [Core] - -The documents herein implement the Ecosystem Upkeep Primitives for $LaunchAgentName. See [A.2.3.6 - Ecosystem Upkeep Primitives](25673fd2-76cb-4c4d-8ec6-8c489207bcfc). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1 - Distribution Requirement Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instance of the Distribution Requirement Primitive. See [A.2.3.6.1 - Distribution Requirement Primitive](0804ab13-d276-4ad9-a935-dc9f7fc2e350). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.1 - Global Activation Status [Core] - -`$DistributionRequirementActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Distribution Requirement Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.2.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Distribution Requirement Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.4 - In Progress Invocations Directory [Core] - -Because the Distribution Requirement Primitive is deployed only once, no further Instances of the Primitive can be Invoked. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Distribution Requirement Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Distribution Requirement Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Distribution Requirement Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2 - Active Instances [Core] - -The Instances of the Distribution Requirement Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Distribution Requirement Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.1.1 - Parameters [Core] - -The documents herein define the parameters of the Single Instance of the Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.1.1.1 - Terms [Core] - -$LaunchAgentName will buy back and distribute $BuybackAmount of its total token supply per year. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.1.1.2 - Custom Instance Parameters [Core] - -The documents herein define the custom parameters of the Single Instance of the Distribution Requirement Primitive, if any. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.2 - Operational Process Definition [Core] - -The documents herein define the process for the ongoing management of the Single Instance of the Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.2.1 - Routine Protocol [Core] - -This document defines the protocol for routine ongoing management of the Single Instance of this Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.2.1.1 - Process Definition [Core] - -The process to buy back and distribute $BuybackAmount of $LaunchAgentName's tokens per year will be specified in future iterations of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.2.2 - Non-Routine Protocol [Core] - -The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.2.3 - Emergency Protocol [Core] - -The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Distribution Requirement Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.2.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.3 - Completed Instances [Core] - -The Instances of the Distribution Requirement Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.1.4 - In Progress Invocations [Core] - -Because the Distribution Requirement Primitive is deployed only once, no further Instances of the Primitive can be Invoked. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2 - Market Cap Fee Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's instances of the Market Cap Fee Primitive. See [A.2.3.6.2 - Market Cap Fee Primitive](a21616f4-1611-4e0b-87b2-efbdff9f6f28). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Market Cap Fee Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.1 - Global Activation Status [Core] - -`$MarketCapFeeActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Market Cap Fee Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Market Cap Fee Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.4 - In Progress Invocations Directory [Core] - -This document contains a Directory of all prospective Instances of the Market Cap Fee Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Market Cap Fee Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Market Cap Fee Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Market Cap Fee Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.2 - Active Instances [Core] - -The Instances of the Market Cap Fee Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.3 - Completed Instances [Core] - -The Instances of the Market Cap Fee Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.2.4 - In Progress Invocations [Core] - -The in progress Invocations of the Market Cap Fee Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3 - Upkeep Rebate Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's instances of the Upkeep Rebate Primitive. See [A.2.3.6.3 - Upkeep Rebate Primitive](569e1c2b-0e69-43e7-8491-06cc5f7d2988). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.1 - Global Activation Status [Core] - -`$UpkeepRebateActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.2.1 - Single Instance Configuration Document Location [Core] - -This Instance's associated Instance Configuration Document is located at [Single Instance Configuration Document]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Upkeep Rebate Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.4 - In Progress Invocations Directory [Core] - -This document contains a Directory of all prospective Instances of the Upkeep Rebate Primitive whose Invocation is currently in progress. Invocations that are completed successfully are moved to [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Upkeep Rebate Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Upkeep Rebate Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Upkeep Rebate Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2 - Active Instances [Core] - -The Instances of the Upkeep Rebate Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1 - Single Instance Configuration Document [Core] - -The documents herein contain the Instance Configuration Document for the Single Upkeep Rebate Primitive Instance. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.1 - Parameters [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2 - Operational Process Definition [Core] - -The documents herein define the process for the ongoing management of the Single Instance of the Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.1 - Routine Protocol [Core] - -This document defines the protocol for routine ongoing management of the Single Instance of this Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.1.1 - $LaunchAgentName Holds Tokens Of Other Agents In Its SubProxy Account [Core] - -$LaunchAgentName keeps all tokens of other Agents it holds in its SubProxy account. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.1.2 - $LaunchAgentName Deducts Rebate From Ecosystem Upkeep Fees [Core] - -When paying Ecosystem Upkeep fees, $LaunchAgentName deducts the rebate from the fees it pays. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.1.3 - Operational GovOps Reviews Rebate [Core] - -Operational GovOps reviews $LaunchAgentName'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 "$LaunchAgentName Prime" category and work with $LaunchAgentName to resolve the disagreement. If Operational GovOps and $LaunchAgentName cannot resolve the disagreement, it must be escalated to Core GovOps. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.2 - Non-Routine Protocol [Core] - -The documents herein define the protocol for non-routine ongoing management of the Single Instance of this Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.2.3 - Emergency Protocol [Core] - -The documents herein define the protocol for handling emergency situations in the ongoing management of the Single Instance of this Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.3 - Data Repository [Core] - -The documents herein contain data relevant to the Single Instance of the Upkeep Rebate Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.3.1 - Initial Planning [Core] - -The materials associated with initial planning of the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.3.2 - Operational GovOps Review [Core] - -The materials associated with Operational GovOps Review during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.2.1.3.3 - Artifact Edit Proposal [Core] - -The materials associated with preparing the Artifact Edit Proposal during the Invocation of this Instance are contained herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.3 - Completed Instances [Core] - -The Instances of the Upkeep Rebate Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.6.3.4 - In Progress Invocations [Core] - -The in progress Invocations of the Upkeep Rebate Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7 - SkyLink Primitives [Core] - -The documents herein implement the SkyLink Primitives for $LaunchAgentName. See [A.2.3.7 - SkyLink Primitives](7b5d8965-a64c-4c44-b742-607f51f69d8f). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1 - Token SkyLink Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Token SkyLink Primitive. See [A.2.3.7.1 - Token SkyLink Primitive](4504d2d4-ee45-4a07-8c5b-9baf20b12e76). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Token SkyLink Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.1 - Global Activation Status [Core] - -`$TokenSkylinkActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Token SkyLink Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Token SkyLink Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Token SkyLink Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Token SkyLink Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.2 - Active Instances [Core] - -The Instances of the Token SkyLink Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.3 - Completed Instances [Core] - -The Instances of the Token SkyLink Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.7.1.4 - In Progress Invocations [Core] - -The in progress Invocations of the Token SkyLink Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8 - Demand Side Stablecoin Primitives [Core] - -The documents herein implement the Demand Side Stablecoin Primitives for $LaunchAgentName. See [A.2.3.8 - Demand Side Stablecoin Primitives](26415305-432d-423b-9553-3f325279712d). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1 - Distribution Reward Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's instances of the Distribution Reward Primitive. See [A.2.3.8.1 - Distribution Reward Primitive](e632c38f-3e4e-4c7e-acfd-b6ec45a422e6). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Distribution Reward Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.1 - Global Activation Status [Core] - -`$DistributionRewardActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Distribution Reward Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Distribution Reward Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Distribution Reward Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Distribution Reward Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.2 - Active Instances [Core] - -The Instances of the Distribution Reward Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.3 - Completed Instances [Core] - -The Instances of the Distribution Reward Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.1.4 - In Progress Invocations [Core] - -The in progress Invocations of the Distribution Reward Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2 - Integration Boost Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Integration Boost Primitive. See [A.2.3.8.2 - Integration Boost Primitive](73577399-62e4-4a83-ae11-64ef7e7b7f20). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Integration Boost Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.1 - Global Activation Status [Core] - -`$IntegrationBoostActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Integration Boost Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Integration Boost Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Integration Boost Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Integration Boost Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.2 - Active Instances [Core] - -The Instances of the Integration Boost Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.3 - Completed Instances [Core] - -The Instances of the Integration Boost Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.2.4 - In Progress Invocations [Core] - -The in progress Invocations of the Integration Boost Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3 - Pioneer Chain Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Pioneer Chain Primitive. See [A.2.3.8.3 - Pioneer Chain Primitive](4c7be4c6-44b5-407a-94ae-3d7ca7e8039c). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Pioneer Chain Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.1 - Global Activation Status [Core] - -`$PioneerChainActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Pioneer Chain Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Pioneer Chain Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Pioneer Chain Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Pioneer Chain Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.2 - Active Instances [Core] - -The Instances of the Pioneer Chain Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.3 - Completed Instances [Core] - -The Instances of the Pioneer Chain Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.8.3.4 - In Progress Invocations [Core] - -The in progress Invocations of the Pioneer Chain Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9 - Supply Side Stablecoin Primitives [Core] - -The documents herein implement the Supply Side Stablecoin Primitives for $LaunchAgentName. See [A.2.3.9 - Supply Side Stablecoin Primitives](d1142876-33c2-4e21-9339-d8711525d46f). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1 - Allocation System Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Allocation System Primitive. See [A.2.3.9.1 - Allocation System Primitive](9db14ab7-bb4b-4751-8084-843bd4359f2a). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Allocation System Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.1 - Global Activation Status [Core] - -`$AllocationSystemActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Allocation System Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Allocation System Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Allocation System Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Allocation System Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.2 - Multi-Instance Coordinator Document [Core] - -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. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.3 - Active Instances [Core] - -The Instances of the Allocation System Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.4 - Completed Instances [Core] - -The Instances of the Allocation System Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.1.5 - In Progress Invocations [Core] - -The in progress Invocations of the Allocation System Primitive are contained herein. Once an Invocation is successfully completed, its subtree will be moved to [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2 - Junior Risk Capital Rental Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Junior Risk Capital Rental Primitive. See [A.2.3.9.2 - Junior Risk Capital Rental Primitive](d8086dc0-7e77-4c6b-98c7-5fc41337a1ce). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Junior Risk Capital Rental Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.1 - Global Activation Status [Core] - -`$JuniorRiskCapitalRentalActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Junior Risk Capital Rental Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.2 - Active Instances [Core] - -The Instances of the Junior Risk Capital Rental Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.3 - Completed Instances [Core] - -The Instances of the Junior Risk Capital Rental Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.2.4 - In Progress Invocations [Core] - -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 [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3 - Asset Liability Management Rental Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Asset Liability Management Rental Primitive. See [A.2.3.9.3 - Asset Liability Management Rental Primitive](bd1f1ce5-6c31-42fc-a2aa-694acf5eb08c). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Asset Liability Management Rental Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.1 - Global Activation Status [Core] - -`$AssetLiabilityManagementRentalActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Asset Liability Management Rental Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Asset Liability Management Rental Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Asset Liability Management Rental Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Asset Liability Management Rental Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.2 - Active Instances [Core] - -The Instances of the Asset Liability Management Rental Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.3 - Completed Instances [Core] - -The Instances of the Asset Liability Management Rental Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.9.3.4 - In Progress Invocations [Core] - -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 [Active Instances]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10 - Core Governance Primitives [Core] - -The documents herein implement the Core Governance Primitives for $LaunchAgentName. See [A.2.3.10 - Core Governance Primitives](6fa54611-c744-4b9d-897d-b2a20e9cae5d). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1 - Core Governance Reward Primitive [Core] - -The documents herein contain all data and specifications for $LaunchAgentName's Instances of the Core Governance Reward Primitive. See [A.2.3.10.1 - Core Governance Reward Primitive](b22d1c08-042a-4466-94fe-9d28951e4d4a). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1 - Primitive Hub Document [Core] - -The documents herein organize all base information relevant to $LaunchAgentName's usage of the Core Governance Reward Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.1 - Global Activation Status [Core] - -`$CoreGovernanceRewardActivationStatus` - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.2 - Active Instances Directory [Core] - -This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Active`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.3 - Completed Instances Directory [Core] - -This document contains a Directory of all Instances of the Core Governance Reward Primitive with Instance status of `Completed`. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.4 - In Progress Invocations Directory [Core] - -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 [Active Instances Directory]($UUID), whereas failed Invocations are Archived in [Hub Data Repository]($UUID). - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.5 - Hub Data Repository [Core] - -The documents herein contain the Data Repository for the Primitive Hub Document. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.5.1 - Archived Invocations/Instances [Core] - -The subtrees for archived Invocations and Instances of the Core Governance Reward Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.5.1.1 - Failed Invocations [Core] - -The subtrees for failed Invocations of the Core Governance Reward Primitive are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.1.5.1.2 - Suspended Instances [Core] - -The subtrees for Instances of the Core Governance Reward Primitive with `Suspended` Status are stored here. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.2 - Active Instances [Core] - -The Instances of the Core Governance Reward Primitive with `Active` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.3 - Completed Instances [Core] - -The Instances of the Core Governance Reward Primitive with `Completed` Status are stored herein. - -###### A.6.1.1.$LaunchAgentDocNumber.2.1.10.1.4 - In Progress Invocations [Core] - -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 [Active Instances]($UUID). - -##### A.6.1.1.$LaunchAgentDocNumber.3 - Omni Documents [Core] - -The documents herein define $LaunchAgentName's strategic intent and operational processes relating to infrastructure inherited from Sky Core, activities unrelated to Sky Primitives, or activities spanning multiple Sky Primitives. - -###### A.6.1.1.$LaunchAgentDocNumber.3.1 - Governance Information Unrelated To Root Edit Primitive [Core] - -The documents herein specify $LaunchAgentName governance information that is unrelated to the use of the Root Edit Primitive. The governance process for updating the $LaunchAgentName Artifact is specified in the Root Edit Primitive above at Root Edit Primitive. - -###### A.6.1.1.$LaunchAgentDocNumber.3.1.1 - Sky Forum [Core] - -$LaunchAgentName uses the Sky Forum for governance-related discussion. Posts should use the "$LaunchAgentName Prime" category. - -###### A.6.1.1.$LaunchAgentDocNumber.3.1.2 - Sky Ecosystem Emergency Response [Core] - -The documents herein specify $LaunchAgentName's emergency response protocol in situations that impact the entire Sky Ecosystem. This protocol will be specified in a future iteration of the $LaunchAgentName Artifact. - -###### A.6.1.1.$LaunchAgentDocNumber.3.1.3 - Agent-Specific Emergency Response [Core] - -The documents herein specify $LaunchAgentName's emergency response protocol in situations solely impacting $LaunchAgentName versus the broader Sky Ecosystem. This protocol will be specified in a future iteration of the $LaunchAgentName Artifact. \ No newline at end of file