Agenda
- Explain the methodology/purpose
- Failure Modes and Risks
- Walk through the items flagged for “For FOC Leads”
- Communication
- Likely skip. This area will have been covered by “Failure Modes and Risks” section.
- Change Management
- Walk through the items flagged for “For FOC Leads”
- Other topics
- When would we like to get FOC components enrolled in FF Bug Bounty program? After M4.1 or M4.2?
- Operational readiness going forward.
- Thinking to start with a weekly dashboard review, where we take one of our dashboards and have the owner present and we collect feedback on it.
Status
- 2026-03-16: finished adding all the actions
- 2026-03-15: added recording, AI meeting notes, and started compiling actions
- 2026-03-13: meeting was had
Actions
After the meeting, collect the full set of followup actions we agree to take, and delineate between which ones are needed for M4.1 vs. M4.2 vs. later. These will likely get turned into GitHub issues so not lost.
M4.1:
- https://github.com/FilOzone/tpm-utils/issues/19
- [x] Get Tippy and Beck in Builder telegram channels so they can be made aware if there are issues going on with SPs
- [x] Audit membership in
#foc-wg-alertsadding: FOC WG engineers, TSCs, FOC leadership (Molly, etc.).
- Expand dealbot alarms to catch if 50% of approved SPs start failing a given check type. This is tracked in https://github.com/FilOzone/dealbot/issues/89.
- Check our confidence level that that User funds cannot be stuck or drained without a recovery path (i.e., if a bug exists, you can still allow users to withdraw funds - maybe with complex migrations, but feasible.)