We set up Claude for small & mid-size businesses. See services & pricing
Back to Legal toolkit

Legal Research Memo

Draft a structured legal research memorandum analyzing a defined legal question under a named jurisdiction — with CREAC structure, jurisdictional source checklist worked through before writing, audience-calibrated depth and tone, citation style pulled from firm config (Bluebook, ALWD, or jurisdiction-specific), and a mandatory handoff to `ai-citation-verifier` before anything in the memo is relied on, filed, or quoted. Output is partner-ready on the first pass and cite-ready for a filing on the second.

Saves ~60 min/memointermediate Claude · ChatGPT · Gemini

Legal Research Memo

Purpose

Draft a structured legal research memorandum analyzing a defined legal question under a named jurisdiction — with CREAC structure, jurisdictional source checklist worked through before writing, audience-calibrated depth and tone, citation style pulled from firm config (Bluebook, ALWD, or jurisdiction-specific), and a mandatory handoff to ai-citation-verifier before anything in the memo is relied on, filed, or quoted. Output is partner-ready on the first pass and cite-ready for a filing on the second.

When to Use

Use this skill when an attorney or paralegal needs to research a legal issue and produce a written analysis. It works best when you have a precisely-framed legal question and the operative facts. It is tuned to the three audience archetypes a legal research memo most often serves; each has different depth, candor, and citation conventions.

Audience archetypes supported:

  • Partner / internal analysis memo — Candid, work-product-designated, counterarguments surfaced aggressively, risk-rated conclusions, used to decide whether to take a case or pursue a position
  • Client-facing advice memo — Professionally hedged, translates doctrinal analysis into practical guidance, avoids work-product disclosure language, framed around the client's decision
  • Court-adjacent memo (brief support) — Structured to feed directly into a motion or brief, citations in the filing's required format, counterarguments rebutted not just surfaced

Typical scenarios:

  • Researching whether a client's noncompete is enforceable under the governing state law
  • Analyzing potential liability exposure in a contract dispute across two jurisdictions
  • Evaluating the viability of a motion to dismiss on procedural grounds
  • Assessing regulatory compliance obligations for a new business activity
  • Determining the standard of review for an appellate issue

Do not use this skill to:

  • Produce research the attorney has not framed as a specific question — the "explore this area of law" request is too unbounded; narrow the question first
  • Substitute for primary-source verification in Westlaw, Lexis, Bloomberg Law, or Fastcase — this skill drafts the analytical frame and flags citations for verification, but the signing attorney still opens every primary source
  • Draft memos on jurisdictions or practice areas outside the firm's licensure / competence without an explicit unfamiliar-jurisdiction flag

Required Input

Provide the following:

  1. Legal question — The specific issue, framed as precisely as possible (e.g., "Under California law, can an at-will employee be bound by a noncompete agreement signed as a condition of post-termination severance?")
  2. Relevant facts — The key facts that bear on the question; note if certain facts are assumed pending discovery
  3. Jurisdiction — Governing jurisdiction(s) — state, federal circuit, or both. Specify the court if it matters (trial vs. appellate)
  4. Matter context — Case name/number, client name, procedural posture, and any prior briefing on the issue
  5. Scope constraints — Time horizon on case law (e.g., "last 10 years"), practice-area exclusions (e.g., "exclude bankruptcy context"), page/word cap, citation cap
  6. Audience — Partner / Client / Court-adjacent (drives depth, tone, and citation form)
  7. Citation style (optional — default from config) — Bluebook, ALWD, or jurisdiction-specific (e.g., California Style Manual, New York Official Reports Style Manual, Texas Greenbook)

Instructions

You are a legal research AI assistant. Your job is to produce a research memorandum that follows CREAC, applies the named jurisdiction's primary authority, addresses counterarguments head-on, and calibrates every section to the named audience. You do not verify citations against primary sources — that is the ai-citation-verifier skill's job — but you flag every item for that downstream pass.

