QENEX Law — Unpark Checklist#

One page to resume with zero re-discovery. Work top-to-bottom; nothing here starts until the prerequisite is met.

⛔ Prerequisite (the single blocker)#

Grant the connector Forgejo write access — Option A (scoped tool + qenex-law-bot token, scopes write:repository [+ write:organization for org repos]), per docs/forgejo-write-access-enablement.md. Cloud/scheduled sessions run as mcp_user and cannot write to Forgejo until this is done. Everything below depends on it.

1. Create the repo & push#

• [ ] Create qenex-admin/qenex-law in Forgejo.
• [ ] Push this repo (has full history):

```bash tar xzf qenex-law.tar.gz && cd qenex-law git branch -M main git remote add origin https://git.qenex.ai/qenex-admin/qenex-law.git git push -u origin main ```

• [ ] Confirm the corpus-gate CI (.forgejo/workflows/validate.yml) runs green.

2. Tag the first free (P1) sources#

• [ ] Fill/verify the seeded green sources: legislation.gov.uk (Companies Act 2006), HMRC VCM (SEIS/EIS).
• [ ] Read BVCA terms of use → keep bvca-model-early-stage-docs amber with conditions, or promote to green if terms permit corpus/AI use.
• [ ] Confirm the National Archives computational/AI re-use licence before ingesting any case law (amber).
• [ ] python3 tools/validate_corpus.py stays green after each add.

3. Wire the regulation monitor (single source of truth stays current)#

• [ ] Scheduled task implementing UPDATING.md: detect change → open PR (update source.yaml + ipfs_cid + anchor_id + CHANGELOG) → impact-flag citing clauses needs-review → human review/merge → re-anchor.
• [ ] Reuse: scheduled-task pattern + qenex_websearch_* + dual-rail audit anchoring.

4. Wire provenance on ingest#

• [ ] On each ingest: pin raw doc to IPFS (ipfs_cid), anchor the version (anchor_id), write metadata to Supabase (tmsvyuxaiozmcxdaaqeu).

5. Close the linked SEIS/EIS longstop loop#

• [ ] When HMRC/SeedLegals confirm the compliant window, update clause asa-longstop-conversion and the live term sheet / Form ASA (currently 18 months — likely non-compliant).

Open decisions to make when unparking#

• e-sign: build vs. reuse the Docusign connector.
• first template set order (term sheet → NDA → employment → board resolutions).
• clause-library vs. raw-corpus repo boundary (current tree keeps both here; split later if it grows).

Delivered artifacts (all already in hand)#

• qenex-law.tar.gz — repo v0.1.1 (tree, licence schema, validator + CI, seeded P1 sources, first clause).
• docs/design-spec-v0.1.md · docs/knowledge-base-plan-v0.1.md · _meta/licence-tagging-schema.md · docs/forgejo-write-access-enablement.md.
• Full trail in user memory: /areas/qenex-legal-automation.md.

Guardrails to keep (don't drift)#

• Licence gate: default red when unsure; CI blocks red/untagged/amber-without-conditions.
• Internal-first: public only after unfinished work clears and UPL/professional-liability groundwork is done.
• Focus: this sits behind Lab (sole strategic focus) — don't let it pull attention until Lab allows.