[MEGA] Rule 17Ad-7(f)(6)(i) interwoven (a–d) observations backup custodian

[JFWooten4]

Right now we do not have anything in place for subsubsec (6)(i). We should assess the materials going forward with CRON work, which would qualify under this notice regime. It will likely implicate the play around validator data replication, which gets to the DRS processes after the donation.

[JFWooten4]

I started open-sourcing the access permissions in blocktransfer/CRON-jobs#5. If we want to use AWS for the record custodianship with their triplicate replication on the East 2 locale, I think the arrangements would use an account-level addendum like in the examples for #18 (comment).

They require an NDA to view those agreements, which I would like to avoid at all costs. That would make it tougher to document fully and collaborate on here. Luckily, those existing arrangements (i) do not apply to our workflows and (ii) actually have AWS itself acting as the Letter of Undertaking filing, which radically simplifies things compared to the existing #19 flow.

I'll start working on this more thoroughly and make an issue for it after the S-P work. I could easily see a sub-account that agrees to this. Then just that account operates what would be a simple new repo of functions linking into IL and observing the on-chain data like how it is done manually atm.