1---2name: draft-notice-of-arbitration-scenario-023task_id: arbitration-international-dispute-resolution/draft-notice-of-arbitration/scenario-024description: Ensures a notice of arbitration treats service availability and data-loss allegations as distinct claims, states an accurate incident timeline, includes the governing law, and references the filing fee.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-notice-of-arbitration-scenario-028---910# Skill: ICDR Notice of Arbitration (Cloud Services SLA Breach)1112## 1. Subject-matter triage (only if applicable)1314- Draft a standalone notice of arbitration, not a memo or issue list.15- Treat the service outage allegation and any data-loss allegation as potentially distinct claims unless the source documents clearly collapse them into one theory.16- Use the operative contract, correspondence, damages memo, and data records as the hierarchy of facts; if they conflict, privilege the most authoritative operational record.17- If the source set contains one incident only, say so expressly and frame all claims around that single event rather than implying multiple incidents.1819## 2. Failure modes the skill is correcting2021- Merges uptime failure and data-loss harm into one undifferentiated claim, obscuring different liability theories, proof, and damages.22- States the incident chronology loosely instead of anchoring it to the monitoring record and related correspondence.23- Omits the agreement’s governing law or treats it as background rather than a required notice element.24- Fails to reference the concurrent filing fee submission.25- Mixes contractual breach allegations with damages assumptions without tying each to a source document.26- Uses broad narrative instead of a clean arbitration initiation that identifies the parties, contract, dispute, relief, and arbitrator proposal.2728## 3. Legal frameworks / domain conventions that apply2930- ICDR notice practice: identify the parties, the arbitration agreement, the contract at issue, the nature of the dispute, the relief sought, and the requested arbitrator configuration.31- Contract interpretation: plead the claims under the agreement’s express service levels, remedies, limitation clauses, and governing law, rather than generic service complaints.32- Distinct harm framing: service availability breach and data-loss breach may be separate contractual injuries measured by different standards; plead them separately when the record supports that distinction.33- Timeline accuracy: use the monitoring data and any incident log as the primary source for start time, duration, scope, and restoration; avoid rounded or inconsistent times.34- Governing law citation: state the governing law clause from the master agreement or equivalent operative contract.35- Arbitrability and notice sufficiency: the notice should be specific enough to put the respondent and administering institution on notice of the contractual dispute and the relief demanded.36- Liability framing: acknowledge any contractual liability cap or damages limitation only to the extent it is relevant to the notice and consistent with the source documents.37- Supporting authority: cite the rule or clause that supports each procedural statement you make; do not state procedural or substantive points without naming the governing source.3839## 4. Analytical scaffolds4041- Identify the parties exactly as they appear in the contract and notice them in their capacity under the agreement.42- State the arbitration agreement and administering rules invoked, then identify the contract(s) and provisions in dispute.43- Plead the service-availability claim by linking the outage facts to the contractual uptime or performance commitment.44- If data was lost or corrupted, plead that as a separate claim only if the source documents support a distinct data-protection, backup, restoration, or recovery commitment.45- Use the authoritative incident record for:46 - start time47 - end time or restoration time48 - total duration49 - affected services or accounts50 - any separately affected data sets or records51- Track each claimed harm to its own factual predicate and damages theory.52- When the damages memo gives ranges, assumptions, or valuation-based figures, carry them forward as qualified estimates rather than converting them into hard facts.53- If the contract contains a recovery objective or similar data-restoration standard, frame the breach against that standard rather than against uptime metrics.54- State the requested relief in arbitration terms: monetary damages, fees and costs, and any other relief the contract permits.55- State the number of arbitrators requested and any appointment proposal only if the contract or rules require or permit it.56- Include the governing law clause verbatim only if necessary for accuracy; otherwise summarize it faithfully.57- Include the filing-fee reference in the notice so the filing is procedurally complete.5859## 5. Vertical / structural / temporal relationships (only if applicable)6061- Separate the chronology into pre-incident baseline, outage period, restoration period, and post-incident consequences.62- Distinguish service interruption from downstream data effects; do not infer data loss merely from downtime.63- If multiple systems, regions, customer cohorts, or data categories are implicated, describe them separately rather than as a single aggregate event.64- If the damages memo distinguishes direct loss, mitigation cost, and projected or lifetime value effects, keep those categories separate and qualify any forward-looking assumption.65- If the contract’s liability cap or exclusion clause applies differently to service credits, direct damages, or data incidents, note that structure without performing arithmetic in the notice.6667## 6. Output structure conventions6869- Produce a formal Notice of Arbitration suitable for ICDR filing.70- Include, in conventional order:71 - caption / party identification72 - arbitration agreement and governing contract73 - brief statement of the dispute74 - separate claim sections for service availability and, if supported, data-loss or restoration failures75 - incident chronology76 - damages summary with clearly qualified figures from the memo77 - governing law78 - requested relief79 - arbitrator proposal80 - filing-fee statement81 - signature block and service language as appropriate82- Keep the notice factual, concise, and source-driven; avoid argument that belongs in a later statement of claim.83- Preserve internal consistency across the narrative, dates, service names, and claimed harms.84- Before finalizing, verify that the draft includes every operative filing element and that the claims are separated only to the extent the record supports separation.