majesticlabs-dev Launch Legal Checklist
Boundary
Provide general information only, not legal advice. Do not recommend an entity, assert legal readiness, or draft terms, contracts, privacy policies, employment documents, equity documents, or regulated claims.
Required Inputs
- Jurisdictions, entity status, business model, and customer type
- Offer, claims, payment flow, contracts, and refund handling
- Personal or sensitive data collected, stored, shared, and retained
- Workers, contractors, intellectual property, licenses, insurance, and regulated exposure
Workflow
- Define the launch scope, jurisdictions, customer type, and material transactions.
- Inventory registration, tax, licensing, permits, insurance, and entity questions without selecting an answer.
- Map data flows, consent, security, retention, processors, and user-rights questions.
- List contract, refund, IP, employment, advertising-claim, and accessibility issues.
- Separate general administrative tasks from decisions requiring qualified counsel, accountants, security, or domain specialists.
- Prioritize by downside, irreversibility, timing, and dependency.
- Return missing evidence and the next action sequence. A checklist never grants clearance.
Output
- Scope and jurisdiction assumptions
- General-information checklist
- Counsel-required and specialist-required questions
- Missing evidence
- Prioritized next-action sequence
Quality Gate
- Language says qualified counsel, never approved or legally ready.
- No document is drafted as legal advice.
- Jurisdiction and regulated exposure are explicit.
- Material unknowns remain blockers, not implied clearance.