Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds docs/reports/week-2/problem.md, the Week 2 problem section covering scale, cost evidence, non-cost reasons, continued AWS use, and the risks Dropbox accepted.
Closes #12
Why
The Week 2 case analysis needs a source-backed account of why Dropbox built Magic Pocket. The report distinguishes disclosed facts from our calculations and inferences, including the absence of a public storage, request, and egress cost breakdown.
How to check it
Read docs/reports/week-2/problem.md and compare its five main sections with the issue checklist. Every substantive external claim has a Source Log ID.
Checklist