Recover a consistent service before the business deadline

Edit recovery-plan.json using distinct restores {dataset,copy,point,journals,start,team} and jobs {id,start,team}. The report has services keyed by service ID with readyAt,recoverableCut,dataLoss,businessResumedAt, plus totalCost. Use integers or null for genuinely unrecovered fields. Starts are elapsed recovery minutes; a copy/journal must be available at or before 120+start, verified and independent of the failed primary. Select the correct dataset. Replicas allow only listed rewindPoints and no journals. A vault snapshot permits its own point or an ordered, gap-free journal chain tied to that exact baseCopy. Each journal starts where the previous one ends; only the final segment may be truncated to the selected point, which must lie after its start. Unchecked or unavailable evidence cannot establish a usable cut. Restore duration is copy minutes plus every selected journal's full minutes; cost includes all selected copy/journal and scheduled job costs. Every job/restore consumes one permitted team unit throughout [start,end); capacity and horizon 24 apply. Prerequisites must finish before a child starts. keys enables every restore and network; checkout needs network and all three datasets; verify follows checkout. Source flags cannot be edited. Orders/documents need the same usable cut, while the service cut is the oldest usable point across all three datasets. Data loss is 120 minus that cut. Verified service readiness is verify's actual finish after valid work, not checkout's finish or backup freshness. Meet RTO10 and RPO5 separately, then add the supplied two business reprocessing minutes and meet MTD11. Budget15 applies to the complete selected plan. Report derived values, including null readiness when evidence, dependencies or capacity prevent service recovery. Retain partial work and repair the failing condition without Reset.