GARPedia

/examples/ungoverned-vs-governed

Ungoverned vs. governed

The same question about the Heppner ruling, answered twice. The left pane is an authored illustration of how an ungoverned answer can fail: a fabricated citation, an overconfident characterization of the holding, and an invented quotation, each marked and explained. The right pane is not an illustration — it is the real admitted claims, the real refused candidate, and the real receipt for HEPPNER-LIFECYCLE-0001, rendered from the governed record itself.

One question

Did the Heppner court hold that using an AI assistant to prepare legal documents defeats attorney-client privilege and work-product protection?

Ungoverned

An illustrated ungoverned answer

The court in Heppner held that any use of an AI assistant to help prepare a legal document automatically destroys both the attorney-client privilege and the work-product doctrine for that document [1]. As the court put it, “reliance on an artificial-intelligence tool for legal drafting is per se incompatible with a claim of confidential attorney-client communication” [2]. This categorical rule follows the reasoning in Matter of Doe Legal Services Corp., 407 F. Supp. 3d 512, 519 (S.D.N.Y. 2021), which the Heppner court cited as controlling precedent for treating AI-assisted work the same way as work shared with an outside vendor [3]. Practitioners should therefore assume that any AI-assisted drafting is automatically discoverable, regardless of the facts of a particular case.

  1. 1overconfident holding

    The real ruling turned on this record's specific facts — that the AI tool is not an attorney, and that the documents were not prepared by or at the behest of counsel — not on a categorical rule that any AI use forfeits privilege. A candidate proposing exactly this broader rule was refused; see the governed pane.

  2. 2invented quotation

    No such quotation appears in the source filing. The real anchored quotations are the sentences shown in the governed pane, each tied to a specific page of the public document through a citation span.

  3. 3fabricated citation

    This case citation does not exist. The governed record cites only the single source document underlying this proofcase, with a public docket URL and a pinned PDF digest — no secondary case law is cited at all.

This is an authored illustration of known ungoverned failure patterns (a fabricated citation, an overconfident characterization of a holding, and an invented quotation). It is not the captured output of any named model or product, and it names no vendor.

Governed

Heppner AI privilege ruling: governed claim lifecycle

Admitted claims

  • candidate:heppner:ruling

    The court ruled that Heppner's AI Documents were protected by neither attorney-client privilege nor the work product doctrine.1

    Admitted-claim page
  • candidate:heppner:claude-not-attorney

    The court concluded that Claude was not an attorney and treated that fact as sufficient to defeat Heppner's attorney-client privilege claim.2

    Admitted-claim page
  • candidate:heppner:work-product-behest

    The work-product ruling rested in part on the AI Documents not being prepared by or at the behest of counsel and not reflecting counsel's strategy.3

    Admitted-claim page

Citation spans

  1. 01span:anchor:heppner:doc27:p1:ruling
    the written exchanges were not protected by either the attorney-client privilege or the work product doctrine
    fragment
    anchor:heppner:doc27:p1:ruling
    source
    PUBLIC-SRC-HEPPNER-DOC27United States v. Heppner, document 27
    verification
    verbatim verified
    supports
    heppner-initial-state

    Public source page 1; initial capture anchor.

  2. 02span:anchor:heppner:doc27:p5:claude-not-attorney
    Because Claude is not an attorney, that alone disposes of Heppner's claim of privilege
    fragment
    anchor:heppner:doc27:p5:claude-not-attorney
    source
    PUBLIC-SRC-HEPPNER-DOC27United States v. Heppner, document 27
    verification
    verbatim verified
    supports
    heppner-initial-state

    Public source page 5; initial capture anchor.

  3. 03span:anchor:heppner:doc27:p9:work-product-behest
    the documents were not prepared by or at the behest of counsel, nor did they reflect defense counsel's strategy
    fragment
    anchor:heppner:doc27:p9:work-product-behest
    source
    PUBLIC-SRC-HEPPNER-DOC27United States v. Heppner, document 27
    verification
    verbatim verified
    supports
    heppner-revised-state

    Public source page 9; supplemental capture anchor.

  4. 04span:anchor:heppner:doc27:p12:case-specific-conclusion
    Heppner's use of Claude fails to satisfy either of these rules
    fragment
    anchor:heppner:doc27:p12:case-specific-conclusion
    source
    PUBLIC-SRC-HEPPNER-DOC27United States v. Heppner, document 27
    verification
    verbatim verified
    supports
    heppner-scope-boundary

    Public source page 12; supplemental capture anchor.

engine layerWhat the engine considered and refused

The spine routed each candidate claim, declined to admit the ones it could not support, and recorded the reason. These refusals are mechanical: the engine emitted them, and they are carried into the receipt below.

  • candidate:heppner:universal-ai-privilege-rulefinal

    recorded refusal reason

    final refusal: the universal proposition is broader than the case-specific memorandum and has no supporting anchor

Refused-candidate page
engine layerSovereignty receipt

The receipt is what lets a reader know no machine quietly made up the answer: it names the operation, the artifact hashes it produced, and the class of output it was allowed to emit.

receipt id
sovereignty_receipt:heppner-public-proof.v0_1:revised
operation kinds
selectquoteselectquoteselectquoterefuse
artifact hashes
  • context_packet_hash

    sha256:3b886764a7b07a509197ff37708e9aa39ff7f119ecd9e4bad833bdc5b314b37d

  • packet_inspection_hash

    sha256:344bfbb383b51f0d95e8e0a386e513bed4d194b002a0af0a3157821b79a049ca

  • packet_walk_hash

    sha256:94d3ec5c82661b27dfb749fe77e0e7646d5ca6189c029089e61698b091a7f4a9

  • rendered_packet_body_sha256

    sha256:ce2c9956bfa916f7204a1ed5ed4a38a3eb7a7b6ca451638fe772b44b5bc07c66

  • rendered_packet_hash

    sha256:af5265465c37cafb0cce63c82d0630d5f024271069b44b1cbed2c7e0419cf93b

  • source_capture_hash

    sha256:5fea7192b2dd8399bb121e43772f50e472de801a751415ea6080161c2eee8c63

  • sovereignty_receipt_hash

    sha256:d1b8194b71e95839a67496cfc66ffafc19d909f8b527185d648acc6f9dd49767

Independent verification (verification workbench)