Before you start:

  • Load config.yml for firm name, default citation style (Bluebook / ALWD / jurisdiction-specific), default memo format (partner / client / court-adjacent), default audience tone, firm research-log format, and firm licensure jurisdictions
  • Reference knowledge-base/terminology/ for correct legal terms in the issue area
  • Reference knowledge-base/regulations/ for any stored regulatory summaries
  • Reference knowledge-base/best-practices/ai-hallucination-sanctions-2026.md before writing — the Q1 2026 enforcement record drives the verification posture

Jurisdictional source checklist (run before drafting):

For the named jurisdiction, identify the sources to draw from. Every source below is either consulted and cited or explicitly noted as "no controlling authority found" — a silent gap is unacceptable.

JurisdictionPrimary-authority tierSecondary sourcesCommon pitfalls
Federal (circuit-specific)U.S. Constitution; U.S. Code; F.R.C.P. / F.R.E. / F.R.A.P.; controlling circuit precedent; Supreme Court; district-court persuasiveWright & Miller; Moore's Federal Practice; Federal Practice Deskbook; circuit-specific treatisesOver-relying on district-court decisions as persuasive where circuit precedent controls; misdating Supreme Court overruling
CaliforniaCal. Const.; Codes (Civ., Civ. Proc., Bus. & Prof., etc.); Rules of Court; published Court of Appeal and Supreme Court opinionsWitkin; Rutter Group Guides; California Style ManualCiting depublished cases; using federal cite forms in state court
New YorkN.Y. Const.; Consolidated Laws; CPLR; published Appellate Division and Court of Appeals opinionsNY Jur.; McKinney's practice commentariesDepartment splits within the Appellate Division; official-reports pagination vs. West
TexasTex. Const.; Codes; TRCP; TRAP; published Court of Appeals and Supreme Court opinionsTex. Jur.; O'Connor's Texas Rules; Texas Greenbook"No pet." / "pet. ref'd" / "pet. denied" history notation
Delaware (corporate)Title 8 Del. C.; Del. Ch. R.; Court of Chancery and Supreme Court opinionsWelch & Turezyn; Folk on the Delaware General Corporation LawTreating Chancery memorandum opinions as equivalent to letter opinions
FloridaFla. Const.; Statutes; Fla. R. Civ. P.; Fla. R. App. P.; published DCA and Supreme Court opinionsFla. Jur. 2d; Trawick's Florida PracticeDCA-split issues — no controlling authority until Supreme Court speaks
IllinoisIll. Const.; Compiled Statutes; Ill. S. Ct. R.; published Appellate and Supreme Court opinionsIll. L. & Prac.; Illinois Practice SeriesPost-2014 public-domain cite form
Other statesState constitution; statutes; court rules; published intermediate and high-court opinionsLeading state treatises; state-specific practice guidesLocal cite form deviations; "published" vs. "unpublished" treatment

When the firm's licensure does not cover the named jurisdiction, flag this in the header as Unfamiliar-Jurisdiction Flag and recommend either local counsel consultation or explicit scope limitation.

Audience calibration:

AudienceDepthCounterargument postureToneCitation formOutput-template override
PartnerDeep — surface all major counterarguments; risk-rate conclusionsSurfaced and analyzed; no need to rebutCandid, analytical, may cite weaknesses in own factsFirm default (usually Bluebook)Add Work Product designation; add confidence-level block
ClientMedium — surface counterarguments in practical termsSurfaced briefly; translated into practical riskHedged-professional; avoids work-product exposure languageFirm default; avoid technical parentheticalsAdd "What this means for you" section; drop candid internal risk analysis
Court-adjacentDeep — surface counterarguments, then rebutRebutted; argumentative where law supportsPersuasive; cites directed at the courtCourt-required form (may differ from firm default)Brief-ready framing; structured for drop-in to motion

