legal-context-exports

Published build artifacts from the legal-context pipeline. Consumed at build time by usejunior.com for template detail pages and practice notes.

Contents

template-html/

Pre-rendered HTML for OpenAgreements contract templates. Each file contains the full agreement body (cover terms, numbered clauses, drafting notes) generated by the two-pass Gemini pipeline.

Naming convention: {template-slug}.html

Current templates:

• openagreements-restrictive-covenant-wyoming.html — Employee Restrictive Covenant (Wyoming)

practice-notes/

Practice-note JSON artifacts generated by scripts/md2json.py in the legal-context pipeline. Each file is the website-ready v2 export of one canonical note (with _metadata, questions, references, and inline-citation fields).

Naming convention: {topic-slug}-{state-slug}-{subject-slug}.json

Current notes:

• non-compete-wyoming.json — Non-Compete (Wyoming)
• startup-sale-delaware-stock-vs-asset-purchase.json — Stock vs Asset Purchase (Delaware)

How it's consumed

The website's src/_data/wiki.js fetches these files at build time:

• Locally: reads from ../legal-context/data/ (convenience)
• On Vercel: fetches from https://raw.githubusercontent.com/UseJunior/legal-context-exports/main/template-html/{slug}.html

Updating

After regenerating template HTML in the legal-context pipeline:

cp ../legal-context/data/template-*.html template-html/
git add -A && git commit -m "update template exports" && git push