Acceptance criteria:

• There is an open communication channel (discussions board / zulip / discord / ???) (it has to be documented)
• Zero-maintenance (automate out nearcore releases with canary testing ensuring that the new release produces the same JSON dumps on S3 as the previous release)
• Zero-downtime (define redundancy, handle potential errors with retries whenever possible)
• The JSON dumps format is fully controlled by NEAR Lake (instead of being at mercy of nearcore types)