<aside> ⚠️ This document is currently in flux, as we’re figuring out the set of LabWeek 2023 Deliverables. It is based on a previous understanding of priorities, as described in Prioritise Station and Meridian Design Doc 03: Evaluation dissected.
</aside>
https://starmap.site/roadmap/github.com/filecoin-station/roadmap/issues/1
flowchart LR
PN[Non-technical preparation]
subgraph PT[Technical preparation]
B[Boost]
end
M[Measure]
E[Evaluate]
R[Reward]
M --> E
E --> R
B --> M
PN --> R
Unless resourcing or dependencies on external teams inform us otherwise, the milestones Measure, Evaluate and Reward should be implemented sequentially.
The preparation milestones can happen in tandem, as visualized above. Eventually during Measure, Technical preparation: Boost will need to have been completed. Eventually during Reward, Non-technical preparation will need to have been completed.
M1-M3 have the same deadline as there’s a lot of uncertainty on the Boost part:
There’s an alternative way to structure this: Target the existing frisbii server as an SP in all of the milestones, then add a milestone for proper Boost support.