Atlas Edit Proposal · PR #277
121 documents changed · 117 edited, 3 new, 5 removed, 13 renumbered
Update the Monthly Settlement Cycle Process — Removes the Core Council Risk Advisor's Independent Calculation from the Monthly Settlement Cycle; amounts are now resolved through the Operational Executor Agent's Initial Calculation, the Prime-Agent dispute process, and Core GovOps's Final Calculation. Also aligns the documented process with practice: the first Initial Calculation begins the Monthly Settlement Cycle forum thread, and the last Initial Calculation includes the Core Council and Aligned Delegates Buffer amounts.
Add A Timeliness Requirement To Aligned Delegate Voting Participation — Adds that, for Executive Votes, a vote counts toward an Aligned Delegate's participation only where it is cast within three (3) business days of the vote being posted.
Clarify Genesis Capital Phase-Out Is Not A Repayment To Sky — Clarifies that Genesis Capital phase-out reduces an Agent's Genesis Capital through Phased-Out Genesis Capital and involves no repayment or transfer of capital from the Genesis Agents to Sky.
Add The Canonical Sky Frontier Foundation Multisig Address — Records the Sky Frontier Foundation's canonical multisig address in its definition as a standing source of truth for verifying transfer destinations.
Reduce The Instance Financial CRR For JAAA On Avalanche — Reduces the Instance Financial CRR for JAAA on Avalanche from 2.1% to 1.6%.
Add Off-Chain Parameters To The Osero SparkLend USDS Instance — Sets the Osero SparkLend USDS Instance's Maximum Exposure to 5,000,000 USDS and its Capital Ratio Requirement to 100%.
Update Spell Validation And TechOps Communications To The Sky Forum And Slack — With the Spell address handover now on the Sky Forum, points Spell validators to the Forum handover thread for context, adjusts public validation-issue reporting to the Sky Forum to match, and moves the TechOps whitelisting request to Slack. Because validation issues are now reported publicly, this also removes the separate escalation route for a potentially malicious Core Facilitator — a public Forum report already reaches Aligned Delegates and wider Sky Governance directly.
Generalize The Junior Risk Capital Rental Primitive Into The Risk Capital Rental Primitive — Broadens the Primitive to cover rental of both Junior Risk Capital and Originated Senior Risk Capital between Prime Agents, where it previously covered only Junior Risk Capital.
Update Stale URLs — Updates Chainlog and public-dashboard references from sky.money sub-sites to their canonical skyeco.com equivalents.
Move SkyLink Bridges From Governance Scope To Protocol Scope — Relocates the SkyLink Bridge documentation from the Governance Scope to a new Section under the SkyLink Article in the Protocol Scope. The documentation is moved as-is, with no content changes.
Edit scope
1 edited document
The Sky Frontier Foundation is a foundation that supports the innovation, development, and acceleration of the Sky Ecosystem. Its mandate is to fund public goods infrastructure and self-sustainable activities to support long-term ecosystem growth.
The Sky Frontier Foundation's multisig address is 0xca5183FB9997046fbd9bA8113139bf5a5Af122A0.
Edit scope
1 edited document, 1 new document
Aligned Delegates are required to maintain a voting participation rate of at least seventy-five percent (75%) over the past six (6) months in all votes they are eligible to cast as an Aligned Delegate. Failure to meet this standard is a Tier 1 (Procedural) breach.
Voting participation is measured from the date of formal recognition by the Core Facilitator. The participation requirement applies only to votes for which SKY tokens are delegated to the Aligned Delegate. For Executive Votes, a vote counts toward this participation only where the Aligned Delegate casts it within the period specified in Vote Timeliness.
Following the issuance of a Tier 1 (Procedural) breach for failure to meet this requirement, the Core Facilitator will not issue a further Tier 1 (Procedural) breach solely because the Aligned Delegate's participation rate over the past six (6) months remains below seventy-five percent (75%), provided that the Aligned Delegate has participated in at least seventy-five percent (75%) of the votes for which they were eligible after the most recent breach was issued. A further Tier 1 (Procedural) breach on this basis is issued only where the Aligned Delegate fails to meet the seventy-five percent (75%) participation requirement in the votes for which they were eligible after the most recent breach was issued. The Core Facilitator evaluates voting participation for this purpose on a monthly basis.
A vote counts toward an Aligned Delegate's voting participation only where the Aligned Delegate casts it within three (3) business days of the Executive Vote being posted to the voting portal. A vote cast after this period does not count toward the Aligned Delegate's participation for that vote.
Edit scope
1 edited document
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). For Executive Votes, a vote counts toward this participation only where the Ranked Delegate casts it within the period specified in Vote Timeliness.
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.
Edit scope
1 edited document
The Chainlog is an on-chain, governance-managed registry that records the official addresses of Sky’s core smart contracts. Each contract entry in the Chainlog is identified by a unique key ("Chainlog key"), which is used to reference the contract in documentation, governance actions, and integrations. It serves as the single source of truth for contract addresses in the protocol. The Chainlog is available at https://chainlog.sky.money/https://chainlog.skyeco.com/. Updates to the Chainlog are defined as housekeeping items (see Definition Of Housekeeping Items) and can be included directly in an Executive Vote (see Process for Adding Housekeeping Item In Executive Vote).
Edit scope
1 edited document
The Prime Agent must create a publicly available information dashboard through a platform such as Dune showing, at a minimum, the current exposure to the Interim Deployment. This requirement is waived if the Core Council Risk Advisor has already included the Interim Deployment in the publicly available information dashboard at https://info.sky.moneyskyeco.com.
Edit scope
1 edited document
The Governance Point must request that TechOps Services whitelist the Spell address provided by the Spell Team. This support request is submitted in the Discord channel #techops-requestto TechOps Services via Slack. The message should include a request to whitelist the Spell and must specify the Spell address.
Edit scope
2 edited documents
Retrieving values from the Chainlog smart contract is mandatory during the validation of Spells.
The most secure method for retrieving values is to query the Chainlog directly using multiple sources, such as Foundry’s cast tool, the Etherscan blockchain explorer, and the IPFS link accessible on the official Chainlog for Sky at https://chainlog.sky.money/https://chainlog.skyeco.com/, ensuring that the returned addresses match across all platforms.
The use of Discord is not required during Spell verification, as it primarily serves as a platform for public communication between the Core Facilitator and members of the current Spell Team Spell address handover and its associated reviewer verifications are recorded in the Sky Core Executive Vote Address Handover Thread on the Sky Forum (https://forum.skyeco.com/t/sky-core-executive-vote-address-handover-thread/27995), which Spell validators should consult for this context.
However, using Discord is highly recommended for Spell validators, as the communication history in the #new-Spells channel may provide valuable context or additional information for the validation process.
Edit scope
1 edited document
Publicly reporting issues found during Spell validation is the recommended method of issue reporting. Issues reported publicly may be reported to the Core Facilitator using the "#new-Spells" channel in the Sky Builder Discord Group. If the Core Facilitator may be acting maliciously, issues should be reported to Aligned Delegates and wider Sky Governance using the "#governance" channel in the Sky Builder Discord Group. In cases where this is not possible, posts made to the Sky Forum may be used; however, these should be used as a last resort as they will likely cause a slower response timeon the Sky Forum.
Edit scope
1 edited document
The current Sky Primitives are:
Edit scope
1 edited document
The Sky Core Required Risk Capital (RRC) Dashboard serves as the official system for determining and disseminating RRC figures for Prime Agents and their Allocation System Primitive Instances.
Prior to the full operational deployment of the Powerhouse system, Prime Agents must utilize the Sky Core RRC Dashboard as the authoritative source for their official Instance Total RRCs and Aggregate RRC. Data from this source is to be used for all internal TRC management, required reporting and compliance assessments.
The Sky Core RRC Dashboard is located at https://info.sky.money/required-risk-capitalhttps://info.skyeco.com/required-risk-capital.
Edit scope
1 edited document
The Junior Risk Capital Rental Primitive is a mechanism enabling Prime Agents to rapidly rent Junior Risk Capital from each other, ensuring that capital gets deployed to where the best opportunities are. The Primitive facilitates the rental of both Junior Risk Capital, as specified in Prime-External Junior Risk Capital (SEJRC), and Originated Senior Risk Capital, as specified in Originated Senior Risk Capital (OSRC) Rental Implementation.
Edit scope
6 edited documents
Within seven (7) calendar days of the end of each month, each Operational Executor Agent and the Core Council Risk Advisor replies to the Monthly Settlement Cycle Post with their calculation of the net amounts due to or from Prime Agents as specified in the documents hereinposts on the Sky Forum a calculation of the net amounts due to Sky from, or from Sky to, the Prime Agents that it has an Executor Accord with (the "Initial Calculation"), under the "Sky Core" category using the monthly-settlement-cycle tag. The first Initial Calculation posted for a given month begins that month's thread for the Monthly Settlement Cycle (the "Monthly Settlement Cycle Post"), and any further Initial Calculations for that month are posted as replies to it. The last Initial Calculation posted for a given month must also include calculation of the amounts to be transferred to the Core Council and Aligned Delegates Buffers (see Step 1: Security And Maintenance). The Initial Calculation must contain reasonable supporting detail. The required contents of the Initial Calculation will be further specified in a future iteration of the Atlas.
Within seven (7) calendar days of the end of each month, each Operational Executor Agent replies to the Monthly Settlement Cycle Post with a calculation of the net amounts due to or from the Prime Agents that it has an Executor Accord with (the "Initial Calculation"). The Initial Calculation must contain reasonable supporting detail. The required contents of the Initial Calculation will be further specified in a future iteration of the Atlas.
Within seven (7) calendar days of the end of each month, the Core Council Risk Advisor replies to the Monthly Settlement Cycle Post with their own independent calculation of the net amounts due to or from each Prime Agent (the "Independent Calculation"). The Independent Calculation should also include calculation of the amounts to be transferred to the Core Council and Aligned Delegates Buffers (see Step 1: Security And Maintenance). The Independent Calculation must contain reasonable supporting detail. The required contents of the Independent Calculation will be further specified in a future iteration of the Atlas.
By the end of each month, Core GovOps creates a post on the Sky Forum to organize all communications regarding the Monthly Settlement Cycle for that month (the "Monthly Settlement Cycle Post"). The post must be made under the "Sky Core" category using the monthly-settlement-cycle tag.
Within twelve (12) calendar days of the end of each month, Core GovOps replies to the Monthly Settlement Cycle Post with the final calculation of the net amounts due to or from each Prime Agent (the "Final Calculation"). The Final Calculation should also include the final amounts to be transferred to the Core Council and Aligned Delegates Buffers (see Step 1: Security And Maintenance). If there are any Disputed Amounts (see Disputed Amount), then Core GovOps must resolve them. Core GovOps must work with the relevant Operational Executor Agent, relevant Prime Agents, and the Core Council Risk Advisor and relevant Prime Agents to reach a mutually acceptable resolution and may consult other parties to the extent it deems advisable. Where amounts settled are subsequently determined to be incorrect, they are trued up in a subsequent Monthly Settlement Cycle (see True Up In Subsequent Monthly Settlement Cycle).
Core GovOps makes the final decision in resolving differences between the Initial Calculation and the Independent Calculationany Disputed Amounts. The Final Calculation must specify the Final Amount and contain reasonable supporting detail. The required contents of the Final Calculation will be further specified in a future iteration of the Atlas.
The net amount due to or from a Prime Agent in an Initial Calculation is an Agreed Amount if the percentage deviation between the Initial Calculation and the Independent Calculation is less than or equal to the Allowed Deviation (see Allowed Deviation). The percentage deviation is calculated as the absolute value of the difference between the net amount in the Initial Calculation and the net amount in the Independent Calculation, divided by the average of the two amounts, multiplied by 100%. The net amount due to or from a Prime Agent in an Independent Calculation is also an Agreed Amount if there is no Initial CalculationPrime Agent does not post a Dispute Notice with respect to that amount within the period specified in Disputes By Prime Agents.
A Prime Agent may dispute the calculation of the net amount due to or from it (a "Dispute Notice"). The Dispute Notice must be posted as a reply to the Monthly Settlement Cycle Post within five (5) calendar days of the posting of the Initial Calculation or Independent Calculation being disputed. The Dispute Notice must specify the errors in the Initial Calculation or Independent Calculation and the Prime’s own calculation of the net amount due to or from it. The required contents of the Dispute Notice will be further specified in a future iteration of the Atlas.
Core GovOps may at its discretion resolve the differences between the calculationsdispute using the process specified in Final Calculation By Core GovOps. Alternatively, Core GovOps may elect to determine the correct amount and true up any differences in the nexta subsequent Monthly Settlement Cycle as specified in True Up In Subsequent Monthly Settlement Cycle. In either case Core GovOps must post its decision as a reply to the Dispute Notice.
The Allowed Deviation is the maximum allowed deviation, on a percentage basis, between the net amount due to or from a Prime Agent in the Initial Calculation and Independent Calculation before resolution of these differences is required. It recognizes that if the Initial Calculation and Independent Calculation are truly developed independently then differences in methodology are likely to result in small deviations.
The current value of the Allowed Deviation is 1%.
If the amounts of any payments included in the Sky Core Executive Vote (see Settlement Through Sky Core Executive Vote) are subsequently determined to be incorrect, adjustments are included in the nexta subsequent Monthly Settlement Cycle to ensure that each party pays the amount it owes or receives the amount to which it is entitled.
Core GovOps must prepare a statement specifying the errors, the correct amounts, and the adjustments needed (the "Correction Calculation"). The Correction Calculation must be posted to the Sky Forum under the "Sky Core" category with the monthly-settlement-cycle tag. The required contents of the Correction Calculation will be further specified in a future iteration of the Atlas.
Edit scope
1 edited document
The Core Council Risk Advisor must develop toolingmust ensure tooling is developed to allow the net amount due from each Prime to Sky each month under the Simplified Profit And Loss Calculation to be computed automatically.
Edit scope
1 edited document
The Core Council Risk Advisor must develop automated toolingmust ensure automated tooling is developed for calculating the net amount due from each Prime to Sky each month, incorporating the Virtual Base Rate.
Edit scope
1 edited document
The Core Council Risk Advisor must updatemust ensure the tooling specified in Automation Of Monthly Settlement Cycle Calculation Including Virtual Base Rate is updated to reflect the onchain accrual of the Base Rate.
Edit scope
1 edited document
Grove and Spark agree to a bilateral revenue share, up to 40% maximum with JRC rental, see Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
Edit scope
1 edited document
Grove agrees to rent to Spark 50% of the Required Risk Capital associated with Spark’s investments in USDe and sUSDe as a Junior Risk Capital Rental. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
Edit scope
1 edited document
SEJRC is JRC rented from another Prime Agent via the Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive. The capital remains in the lender's treasury but counts towards the borrower's JRC amount. SEJRC is represented by a registered Ecosystem Accord signifying that a specified amount of the lending Agent's JRC (held within the lender's treasury) is designated to count towards the borrowing Agent's JRC requirement for the duration and terms specified in the Accord.
Edit scope
1 edited document
Senior Risk Capital (SRC) is protected from losses relative to Junior Risk Capital. Senior Risk Capital only begins to absorb losses after Junior Risk Capital has experienced 100% losses and absorbs 100% of losses thereafter.
Senior Risk Capital can be originated from Sky Core on a monthly basis as part of the Monthly Settlement Cycle; Prime Agents can also rent Senior Risk Capital from each other via the Risk Capital Rental Primitive.
Edit scope
1 edited document
The following Instance Financial CRRs apply to specific assets listed:
Edit scope
1 edited document
The implementation of the SEJRC rental system is defined as a Sky Primitive, specifically, the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
Edit scope
1 edited document
The operational process for inter-Prime Agent OSRC risk-capital rentals is defined herein. SEJRCOSRC rentals are facilitated through the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
Edit scope
1 edited document
In the near term, the Core Council Risk Advisor must develop a tool to automatically detect and report failures by Prime Agents to maintain the Minimum Actively Stabilizing Collateral. Each violation by a Prime Agent must be reported within 24 hours to the following parties:
In addition, the Core Council Risk Advisor must include a summary of all such violations in the Independent Calculation it prepares as part of each Monthly Settlement Cycle. See Independent Calculation By Core Council Risk Advisor On Behalf Of Core Council.
Edit scope
1 edited document
As the ecosystem matures and Aggregate Backstop Capital (see Aggregate Backstop Capital) reaches a sufficient level, Genesis Capital will phase out. The documents herein define the eligibility conditions and phase-out amounts.
Phase-out is effected by increasing an Agent's Phased-Out Genesis Capital (see Phased-Out Genesis Capital), which reduces the Agent's Eligible Genesis Capital and therefore its Genesis Capital, progressively reducing the Genesis Capital subject to the Genesis Capital Backstop (see Genesis Capital Backstop). Phase-out does not involve any repayment or transfer of capital from the Genesis Agents to Sky.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Spark’s Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Spark’s usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Grove’s Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Grove’s usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Keel’s Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Keel’s usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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, whereas failed Invocations are Archived in Hub Data Repository.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Skybase's Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Skybase's usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Obex's Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Obex's usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Pattern's Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Pattern's usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
2 new documents
The Maximum Exposure for this Instance is 5,000,000 USDS.
The Capital Ratio Requirement for this Instance, as specified in Capital Ratio Requirement, is 100%.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Osero's Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Osero's usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
Edit scope
11 edited documents
The documents herein contain all data and specifications for Launch Agent 7's Instances of the Junior Risk Capital Rental Primitive. See Junior Risk Capital Rental PrimitiveRisk Capital Rental Primitive.
The documents herein organize all base information relevant to Launch Agent 7's usage of the Junior Risk Capital Rental Primitive.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Active.
This document contains a Directory of all Instances of the Junior Risk Capital Rental Primitive with Instance status of Completed.
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.
The subtrees for archived Invocations and Instances of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for failed Invocations of the Junior Risk Capital Rental Primitive are stored here.
The subtrees for Instances of the Junior Risk Capital Rental Primitive with Suspended Status are stored here.
The Instances of the Junior Risk Capital Rental Primitive with Active Status are stored herein.
The Instances of the Junior Risk Capital Rental Primitive with Completed Status are stored herein.
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.
These documents had their identifier changed without modifying their content. Listed for audit; not shown in the Document Changes section above.
