こんにちはTAG!

I'm requesting a TAG review of:

• Name: Storage Corruption Review
• Specification URL: None yet
• Explainer (containing user needs and example code)¹: https://github.com/wanderview/storage-corruption-reporting/blob/master/explainer.md
• GitHub issues (if you prefer feedback filed there): https://github.com/wanderview/storage-corruption-reporting/issues
• Tests: None yet
• Primary contacts (and their relationship to the specification): @wanderview

Further details:

• Relevant time constraints or deadlines: [please provide]
• I have read and filled out the Self-Review Questionnare on Security and Privacy. The assessment is here.
• I have reviewed the TAG's API Design Principles
• The group where the work on this specification is: Planning to discuss at WebApps WG at TPAC.

We recommend the explainer to be in Markdown. On top of the usual information expected in the explainer, it is strongly recommended to add:

• Links to major pieces of multi-stakeholder review or discussion of this specification:
• Links to major unresolved issues or opposition with this specification:

You should also know that...

[please tell us anything you think is relevant to this review]

We'd prefer the TAG provide feedback as (please select one):

• open issues in our GitHub repo for each point of feedback
• open a single issue in our GitHub repo for the entire review
• leave review feedback as a comment in this issue and @-notify [github usernames]

---

Please preview the issue and check that the links work before submitting. In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document.

¹ For background, see our explanation of how to write a good explainer.