Launch Gate - clear the launch before it ships: what applies, how bad, what evidence

Paste one proposed launch - a product feature, a marketing programme, a data-sharing arrangement, a new vendor, a market entry - plus a short key-and-value facts block, and run three lanes over that one work object. The scoping lane names which regulations, frameworks and internal approvals apply, cites the operative provision for each, and positively rules out the regimes a reader would expect but that do not bite. The risk lane classifies the exposure on a severity-by-likelihood grid with mitigation, residual band and an explicit escalation call. The readiness lane produces the audit-readiness register: requirement, provision, control, evidence artifact, owner role, status and how an auditor would test it, with the gaps ranked and the counts recomputed from the rows. A free in-browser scan parses the facts block as real key-and-value input, reads the brief for jurisdictions and data categories it does not declare, places the frameworks by rule, derives the approval gates, reads each processor's agreement, computes the days to launch against the gates still open, and raises around fifty deterministic flags that the model must then account for one by one. Each lane can start from the previous lane's output. A derived work built on three agent skills: @anthropics/compliance-check, @anthropics/legal-risk-assessment and @anthropics/compliance-tracking, all published under @anthropics/knowledge-work-plugins. A working analysis for a named reviewer - not legal advice, and not a clearance.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.