Eight Roles, One Architecture: The Associate, the Partner, and In-House Counsel
Part 2 of the series, post two of three sub-pieces. The May 7 to May 13 legal AI architecture walked through three working roles where the supervisory chain runs through more than one person.
Part 2 of a three-part series. Part 1 walked the components. Part 2 walks the roles. Part 3 will walk the practice areas. Part 2 publishes in three sub-pieces. This is the second. The first covered the solo or small-firm lawyer and the paralegal. The third covers litigation support specialists, government attorneys, and public-interest or legal aid lawyers.
Corrections. Spot a factual error, misquote, mischaracterization, broken link, or anything else that needs correcting? Please email allsourcelegalai@substack.com. If a material issue is confirmed, the publication will aim to append a dated correction or clarification promptly, ordinarily within 72 hours where practicable.
The first sub-piece of Part 2 covered the two roles in which the productivity tier lands first and integration-layer access is uneven, emerging, or absent: the solo or small-firm lawyer and the paralegal.
This sub-piece covers three roles where the picture inverts. Integration-layer access is often standard. The work surface is taken for granted. And the supervisory chain spans more than one person, which means the exposure no longer sits on a single desk.
A quick refresher on the vocabulary that travels across every role section. The stack is three layers. Work surface refers to Microsoft 365 with Claude in Word, Excel, PowerPoint, and Outlook. Workflow layer means Anthropic’s twelve practice-area legal plugins and twenty-plus connectors. Integration layer means CoCounsel Legal, grounded in Westlaw or Lexis+, with Protégé connected to Lexis. Adjacent systems sit at the edges: document management, eDiscovery, and contract management platforms that come from outside the May 7 to May 13 announcements but are increasingly wired into the stack through standardized connections. Integration-layer access means whether the role has CoCounsel Legal or Lexis+ with Protégé in the working environment. Grounded retrieval means the technical mechanism by which a connected AI system searches a known database before generating output. MCP, the Model Context Protocol, is a standardized, open protocol that allows AI systems to connect to external systems without custom integrations. Product-status descriptions in this piece reflect the cited public record as of the publication date; vendor deployments, beta status, and integration scope can change quickly.
Three lessons from the prior articles travel through every role section. The architecture is still stabilizing in public. Announcement language often exceeds the scope of deployment. Operational adoption is outpacing the verification discipline. The reported phantom-quotations filing in a federal layoffs case, drafted partly through Claude Console, is the working example of that third lesson reaching a court filing.
At the three roles in this sub-piece, those lessons stop being individual concerns and become institutional ones. The associate produces work that another person signs. The partner signs work other people produced. The in-house counsel sets the rules governing how the entire workforce uses the stack. The verification chain now has links.
The architecture is the same. The exposure moves.
The role profiles that follow are analytical composites built from the architecture documented in Part 1 and the deployment patterns described in the public record. They are illustrative, not survey findings, and not claims about every firm, department, or rollout.
Role 3: The litigation associate at a midsize-to-large firm
On a Wednesday at the firm, the second-year associate has a research memo due to the partner by the end of the day and a section of a summary-judgment brief due tomorrow. At a midsize-to-large firm, all three layers of the stack are often available to the associate, though what is actually provisioned varies by practice group, license tier, and the firm’s rollout progress. In a fully provisioned setup, the work surface is open in Word and Outlook. The workflow layer is deployed: the firm has rolled out the litigation plugin, which runs beneath the drafting environment. The integration layer is connected: CoCounsel Legal with Westlaw Deep Research, or Lexis+ with Protégé on the Lexis side, is one pane away, with the specific capability depending on which product the firm has configured. The adjacent systems are wired in: iManage holds every prior memo, brief, and template the firm has produced on this kind of matter.
This is the role the architecture was built for. In firms that have deployed these tools, the associate has the full stack and the institutional support to run it. The associate also has the least control over how the output is used, because the associate is often not the one who signs the filing.
The role
The litigation associate researches, drafts, and revises. Memos, brief sections, deposition outlines, discovery responses, chronologies, and fact summaries. The associate is the person who reads the cases, builds the argument, and produces the first complete version of the document that the partner will review, revise, and sign.
The associate is measured on output and billable hours, which puts the associate in the role under the most direct pressure to adopt tools that produce output faster. A partner who tells associates to be careful with AI is also a partner who expects the memo by the end of the day. The associate lives inside that tension every working week.
The associate is often not the signing attorney on the filing. The partner usually is. But the associate produces the draft that the partner relies on, which means the quality of the associate’s verification determines what the partner is signing, whether the partner knows it or not.
Work surface
Same Microsoft 365 environment as the rest of the firm, fully provisioned rather than the low-admin setup at the solo desk. Claude in Word for drafting memos and brief sections. Claude in Excel for damages models, deposition designations, and document review tracking. Claude in Outlook for the constant internal coordination an associate runs with partners, paralegals, co-counsel, and the client’s in-house team.
What this looks like on a working day. The partner asks for a memo on whether a particular affirmative defense survives a recent appellate decision. The associate opens Word with Claude, frames the question, and gets a first structural pass in minutes rather than the half day a cold start used to take. The associate then does the actual legal work: reading the appellate decision in full, checking whether Claude’s framing of the holding matches the court’s language, tracing every citation Claude proposed back to the reporter.
The speed gain is real and front-loaded. The first draft arrives faster. The verification work that follows is the same work it always has been, and in this role, it is the work that separates a usable memo from a liability.
Workflow layer
This is the role where the workflow layer is most likely to be fully deployed and actively used. The firm has configured the litigation plugin, managed the identity and tenant administration the plugin assumes, and set the policy oversight the solo desk could not. The associate runs inside that configured environment.
The associate can also read the claude-for-legal repository directly, the same public configuration the solo lawyer can read, and the same configuration that changed inside the launch window when the May 12 commit titled “Remove Lexis references at partner request” modified the visible stack. For the associate, the lesson is operational. The plugin the firm deployed encodes a particular sequence of steps and a particular set of connector assumptions. When the firm updates the plugin, the sequence can change. The associate who understands what the plugin is actually doing underneath the drafting environment is better positioned than the associate who treats it as a black box.
The workflow layer now also includes the named agents Anthropic has published in the repository: job-style tools such as a Brief Section Drafter, a Chronology Builder, a Deposition Prep agent, and a Privilege Log Reviewer, each runnable with a single command. These map directly onto associate tasks. The associate who knows which agents exist for litigation work has a more complete picture of what the firm’s deployment can actually do.
Integration layer
This is where the associate’s experience diverges most sharply from the solo lawyer’s. At a midsize-to-large firm, integration-layer access is often standard. The associate runs CoCounsel Legal with Westlaw Deep Research or Lexis+ with Protégé as part of the normal research workflow, with the firm covering the subscription costs that the solo desk could not absorb.
Grounded retrieval changes the failure mode but does not remove it. When the associate runs a research question through CoCounsel Legal, the system searches Westlaw before generating the draft, which lowers the chance that a fabricated citation reaches the draft. It does not lower it to zero. The associate still has to read the cases the system returns, confirm that they say what the system says they say, and confirm that they are still good law. The grounded tier is faster and more reliable than ungrounded drafting. It is not a substitute for reading the cases.
The grounded tier is faster and more reliable than ungrounded drafting. It is not a substitute for reading the cases.
The operational-scope lesson from Part 1 applies directly to this role. The CoCounsel Legal capability exposed through Claude is Westlaw Deep Research, specifically, a research workflow that runs a search against Westlaw and returns a report, exposed through a limited set of tool calls, not the full CoCounsel Legal platform. The associate who needs drafting support, file summarization, or other CoCounsel Legal capabilities is directed back to the native CoCounsel environment. The associate should know which capabilities are actually available in which environment before building a workflow based on an assumption about what the integration does.
What this role should know
The associate’s verification work is the foundation on which the partner’s signature rests. Every citation in an associate-produced draft has to be read against the actual reporter before the draft goes to the partner. Every quotation has to be checked against the source. Every proposition of law has to be traced to a case that actually states it. The partner will review the draft, but the partner is reviewing it on the assumption that the associate already did that work. When that assumption is wrong, the chain breaks at a point the partner cannot see.
AI hallucination in court filings is a documented and growing concern, tracked in more than 1,000 cases across public databases such as Damien Charlotin’s AI Hallucination Cases Database. The database covers more than lawyer sanctions; it includes pro se litigants and a range of outcomes. Many of the lawyer-involved cases follow a consistent pattern. The work was produced with AI assistance, the citations were not independently verified, and the filing reached the court with fabricated or misattributed authority. The associate is frequently the person who produced the underlying draft. Making AI use visible to the supervising partner is one of the most protective practices available in this role, because it tells the partner’s verification step where to focus.
The associate has professional exposure that the supervisory structure does not provide. The duties of competence, candor, and verification under the rules of professional conduct attach to the associate as a lawyer, not only to the partner who signs. A partner’s instruction to produce work fast does not eliminate the associate’s own obligation to check it. The associate who files AI-assisted work without checking the authority, or who passes unchecked work up the chain, knowing the partner may not catch it, is acting against duties the associate holds independently.
The next twelve months
More firms are moving from pilot deployments to full litigation-plugin rollouts. More associate workflows are built on the named agents in the repository. More firm-level policy on how associates flag AI use when work moves up to the signing attorney. More pressure on the billable-hour model as the work surface compresses the time a first draft takes, and more attention to what that compression does to associate training and development. The verification work does not compress. It is the part of the job the architecture does not do.
Role 4: The litigation partner at a midsize-to-large firm
On a Thursday, the partner has four matters moving at once and a brief to sign by close of business. The partner did not draft the brief. An associate did so, with AI assistance, within the firm’s deployed stack. A paralegal assembled the exhibits and flagged which sections came from Claude and which citations came from CoCounsel Legal. The brief is on the partner’s screen now, and the partner’s signature is what turns it from a draft into a filing.
The partner sees the least of the stack day-to-day and carries the most exposure to it. The partner may not open Claude in Word at all. The partner reviews the output that other people produced inside the architecture, and the partner signs.
The role
The litigation partner supervises, signs, and carries the relationship with the client and the court. The partner sets strategy, reviews the work associates and paralegals produce, makes the judgment calls, and puts a signature on the documents that go to the court. The partner is often the lead signing attorney. The partner is the person the court can hold responsible when a filing contains fabricated authority.
The partner’s exposure is structural, and it runs in two directions. Under the federal rules, the signature on a filing certifies that the partner has conducted a reasonable inquiry and that the claims and contentions are warranted, not that the partner personally guarantees every assertion in the abstract. Under the rules of professional conduct, the partner carries supervisory responsibility for the lawyers and nonlawyers the partner directs. The partner is signing for the associate’s research, the paralegal’s assembly, and the partner’s own judgment, all at once.
Work surface
The partner’s use of the work surface is often lighter and more selective than the associate’s. Claude in Outlook to triage a heavy inbox and draft responses to opposing counsel and clients. Claude in Word to revise rather than to draft from scratch, tightening an associate’s section or reworking an argument. Claude in PowerPoint for client presentations and pitch materials. The partner is more likely to use the work surface as a revision and communication tool than as a primary drafting environment.
What this looks like on a working day. The associate’s brief lands in the partner’s inbox at two in the afternoon. The partner reads it. The argument is sound. The structure is right. The citations look correct. Here is the decision the architecture has made sharper: the partner can sign on the strength of the read, or the partner can verify the citations independently before signing. The work surface did not create that decision, but the speed of AI-assisted drafting has increased the volume of work flowing up to the partner’s signature, which makes the decision recur more often and under more time pressure.
Workflow layer
The partner is often less likely than the associate to interact directly with the workflow layer and is among the most affected by its configuration. The partner generally does not run the litigation plugin. The associate does. But the partner is the person who should understand, at a policy level, what the firm’s deployed plugins do, what the named agents are configured to produce, and where the verification gaps are. A partner who signs work produced through a workflow the partner does not understand is signing on trust alone.
The architecture-stabilizing lesson presents itself to the partner as a governance question. The May 12 Lexis removal commit showed that the stack's visible configuration can change within a launch window. For the partner, the implication is that the firm’s AI deployment is not a fixed thing the partner can understand once and then ignore. It is a moving system, and the partner’s supervisory obligation attaches to whatever it is currently doing.
Integration layer
The partner relies on integration-layer access without necessarily operating it. When the associate runs CoCounsel Legal with Westlaw Deep Research and weaves the grounded citations into the brief, the partner inherits the benefit and the residual risk. Grounded retrieval reduces the rate at which fabricated citations reach the draft. It does not eliminate the partner’s obligation to verify before signing. A grounded citation is more likely to be real than an ungrounded one, but “more likely to be real” is not the standard the partner certifies to when the partner signs.
The signing decision is where every layer of the stack converges. The work surface produced the draft faster. The workflow layer structured it. The integration layer grounded the research. The adjacent systems supplied the firm precedent. All of that lands on the partner’s signature, and none of it discharges the partner’s certification obligation.
Every layer of the stack lands on the partner’s signature, and none of it discharges the partner’s certification obligation.
What this role should know
The partner’s signature is the certification the entire chain rests on, and AI assistance does not displace the lawyer’s duty of reasonable inquiry and supervision. A lawyer who signs a filing certifies that a reasonable inquiry was made. AI-assisted drafting does not change what a reasonable inquiry requires; if anything, the documented pattern of AI hallucination in filings raises the baseline of what reasonable inquiry now includes. The partner who signs an associate’s AI-assisted brief without confirming the citations were verified is certifying to something the partner has not confirmed.
The partner carries supervisory exposure on top of the signing exposure. Under the rules of professional conduct, the partner is responsible for ensuring that the lawyers and nonlawyers the partner supervises conform to the rules. That responsibility now extends to how associates and paralegals use AI. A partner who has not set clear expectations for how AI-assisted work is verified and flagged inside the team is carrying a supervisory gap that the architecture makes more consequential, because the architecture puts AI inside more of the work.
AI hallucinations create a real and growing sanction and malpractice risk that the signing attorney bears most directly, documented across a rising count of cases in public trackers. The lesson for the partner is not the specifics of any one case. It is that the courts have consistently placed responsibility on the signing attorney regardless of who did the drafting and regardless of whether AI was involved. The partner who treats verification as the associate’s job alone has misread where the exposure sits. The signature is the partner’s. So is the certification.
The most protective practice at this role is requiring AI use to be made visible up the chain, so the partner’s verification step is informed rather than blind. If the partner does not know which parts of a draft came from AI output, the partner cannot focus where the checking is needed. The firms reducing this risk are the ones building the flagging practice into the workflow, not the ones relying on individual diligence under deadline pressure.
The next twelve months
More firm-level AI governance is moving from informal guidance to written policy. More partner attention to what the firm’s deployed workflow actually does, driven by supervisory exposure rather than curiosity. More malpractice and professional liability attention to AI-assisted filings. More divergence between firms that build verification into the workflow and firms that leave it to individual diligence. The decision to sign is not getting easier. The volume of work reaching it is going up.
Role 5: In-house counsel
On a Friday, the in-house counsel at a regional employer has two jobs running in parallel. One is the legal work: reviewing a vendor contract, advising the business on a regulatory question, managing outside counsel on a piece of litigation. The other is the policy work: the company’s employees are already using AI tools, the company is being asked to approve new AI features in the products it buys, and the in-house counsel is the person expected to set the rules. Both jobs run through the same stack, and the in-house counsel sits on both sides of it.
This role is different from the three litigation roles because the in-house counsel is not only a user of the architecture. The in-house counsel is also the person who decides how an entire workforce is allowed to use it.
The role, as user
As a practitioner, the in-house counsel does much of what the other roles do, often with a smaller team and a broader subject-matter range. Contract review, regulatory advice, employment questions, commercial disputes, board and governance support, and management of the outside counsel who handle what the in-house team does not. The in-house counsel drafts, reviews, and advises, frequently as a department of one or a few, which means the in-house counsel often has the solo lawyer’s no-second-reader problem inside a corporate structure.
The role, as policy-setter
The second job is what makes this role distinct. The in-house counsel is often the person the business turns to when it asks whether employees can use a given AI tool, whether a contract’s AI clause is acceptable, whether a vendor’s new AI feature creates a data or privilege risk, and what the company’s policy on AI use should be. Some companies route those questions through privacy, security, IT, procurement, or compliance instead, but in many companies, they land with in-house counsel. The in-house counsel is not setting policy for a legal team of a few people. The in-house counsel is often shaping policy for an entire workforce, most of which is not legally trained, and much of which is already using AI tools, whether or not a policy exists.
That dual position is the defining feature of the role. The in-house counsel feels the burden of checking as a user and the governance burden as a policy-setter at the same time.
The in-house counsel feels the checking burden as a user and owns the governance burden as a policy-setter, at the same time.
Work surface
In-house counsel often works within the company’s standard productivity environment, which, for many companies, is Microsoft 365 with Claude. Claude in Word for contract markups and advice memos. Claude in Excel for tracking matters, budgets, and outside counsel spend. Claude in Outlook for the heavy internal communication and an in-house role that runs across business units. Claude in PowerPoint for board and leadership presentations.
The work-surface question for this role is not only how the in-house counsel uses it. It is how everyone else in the company uses it. While Claude is available across Microsoft 365 in the company’s tenant, in-house counsel’s own use is just one of hundreds or thousands. The marketing team is drafting in Word with Claude. The finance team is modeling in Excel with Claude. The sales team is in Outlook with Claude. The in-house counsel is the person who has to think about what all of that means for privilege, confidentiality, data handling, and record retention across the business.
Workflow layer
The in-house counsel encounters the workflow layer from two directions. As a user, the in-house counsel may run practice-area plugins relevant to corporate and commercial work, and the named agents in the repository map onto in-house tasks: a Vendor Agreement Reviewer, a DPA Reviewer for data processing agreements, a DSAR Responder for data subject access requests, and an AI Use Case Triager. As a policy-setter, the in-house counsel is the person who has to decide which of these workflows the company sanctions, which it restricts, and what verification the company requires before relying on AI-assisted work product.
The architecture-stabilizing lesson is sharper for the in-house counsel than for any other role, because the in-house counsel is setting policy against a moving target. A policy written around what the stack did in May may not describe what it does in August. The in-house counsel who writes an AI policy as a fixed document, rather than as a reviewed and updated one, is governing a system that does not hold still.
Integration layer
Whether in-house counsel has integration-layer access depends on the company's size and litigation posture. A large in-house department with active litigation may carry CoCounsel Legal or Lexis+ with Protégé. A smaller department may rely on the work surface and outside counsel for grounded research. Either way, the obligation to read the authority is the same as every other role’s. Grounded retrieval reduces the fabrication rate; it does not remove the need to read the authority.
The integration-layer question unique to this role is vendor management. The in-house counsel is frequently the person reviewing the contracts and data-processing terms for the AI tools the company buys, including the legal-research tools the legal team itself uses. The in-house counsel is reading the CoCounsel Legal or Lexis+ with Protégé terms not only as a user deciding whether to trust the output, but also as counsel deciding whether the data-handling, confidentiality, and retention terms are acceptable for the company’s matters.
What this role should know
The in-house counsel carries the verification burden twice. Once, as a practitioner, where every AI-assisted contract markup and advice memo needs the same checking as any legal work needs, often without a second reader inside the department. And once as a policy-setter, where the in-house counsel is responsible for whether the broader workforce’s AI use creates risk the company has not addressed through vendor terms, internal policy, and employee training.
The privilege and confidentiality questions are the ones most specific to this role. When employees across the business use AI tools, in-house counsel must consider whether confidential or privileged information is being entered into systems whose retention, training, and access terms the company has not vetted. AI use can create privilege and confidentiality risk when sensitive information enters tools that the legal department does not control and has not reviewed, against the backdrop of a lawyer’s duty to protect client confidences. These are governance questions the architecture has made urgent because it has put AI inside the everyday productivity tools the whole company already uses.
The policy-setting role is where the in-house counsel can do the most good and carry the most exposure. A clear, current, and enforced AI policy that sets expectations for verification, confidentiality, and acceptable use is one of the most protective measures in-house counsel can build. A policy that is written once and never updated, or written for the legal team but not for the workforce, leaves the gap open. The in-house counsel is the person positioned to close it, and the person accountable if it stays open.
AI hallucination in legal filings is a risk that in-house counsel manages from the client side, through the outside counsel relationship. The in-house counsel who sets expectations with outside counsel about AI use and how its output is checked is managing a risk that, when it goes wrong, lands on the company’s matter and the company’s outcome. The growing record of AI hallucination cases is a reason for the in-house counsel to make verification an explicit term of the outside counsel relationship, not an assumed one.
The next twelve months
More in-house departments are writing and revising formal AI policies. More attention to privilege and confidentiality as AI use in the workforce scales within the Microsoft 365 environment. More vendor-management scrutiny of the AI terms in the contracts companies sign. More in-house counsel are setting explicit AI-verification expectations with outside counsel. More pressure on small in-house departments that carry the user burden and the policy burden at the same time, with limited resources. The architecture put AI in front of the whole workforce. The in-house counsel is the person who has to govern that and use it at once.
Looking ahead
The third and final sub-piece of Part 2 covers the three roles where the architecture meets the parts of the system with the fewest resources and the highest stakes: the litigation support specialist and eDiscovery professional who runs the data infrastructure of a case, the government attorney who works inside procurement and security constraints the private sector does not face, and the public-interest or legal aid lawyer who serves the clients least able to absorb an error. The architecture is the same. The constraints are not.
Sources
Anthropic, “Collaborate with Claude across Excel, PowerPoint, Word and Outlook,” May 7, 2026
Anthropic, “Claude for the legal industry,” May 12, 2026
Anthropic claude-for-legal GitHub repository, including commit 210fd7a, “Remove Lexis references at partner request”, May 12, 2026
Reuters, “Anthropic expands Claude’s AI tools for law firms, lawyers,” May 12, 2026
Thomson Reuters, CoCounsel Legal MCP Connector Guide
LexisNexis, “LexisNexis Expands Lexis+ with Protégé by Integrating Anthropic’s Claude Legal Plugin Suite,” May 13, 2026
iManage, “iManage MCP Server is now Available to Connect Governed Knowledge to the Broader AI Ecosystem,” May 14, 2026
Bloomberg Law, “Lawyers Apologize for Fake AI Quotes in Trump Mass Layoffs Case,” May 2026
Damien Charlotin, “AI Hallucination Cases Database“
American Bar Association, Model Rule 1.1, Competence
American Bar Association, Model Rule 1.6, Confidentiality of Information
American Bar Association, Model Rule 5.1, Responsibilities of Partners, Managers, and Supervisory Lawyers
American Bar Association, Model Rule 5.3, Responsibilities Regarding Nonlawyer Assistance
Federal Rule of Civil Procedure 11
A Note on Methodology: This piece is based on the sources cited below, including company announcements, public repository records, press releases, court-related reporting, and legal authorities. High-risk factual assertions, dates, and direct quotations were checked against the cited materials. The role profiles are analytical composites derived from the cited architecture and public reporting; they are illustrative, not statistical claims about all deployments. Where the architecture has not yet been deployed at a given role, that is identified directly. Where public announcement language differs from documented implementation scope, this article separates the broader framing from the narrower operational claim.
AI tools used in preparation. This article was drafted and revised with assistance from Claude and ChatGPT. Factual claims were checked against primary sources using Perplexity, ChatGPT, and DeepSeek. Copyediting was performed with Gemini. Editorial judgments, framing, and analytical conclusions are the author’s.
This article is for informational and educational purposes only. Nothing herein constitutes legal advice, and reading this article does not create an attorney-client relationship. Readers should consult qualified legal counsel for advice specific to their situation.
Copyright © 2026 Robert Meyers-Lussier. All rights reserved.