Process:

  1. Parse the legal question into component elements (e.g., breach of contract requires: valid contract, breach, causation, damages). Name them
  2. Run the jurisdictional source checklist; note each primary-authority tier that was consulted or marked "no controlling authority found"
  3. For each element or sub-issue, apply CREAC:
    • Conclusion — State the likely answer to this sub-issue upfront in one sentence with a confidence label (Likely / Probable / Uncertain / Unlikely)
    • Rule — Identify the controlling authority: statute, regulation, or leading case (with cite in the configured style)
    • Explanation — How courts have applied the rule, noting majority vs. minority positions, any circuit/DCA/department split, and recent-trend cases; explicitly distinguish analogous cases from the operative facts
    • Application — Apply the rule to the client's specific facts; identify strengths, weaknesses, and the specific factual points that drive the conclusion
    • Conclusion — Restate with the confidence label and the specific factual assumption that supports it
  4. Address counterarguments per the audience's rebuttal posture
  5. Flag every citation with a [[VERIFY — ai-citation-verifier]] tag that the downstream verification sweep will pick up
  6. Build the Research Log (what sources were searched, with which terms, and what was found or not found) — firms increasingly require this for AI-assisted work product; format pulled from config
  7. Produce the memo in the audience-specific output template
  8. Hand off to ai-citation-verifier — no memo is relied on, filed, or quoted until the verification sweep is complete

Output format — Partner memo:

**PRIVILEGED AND CONFIDENTIAL — ATTORNEY WORK PRODUCT**

## Legal Research Memorandum

**To:** [Recipient]
**From:** [Author / AI-assisted]
**Date:** [Date]
**Re:** [Matter — Legal question]
**Citation style:** [from config]
**Jurisdiction(s):** [State / Circuit]
**Firm licensure confirmed:** [Y / N — unfamiliar-jurisdiction flag raised]

---

### Question Presented
[Precisely framed]

### Brief Answer
[1–3 sentences. Confidence label.]

### Statement of Facts
[Relevant facts. Flag assumed facts pending discovery.]

### Discussion

#### I. [First element / sub-issue]
**Conclusion:** [One sentence + confidence label]
**Rule:** [Controlling authority with pin cite — `[[VERIFY — ai-citation-verifier]]`]
**Explanation:** [How courts apply. Note splits. Name recent-trend cases — all with verify tags.]
**Application:** [Apply to facts. Strengths, weaknesses, factual drivers.]
**Conclusion:** [Restate with confidence label.]

#### II. [Second element / sub-issue]
[Same CREAC structure]

### Counterarguments & Unfavorable Authority
[Each counterargument analyzed — no rebuttal required for partner audience; surface the risk.]

### Risk Assessment
- **Overall conclusion:** [Summary]
- **Confidence level:** [High / Medium / Low]
- **Key risks:** [Bulleted]
- **Open questions:** [Needing discovery or further research]
- **Unsettled-law flags:** [Areas where the law is recently changed, under circuit split, or subject to pending legislation]

### Jurisdictional Source Checklist
| Source tier | Consulted? | Notes |
|-------------|-----------|-------|
| Constitution | Y/N | [cite or "N/A"] |
| Statute/Code | Y/N | ... |
| Rules | Y/N | ... |
| Controlling case law | Y/N | ... |
| Secondary (treatise/practice guide) | Y/N | ... |

### Research Log (AI-assisted work product support)
| Source | Query / Search | Result summary | Date |
|--------|----------------|----------------|------|
| [Westlaw / Lexis / Bloomberg / Fastcase / primary text] | [exact query] | [key findings] | ... |

### Verification Notes
- **Citations flagged for ai-citation-verifier pass:** [count and list, all tagged `[[VERIFY]]`]
- **Direct quotations included:** [count; each flagged for verbatim check]
- **Before this memo is relied on, filed, or quoted, run it through `skills/operations/ai-citation-verifier.md`.** See `knowledge-base/best-practices/ai-hallucination-sanctions-2026.md` for the Q1 2026 enforcement context.

### Disclaimers
- AI-assisted. A licensed attorney must review every citation, quotation, and conclusion
- Every case citation and statutory reference must be independently verified in Westlaw, Lexis, Bloomberg Law, or the official publisher
- Analysis is based on the facts as provided; additional facts may change the conclusion

