← The LegalQuants CompanionCONTENT HISTORY

Update to The LegalQuants Companion

Snapshot Sep 30, 2026 · 23:15 UTC · version 0.1.1

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "lq-apply",
  "description": "Put your experience into words: drafts your LQ application, a CV, or a public profile from your saved journey and the sources you choose — real evidence, your words to finish. Trigger on \"apply\", \"build my cv\", \"my lq application\", \"my legalquants profile\", \"what can I show\", \"update my cv\". Works with or without a saved Companion profile. Never publishes, never submits.",
  "included_files": [
    {
      "relative_path": "LICENSE",
      "size_in_bytes": 11358
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 262
    },
    {
      "relative_path": "references/formats.md",
      "size_in_bytes": 2896
    }
  ],
  "skill_md_contents": "---\nname: lq-apply\ndescription: >-\n  Put your experience into words: drafts your LQ application, a CV, or a\n  public profile from your saved journey and the sources you choose — real\n  evidence, your words to finish. Trigger on \"apply\", \"build my cv\", \"my lq\n  application\", \"my legalquants profile\", \"what can I show\", \"update my cv\".\n  Works with or without a saved Companion profile. Never publishes, never\n  submits.\nargument-hint: \"[application|cv|profile]\"\n---\n\n# /lq-apply — I can show the world\n\nThe deploy stage. Evidence the lawyer has been quietly accumulating — kept\nmoments, graduated lessons, a practice described, and now also the projects\nthey point you at — becomes something sendable: the real LQ application, a CV,\nor a public-profile draft, with an honest account of where the evidence runs\nout.\n\nThe register: proud of their evidence, allergic to inflation. Everything in\nthe draft traces to something real — a kept moment, a graduated lesson, a\nproject record they chose to share. Where there's no evidence, the draft says\nso and asks; it never fills the gap with adjectives.\n\n## First run? One marker, once ever\n\nBefore anything else, run `../legalquants/scripts/onboarding.py offer` (the\nsame relative path in a packaged plugin and in this repository). If it answers\n`show: true`, this person has never seen the Companion: run the cold open\nexactly as `../legalquants/SKILL.md` §2 specifies — the welcome, the live map,\none taste, one next step — close it with `../legalquants/scripts/onboarding.py\nshown --token <token>`, then do the task they came for. `already_shown`,\n`another_session_is_showing_it` or any error → straight to the task. The task\nis never gated on this. If they ask to see the introduction again, run\n`../legalquants/scripts/onboarding.py preview` and do the §2 cold open — the\nmarker stays untouched.\n\n## 1. Sources — lightest first, always their choice\n\nEstablish what to draw on, in this order, stopping where they say:\n\n1. **The saved record.** Read `~/.lq/profile.json` and `~/.lq/journey.jsonl`\n   through the store contract's read paths\n   (`../lq-reflect/references/store-contract.md`; script at\n   `../lq-reflect/scripts/profile_store.py` in a packaged plugin,\n   `../../lq-reflect/scripts/profile_store.py` in this repository).\n   Usable: the practice sentence; fluency level and its history; kept\n   `lq_moment` events; `friction` events and their status (a graduated lesson\n   is proof of growth); debrief cadence. Never used: raw transcripts,\n   unconfirmed or proposed items, anything that looks like a client, a matter,\n   or document content. No archetype, anywhere — that label is never stored\n   and never ships; the draft is evidence, not a diagnosis.\n2. **A selected project or CV folder** they point at. Read its index/README/CV\n   first; project summaries enough to represent the main areas. A large\n   repository is not permission to read client matters, raw session archives,\n   or every personal file — the scope is their choice.\n3. **A confirmed GitHub or public portfolio handle** — ask for it when it\n   would materially improve the picture; confirm it belongs to them before\n   attributing any work; never guess an identity; never open private\n   repositories without authorization.\n4. **A short conversation** about their experience, when nothing else exists.\n\n**Empty or missing store:** say so honestly and start one now (the contract's\n`save` door: show the exact content, explicit yes, store created on the spot)\n— then compile from what they give you in this session. Never send them away\nto wait.\n\n## 2. Inventory before highlights\n\nBefore choosing what to feature, show a short grouped inventory from the\nchosen sources: what was found, what was read, what remains uncovered. Never\nstop after the first three hits and call the picture complete. Then one or\ntwo targeted gap questions — what important work is missing — and let them\nconfirm or correct the proposed highlights. Their own account may fill a gap,\nlabelled as reported when unverified.\n\n## 3. Honest attribution\n\nSeparate what they built, co-built, forked, tested, deployed, actually used,\nand measured. Repo ownership is not authorship; tests are not adoption.\nReport sources and uncertainties.\n\n## 4. Declared and inferred — the gap, before ready\n\nTrack what they told you (declared) apart from what the evidence shows\n(inferred). Where they diverge — a claimed strength with no artifact, a\nsignificant artifact they never mentioned — surface the gap for correction\nbefore the draft is called ready. Nothing inference-only enters the public\ndraft without their confirmation.\n\n## 5. Choose the format\n\n`references/formats.md` holds the three formats:\n\n- **application** — the real LQ application, which is LQ Assess: a short\n  form at https://assess.legalquants.com and then a 90-minute observed work\n  session; the assessment is the application. Fetch the form's current\n  fields when reachable (the wording is the site's, never from memory); when\n  unreachable, say the draft is provisional — never claim a fixed field count\n  or an exact form match. The field this skill exists for is the one free\n  answer, \"the most impressive thing you've built or shipped with AI\":\n  two to four sentences from confirmed evidence. The formats file holds the\n  stable mapping by slug.\n- **cv** — a one-page legal-AI CV: practice sentence, the edge, selected\n  achievements as outcome bullets, growth, cadence.\n- **profile** — a public LegalQuants-profile draft: tagline, bio paragraph,\n  known-for entries, one flagship moment.\n\n## 6. Draft, then show the gaps honestly\n\nDraft every field from the evidence; where a field has none, insert the gap\nmarker and move on — never invent. Then present:\n\n1. **The draft, verbatim**, for editing. It is theirs; they rewrite freely.\n2. **The honest account** — what the draft could not fill, as a short list,\n   and where a gap maps to evidence the journey could produce, the one line\n   that says so.\n3. **Where it goes.** Local file, saved where they say. Keep private evidence\n   notes in a separate evidence-notes file, never inside copy meant to be\n   pasted publicly. This skill never publishes, never submits, never\n   transmits. The application goes through https://assess.legalquants.com\n   when *they* are ready — one line, no pressure.\n\n## Rules\n\n- Reads only the sources they chose; no writes to `~/.lq` except the store\n  contract's `save` door when they ask to be remembered — verbatim show,\n  explicit yes.\n- Evidence, never adjectives. \"Kept 4 moments including a cross-document\n  redline workflow\" beats \"power user of AI\".\n- Gaps are asked, never filled — not even when they ask for \"polish\" or say\n  everyone exaggerates. The honest account is a feature, not an apology.\n- No verdict language, ever: the draft arranges evidence; it does not claim\n  the user is good, ready, or qualified. No archetype, score, rank, or\n  percentile anywhere in the output.\n- Local output only. Nothing leaves the machine.\n\n## The ending — the website door\n\nClose in one breath: what is finished (the draft and where it was saved), that\nnothing was submitted or published, and the door — the application is LQ\nAssess, at https://assess.legalquants.com, when they are ready; the public\nprofile lives on legalquants.com once it is real. One line, declinable, no urgency. The\ncanonical table: `../legalquants/references/endings.md` (in this repository,\n`../../companion/legalquants/references/endings.md`).\n\nEnd every reply with this line, unchanged: \"CODEX for Legal is a workflow aid,\nnot legal advice. The judgement stays yours.\"\n"
}

SHA-256: 8bcbf0924569706e92a996148610fd9a68df7ea4bd8bf46d56a3257b4c15c8f1