Law Firm

Origin

Cross-jurisdictional formation, fundraising, and dissolution have been a partner-time tax for decades. The same operations — a Delaware C-corp, a 409A, a Reg D 506(c) raise, a Cayman feeder, a Singapore tax filing — get hand-derived every time. The cost is paid in calendar weeks; the value is paid to whoever memorized the playbook.

Problem

What's needed is not a document-search tool. What's needed is an operations engine: lawpacks that name a multi-step legal procedure (incorporate, fundraise, dissolve, migrate), encode the steps as YAML, and execute against the registrars, e-signers, and compliance trackers that operate the jurisdiction.

Approach

YAML-driven lawpacks define each multi-step operation explicitly. The engine reads the pack, generates the documents, files with the right registrar, dispatches e-sign, and tracks the compliance windows that follow. Production matrix: six US states (Delaware, Wyoming, California, New York, Texas, Florida) and four international jurisdictions (ADGM in Abu Dhabi — FSRA-regulated, 0% corporate tax, English common law; Cayman Islands — CIIPA, BOSS register; BVI — cheaper alternative for sub-$25M AUM holdcos; Singapore — ACRA/MAS, VCC for funds). The deeper engine reaches all fifty US states plus DC under the same framework.

Methodology

The lawpack is the law's executable form. A new operation is a new file, partner-reviewed, version-controlled, and applied through the same engine that runs the others. Each operation × jurisdiction is an explicit lawpack with sanctions screen, document generation, registrar filing, and per-step configuration. Concrete operations live in production — entity formation and dissolution (full teardown including beneficial-ownership reporting), foreign qualification, employee and contractor onboarding (with the appropriate state-by-state form stack), distributions and tax filings, financing flows (SAFE rounds, priced rounds with valuation stack, convertible notes), advanced operations including equity compensation, IP assignment, and banking. A trap-warning system flags documented jurisdiction traps automatically at execution time.

Selected milestones

• Production matrix spans the named US states and the four international jurisdictions
• Tier 1 entity-lifecycle operations operational across the production matrix
• Tier 2 financing flows live: SAFE rounds, priced rounds, convertible notes
• Tier 3 advanced operations live: equity compensation, IP assignment, banking, insurance
• Trap-warning system flags documented jurisdiction traps at lawpack execution time
• Reg D 506(c) handling supported end-to-end with accredited-investor verification

Open questions

• How to extend the lawpack format to cross-border restructurings without losing per-jurisdiction precision
• Where the boundary sits between automated drafting and supervised review
• What the right authorization model is for a lawpack that touches multiple regulators

Ask me about

• How a lawpack actually executes a multi-step jurisdictional operation
• What the partner review surface looks like inside the engine
• How the engine handles cross-jurisdiction conflicts in compliance windows

Stack