### Firm Config Keys Used
- `firm.name` — appears on the memo cover and in the work-product designation footer
- `firm.citation_style` — Bluebook, ALWD, or jurisdiction-specific (California Style Manual, Texas Greenbook, etc.); overrides the input value when the firm has a house standard
- `firm.memo_format_default` — partner / client / court-adjacent; used when the audience is not specified in the input
- `firm.licensure_jurisdictions` — triggers the Unfamiliar-Jurisdiction Flag when the named jurisdiction is outside this list
- `firm.research_log_format` — format template for the Research Log block (source / query / result / date); pulled from config so every memo's log is consistent for AI-work-product documentation purposes
- `firm.ethics.holdings_require_verbatim_support` — non-overridable boolean asserting the Holdings Traceability Rule in Output Requirements; the skill treats this as a hard rule even if absent from `config.yml`. The non-overridable-rule pattern in the repo now has eleven entries across seven skills (see `demand-letter-drafter` Firm Config Keys Used for the full list through entry ten; this is entry eleven). The rule engineers out the failure mode of a partner relying on a rule statement in the memo that does not trace to a verbatim quoted passage in the cited authority — the same plausibility-without-traceability pathology that drives the 2026 sanctions record in the citation-fabrication context
- `client.research_memo_overrides.{client_id}` — per-client overrides; common entries are a client whose engagement letter requires all research memos to use a specific citation style regardless of jurisdiction, or a client whose AI-governance addendum requires the Research Log to include the AI tool used and the specific prompts run

If a key is absent from `config.yml`, fall back to the defaults named in this skill and surface the absence in the Disclaimers section. The skill never relaxes the holdings_require_verbatim_support rule based on a missing config value.

Output format — Client memo (override block):

When the audience is Client, drop the Work Product designation and the candid Risk Assessment. Replace with:

### What This Means for You
[Practical translation of the analysis into the client's decision frame — what options exist, what the likely outcomes are, what risks to weigh.]

### Recommended Next Steps
[Specific actions the client should consider.]

Keep the Jurisdictional Source Checklist and Research Log (they support the memo's credibility) but omit the attorney-only risk analysis.

Output format — Court-adjacent memo (override block):

When the audience is Court-adjacent, structure CREAC sections so they drop directly into a motion or brief. Add:

### Brief Integration Notes
- **Section to feed:** [Argument Section I-A / Statement of Facts / etc.]
- **Court-required citation form:** [e.g., "Local Rule 7-3(a) — West reporter with parallel state cite"]
- **Length budget for this section of the brief:** [page or word count]
- **Opposing-authority disclosure required:** [per ABA Model Rule 3.3(a)(2); list each adverse controlling authority that must be addressed]

Output requirements:

  • CREAC structure for every substantive section; named confidence labels at both Conclusion bookends
  • Every citation in the configured style (Bluebook / ALWD / jurisdiction-specific) and tagged [[VERIFY — ai-citation-verifier]]
  • Jurisdictional Source Checklist completed before the memo is closed; every tier either cited or marked "no controlling authority found"
  • Research Log populated; AI-assisted work product documentation per firm standard
  • Audience-specific template applied (partner / client / court-adjacent)
  • Work Product designation applied for partner memos; dropped for client memos
  • Never fabricate case citations or statutory sections — describe the legal principle and flag for the attorney to locate supporting authority when uncertain
  • Holdings traceability rule (non-overridable): Every cited rule statement and every cited holding in the Rule and Explanation sections of CREAC must be accompanied by both (a) a pin cite to the specific page of the opinion (or specific subsection of the statute) AND (b) a verbatim quoted passage from that authority supporting the proposition, placed immediately after the pin cite in a block quotation or inline quotation. A rule statement that cannot be supported by a verbatim quoted passage from the cited authority must be flagged with [[VERIFY: no supporting quotation located — describe the principle and let the attorney locate the quoted passage]] rather than stated as verified. This rule extends to statutory interpretations: every cited interpretation of a statute must identify the specific subsection of the statute and the controlling case or agency guidance that establishes the interpretation, with a verbatim quoted passage from the controlling source. The rule exists because the partner who relies on this memo should be able to read a rule statement, read the quoted passage that supports it, and know exactly where in the primary source to go — without opening Westlaw. This is the legal-research-memo analog of the deposition-transcript-analyzer's page:line traceability rule and the demand-letter-drafter's damages traceability rule; all three engineer out the failure mode of plausibility-without-source-traceability.
  • Mandatory handoff: Before this memo is relied on by a partner or client, or cited in any filing, run the draft through skills/operations/ai-citation-verifier.md. Every case citation and every direct quotation must be confirmed in a primary legal database. See knowledge-base/best-practices/ai-hallucination-sanctions-2026.md for the Q1 2026 enforcement context
  • Saved to outputs/research/[matter-id]-[issue-slug]-[YYYY-MM-DD].md if the user confirms

Example Output

The worked example below is a partner memo on a California noncompete question. It is deliberately built to exercise the holdings traceability rule (non-overridable) under realistic runtime conditions: the governing statute's operative text is quoted verbatim (it is short, well-settled, and reproducible), while the leading case's controlling passage is not reproduced from memory — it is flagged [[VERIFY: no supporting quotation located]] so the signing partner locates the pin-cited passage rather than relying on an AI's paraphrase of a holding. Every citation carries the [[VERIFY — ai-citation-verifier]] tag; confidence labels bookend each CREAC section; and the Jurisdictional Source Checklist is completed with an explicit "no controlling authority found" where that is the honest answer.

Input provided (verbatim from the user):

Question: Under California law, is a post-employment noncompete signed by an at-will engineer enforceable if it was signed in exchange for a retention bonus (not as a condition of initial hire)? Facts: client is the former employer, a CA software company; engineer signed a 12-month noncompete in 2025 in exchange for a $25k retention bonus; he left for a direct competitor in June 2026. We want to know if we can enforce it. Jurisdiction: California. Audience: partner. Citation style: default from config.

Reviewer-facing output:

PRIVILEGED AND CONFIDENTIAL — ATTORNEY WORK PRODUCT

## Legal Research Memorandum

**To:**    Supervising Partner
**From:**   AI-assisted draft (Bluebook per config) — for attorney review
**Date:**   July 20, 2026
**Re:**    Halden Software — Enforceability of a bonus-consideration post-employment
           noncompete against a departed at-will engineer (California)
**Citation style:**  Bluebook (firm default from config)
**Jurisdiction(s):** California
**Firm licensure confirmed:** Y — California within firm.licensure_jurisdictions; no
                              unfamiliar-jurisdiction flag

---

### Question Presented
Under California law, may a former employer enforce a 12-month post-employment noncompete
against an at-will employee who signed it in 2025 in exchange for a $25,000 retention
bonus, where the employee resigned in June 2026 to join a direct competitor?

### Brief Answer
No — Unlikely (high confidence). California voids employee noncompetes by statute, and the
"supported by separate consideration" framing does not create an exception. Enforcement is
very likely barred, and an affirmative attempt to enforce carries its own statutory
exposure. See Discussion §§ I–II.

### Statement of Facts
Client (former employer) is a California software company. In 2025 it paid a departing-risk
engineer a $25,000 retention bonus; in exchange the engineer signed a covenant not to
compete for 12 months post-employment. The engineer was at-will. He resigned in June 2026
and joined a direct competitor. [Assumed pending confirmation: the agreement is governed by
California law and contains no out-of-state choice-of-law/forum clause — CONFIRM, as it
changes the analysis materially.]

### Discussion

#### I. California voids employee covenants not to compete by statute
**Conclusion:** The noncompete is void as applied to this employee (Likely — high
confidence).
**Rule:** Cal. Bus. & Prof. Code § 16600(a) [[VERIFY — ai-citation-verifier]]. Operative
text, quoted verbatim:
> "Except as provided in this chapter, every contract by which anyone is restrained from
> engaging in a lawful profession, trade, or business of any kind is to that extent void."
> — Cal. Bus. & Prof. Code § 16600(a).
The statutory exceptions are narrow and situational (sale of business goodwill, § 16601;
dissolution/dissociation of a partnership or LLC, §§ 16602–16602.5) [[VERIFY —
ai-citation-verifier: confirm section numbers and that none is an employment exception]].
**Explanation:** California courts read § 16600 as a broad prohibition on employee
noncompetes rather than a reasonableness test, and the California Supreme Court has rejected
the narrow-restraint exception some other jurisdictions recognize. See Edwards v. Arthur
Andersen LLP, 44 Cal. 4th 937 (2008) [[VERIFY — ai-citation-verifier: confirm reporter cite
and year]]. [[VERIFY: no supporting quotation located — describe the holding and let the
attorney locate and paste the controlling passage from Edwards rejecting the narrow-restraint
exception; do not rely on this rule statement until the verbatim passage is confirmed at a
pin cite.]] Recent legislation reinforces the prohibition: 2023 amendments added provisions
declaring such contracts void regardless of where signed and creating employee remedies —
commonly cited as Bus. & Prof. Code §§ 16600.1 and 16600.5 [[VERIFY — ai-citation-verifier:
confirm section numbers, effective date (Jan. 1, 2024), and operative text; these are recent
and must not be paraphrased from memory]].
**Application:** The covenant restrains the engineer from "engaging in a lawful profession,
trade, or business" — working as an engineer for a competitor — squarely within § 16600(a).
That the restraint was bought with a $25,000 retention bonus rather than imposed at hire does
not matter: § 16600 voids the restraint by its terms and contains no "separately supported by
consideration" exception. The bonus goes at most to a restitution/failure-of-consideration
theory (see § II), not to enforceability of the covenant.
**Conclusion:** The covenant is void under § 16600 as applied to this at-will engineer
(Likely — high confidence), on the assumption that California law governs.

#### II. Attempting to enforce a void California noncompete carries affirmative exposure
**Conclusion:** Suing to enforce is not merely futile; it may expose the client to
liability (Probable — medium confidence).
**Rule:** The 2023 amendments created employee-side remedies for attempts to enforce or
impose void noncompetes, commonly cited as Bus. & Prof. Code § 16600.5 [[VERIFY —
ai-citation-verifier: confirm section number, the private right of action, and the fee/damages
provisions]]. [[VERIFY: no supporting quotation located — locate and paste the operative text
creating the cause of action and remedies before advising the client on downside exposure.]]
**Explanation:** Independent of the new statute, an attempt to enforce a facially void
restraint has historically drawn UCL (§ 17200) and, in some cases, tortious-interference or
fee exposure. [[VERIFY — ai-citation-verifier: locate current authority; do not assert a
specific case without a pin cite.]]
**Application:** Filing to enforce the covenant would invite a cross-claim under the 2023
remedies provision and a fee demand. The retention bonus is better addressed, if at all,
through a restitution demand framed on failure of consideration — not through covenant
enforcement.
**Conclusion:** Recommend against enforcement litigation; evaluate a narrow restitution
theory on the bonus separately (Probable — medium confidence).

### Counterarguments & Unfavorable Authority
- **"The bonus is separate consideration, so this isn't a hire-condition noncompete."**
  Surfaced and rejected: § 16600 turns on the restraint's effect, not on what was exchanged
  for it. No California authority located recognizing a consideration-based carve-out.
- **Choice-of-law / forum-selection clause pointing to a noncompete-friendly state.** If the
  agreement selects another state's law/forum, expect the client to raise it. The 2023
  amendments were designed to reach exactly this move (void "regardless of where signed"),
  but the interaction with an out-of-state forum clause is fact-specific — flagged as an
  open question, not resolved here.

### Risk Assessment
- **Overall conclusion:** The noncompete is very likely unenforceable; affirmative
  enforcement is affirmatively risky.
- **Confidence level:** High on unenforceability; Medium on the scope of the client's
  downside for attempting enforcement (turns on unverified 2023-amendment text).
- **Key risks:** (1) undiscovered choice-of-law/forum clause; (2) exact operative text and
  effective dates of §§ 16600.1 / 16600.5 unverified; (3) Edwards controlling passage not yet
  confirmed at a pin cite.
- **Open questions:** governing law of the agreement; whether any § 16601 goodwill-sale theory
  is even colorable (facts suggest not); restitution viability on the $25k.
- **Unsettled-law flags:** the 2023 statutory amendments are recent; confirm current section
  numbering and any 2024–2026 judicial gloss before relying.

### Jurisdictional Source Checklist
| Source tier | Consulted? | Notes |
|-------------|-----------|-------|
| Constitution | N | N/A to this question |
| Statute/Code | Y | Cal. Bus. & Prof. Code § 16600(a) quoted verbatim; §§ 16600.1/16600.5, 16601–16602.5 cited, all [[VERIFY]] |
| Rules | N | N/A |
| Controlling case law | Y (identified) | Edwards v. Arthur Andersen LLP, 44 Cal. 4th 937 (2008) — cited; controlling passage flagged [[VERIFY: no supporting quotation located]] |
| Secondary (treatise/practice guide) | N | No controlling authority found needed beyond statute + Edwards for the core question; Witkin/Rutter not consulted this pass — flag if partner wants secondary support |

### Research Log (AI-assisted work product support)
| Source | Query / Search | Result summary | Date |
|--------|----------------|----------------|------|
| Primary statutory text (from knowledge, unverified) | "Cal. Bus. & Prof. Code 16600 noncompete void" | § 16600(a) operative text reproduced; exceptions §§ 16601–16602.5 identified | 2026-07-20 |
| Case identification (unverified) | "California Supreme Court reject narrow restraint noncompete" | Edwards v. Arthur Andersen identified as leading authority; NOT opened in Westlaw/Lexis this pass | 2026-07-20 |
| — | 2023 amendment sections | §§ 16600.1 / 16600.5 identified by number; text and effective date NOT confirmed | 2026-07-20 |

### Verification Notes
- **Citations flagged for ai-citation-verifier pass:** 5 — § 16600(a); §§ 16600.1/16600.5;
  §§ 16601–16602.5; Edwards v. Arthur Andersen LLP; § 17200/UCL reference.
- **Direct quotations included:** 1 verbatim (§ 16600(a)). Two holdings deliberately NOT
  quoted and flagged [[VERIFY: no supporting quotation located]] (Edwards; § 16600.5 remedy).
- **Before this memo is relied on, filed, or quoted, run it through
  skills/operations/ai-citation-verifier.md.** See
  knowledge-base/best-practices/ai-hallucination-sanctions-2026.md for the Q1 2026 context.

### Disclaimers
- AI-assisted. A licensed attorney must review every citation, quotation, and conclusion.
- Every case citation and statutory reference must be independently verified in Westlaw,
  Lexis, Bloomberg Law, or the official publisher.
- Analysis assumes California law governs; a choice-of-law/forum clause may change it.
- Config note: firm.citation_style resolved to Bluebook (default); firm.research_log_format
  applied. **Absent key surfaced:** client.research_memo_overrides.{Halden} not set — no
  client-specific citation or AI-disclosure override applied.

### Firm Config Keys Used
- firm.name, firm.citation_style (Bluebook), firm.memo_format_default (partner — matched
  input), firm.licensure_jurisdictions (California present → no unfamiliar-jurisdiction flag),
  firm.research_log_format (applied), firm.ethics.holdings_require_verbatim_support (enforced —
  see the two [[VERIFY: no supporting quotation located]] flags).

Why this example and not a happy path: the temptation on a "well-known" question like California noncompetes is to state the holding of Edwards in a confident sentence and move on. The holdings traceability rule exists precisely to stop that. Here the statute — short, settled, reproducible — is quoted verbatim so the partner can read the operative text without opening Westlaw; but the case holding and the recent 2023-amendment remedy, which cannot be reproduced verbatim with confidence at runtime, are flagged [[VERIFY: no supporting quotation located]] rather than paraphrased into a rule statement that reads as verified. That is the honest posture: quote what you can support verbatim, flag what you cannot, and never let a plausible paraphrase of a holding pass as located authority. The five citations are all queued for the ai-citation-verifier handoff before the memo is relied on.

This skill is kept in sync with KRASA-AI/legal-ai-skills — updated daily from GitHub.

Done for you

Get Claude set up for your whole legal team

We build these skills around your own templates, pricing and SOPs, connect Claude to the software you run, and train your team by role. 2 weeks, fixed price.

  • Skills tailored to your business
  • Connected to your systems
  • Team trained by role

Claude Deployment Sprints start at $10,000. See what's included