Who Owns the "Methodology Developed During Engagement" in the MG Consulting Contract — and Whether It Blocks the Sanity Check Field Study

The question

What does the MG consulting-services contract say about IP ownership for "methodology developed during engagement"? The MAC serialized field-study Sanity Check newsletter arc depends on the answer. (Surfaced as an open follow-up from [[2026-05-21-mammoth-client-field-study-feasibility]]; "MG" = Mammoth Growth, the founder's 1099 consulting client; "MAC" = RDCO's data-quality framework; "Sanity Check" = the RDCO newsletter.)

What we already know (from the vault)

• The executed contract's IP-clause text is NOT in the vault. The feasibility brief flagged this exact question as an open follow-up and pointed to an "internal-review doc [that] may already have this." On inspection, the pointed-to doc does not contain it. See [[2026-05-21-mammoth-client-field-study-feasibility]].
• The referenced "internal-review" doc is a technical architecture review, not a legal/IP review. [[internal-review-mg-harness-cc-wrapped-2026-04-13]] grades the cc-wrapped agentic harness (architecture, skill depth, security) and characterizes it as the founder's "prior art in agentic tooling — the work that preceded RDCO's setup." It quotes NO contract language, no assignment clause, no work-for-hire terms. The feasibility brief's claim that this doc "governs IP boundary... settled cleanly Apr 23" overstates what the file actually holds — a documentation gap worth correcting in the feasibility doc.
• The vault already draws the publishable line at methodology-vs-identity, not ownership. The feasibility brief's convergence: the technical pattern (MAC 3x6 matrix, PRO-303-style dual-path override) is methodology the founder "independently developed" and applied across engagements; column names, table names, and BRD content are client-confidential. The publishable artifact splits at exactly that line. See [[2026-05-21-mammoth-client-field-study-feasibility]].
• MG senior leadership has used permission-adjacent language about the work — but that is not a contract term. Dylan Cruise on record calling the harness the founder's "brainchild"; Tom Clinton crediting "foundational work in all of the agentec processes." Endorsement, not a written IP release. See [[2026-05-05-sendoff-testimonials]].
• The MAC landing-page spec already enforces the strictest posture: a grep audit blocking "Mammoth", "Progress", "Nutrafol", "gold_opp_pipeline", "silver_fct_*". This is stricter than any NDA requires and is the safe default for a public product page; the Sanity Check field study is a different surface. See [[2026-05-05-build-spec]].

What the web says

• Default rule cuts toward the consultant, not the client. Absent an express written agreement, whoever authors/invents IP owns it — for a 1099 independent contractor that is the contractor, not the hiring party. Client ownership requires an affirmative written assignment. (KTS Law, https://ktslaw.com/en/Insights/Alert/2017/8/4-Key-Takeaways-Consulting-Agreements-Who-Owns-the-IP)
• "Work made for hire" rarely applies to analytics/software work. For contractors the WMFH doctrine only reaches nine narrow statutory categories (none of which is software or a data-engineering deliverable) and only with an express written agreement; the real ownership-transfer mechanism is a present-tense assignment clause. (Cornell LII, https://www.law.cornell.edu/wex/work_made_for_hire; KTS Law, same)
• Background IP is typically retained by the consultant; foreground IP is typically assigned to the client. Background = pre-existing methodologies, frameworks, tools the consultant brought in. Foreground = deliverables built specifically for the client using the client's confidential data (process maps, custom models, roadmaps). (Genie AI, https://www.genieai.co/en-us/blog/intellectual-property-rights-in-operations-consulting-engagements-who-owns-what)
• "Generalizable methodology stripped of client confidential information" is the standard consultant carve-out. Even where the client owns the specific deliverable, standard practice lets the consultant retain and reuse the general methodology once client-specific data is removed. (Genie AI, same)
• The residuals clause is the mechanism that permits reuse of retained know-how. A residuals/residual-knowledge clause lets personnel use ideas, concepts, know-how, and techniques left in genuine unaided memory — limited to general professional skills and methods, NOT intentionally memorized or systematically extracted specifics, and it does NOT override the tangible-information confidentiality obligations. (Terms.Law, https://terms.law/NDA/clause-library/residuals-clause.html; Morgan Lewis, https://www.morganlewis.com/blogs/sourcingatmorganlewis/2025/08/residuals-clauses-vs-feedback-licenses-getting-the-balance-right-in-ip-agreements)
• Ownership and confidentiality are two separate legal surfaces. Who owns the methodology and whether the founder may disclose engagement-specific facts are governed by different clauses (IP/assignment vs confidentiality/NDA). A publication can be clean on ownership yet still breach confidentiality, or vice versa. (Genie AI + Terms.Law, above)
• The general-vs-specific boundary is real but hard to police. Practitioners note the line between legitimately retained general knowledge and improperly extracted proprietary specifics is "blurry"; documenting the background/foreground split up front is the standard risk-reducer. (Terms.Law, above)

Convergences and contradictions

• Convergence: the vault's own methodology-vs-identity split maps cleanly onto the web's background-IP / residuals framework. The MAC method (framework, matrix, override pattern) reads as retained background IP + residual know-how; the client's column names, table names, and BRDs read as foreground/confidential. Both sources locate the publishable line in the same place.
• Contradiction (internal): the feasibility brief treats the IP boundary as "settled," but the doc it cites contains no contract terms — the boundary is characterized, not verified against the executed agreement. The "settled" framing is stronger than the evidence supports.
• Caveat: the default rule and the background/foreground norm are only defaults. A broadly drafted assignment clause ("all work product, materials, and methodologies conceived during the engagement are assigned to Client") can override the default and sweep in methodology unless a residuals/retained-rights carve-out exists. Only the executed contract settles which way MG's clause was drafted.

Synthesis for RDCO

Does the field-study arc face an IP blocker? Most likely no — but the definitive answer is not in the vault, and it must be read before publication, not inferred. The dominant risk on a serialized field study is the confidentiality surface (disclosing client-identifying facts), which the vault's anonymization discipline and the MAC grep-audit already address. The ownership surface is the secondary risk, and under standard consulting norms it favors the founder: the MAC framework is background IP / retained methodology, and even where MG owns a specific deliverable, the general method stripped of client identifiers is normally the consultant's to reuse and publish. Nothing found here suggests a structural blocker to a properly anonymized methodology piece.

The reason this cannot be closed from the vault is that MG's actual clause could be drafted more broadly than the default. A minority of consulting agreements assign not just "deliverables" but "all work product and methodologies conceived during the engagement," with no residuals carve-out. If MG's contract reads that way, the ownership question flips and even anonymized methodology publishing needs express written permission. The vault's "internal-review doc" does not resolve this because it never quoted the contract — it reviewed the harness architecture. So the honest status is: the specific terms are unverified; do not treat the boundary as settled until a human reads the executed 1099 consulting-services agreement.

Exactly what the founder must verify in the executed contract (three clauses, in priority order): (1) the IP / work-product / assignment clause — does it assign only "deliverables/work product" (safe) or does it also sweep in "methodologies, know-how, or improvements conceived during the engagement" (blocker without a carve-out)? (2) any residuals / retained-rights clause — look for language like "Consultant retains all general knowledge, skills, experience, know-how, and methodologies," which is the affirmative right to reuse and is the single most load-bearing sentence for the field study. (3) the confidentiality clause's definition of Confidential Information and its standard exclusions (public knowledge, independently developed, rightfully obtained from third parties) — this governs what engagement facts may be disclosed regardless of who owns the method.

Recommended posture, unchanged from the feasibility brief but now with the legal frame attached: proceed on Path 2 (anonymized field study, methodology-focused, client identifiers scrubbed) AND close two gaps before Episode 1 publishes — (a) the founder reads the three clauses above from the executed contract, or a subagent extracts them if the PDF is in Drive/email; and (b) the one-question permission conversation with Dylan/Tom the feasibility brief already recommends. Ownership favors the founder by default; the contract read confirms the default wasn't contracted away; the Dylan/Tom conversation covers the confidentiality-and-relationship surface. All three are cheap; none individually blocks drafting the anonymized episodes, but the contract read must precede publication.

Why this is in the vault

Gates the MAC serialized field-study Sanity Check arc: it establishes that the IP-ownership default favors the founder, but that publication must not proceed until the executed MG 1099 agreement's assignment, residuals, and confidentiality clauses are read. It names the three exact clauses to check, which turns a vague legal worry into an actionable pre-publication gate.

Open follow-ups

• Where is the executed MG 1099 consulting-services agreement stored (Google Drive, email, physical)? Locate it so a human — or a scoped subagent — can extract the three clauses verbatim.
• Does MG's IP clause assign only "deliverables/work product" or also "methodologies conceived during the engagement"? This single distinction decides whether a residuals carve-out is needed.
• Is there an explicit residuals / retained-rights clause ("Consultant retains general knowledge, skills, and methodologies")? If yes, the field study is on solid ownership footing.
• Does the cc-wrapped harness IP boundary explicitly cover authored content about the harness, or only the harness code? Sanity Check Episode 5 (the harness-adoption story) depends on this and is not answered by the architecture review.
• Could the founder pre-clear a single canonical anonymization + methodology-publishing protocol with MG that covers ALL future episodes, rather than per-episode permission?

Related

• [[2026-05-21-mammoth-client-field-study-feasibility]] — the parent feasibility brief that surfaced this question and set the Path-2 recommendation
• [[internal-review-mg-harness-cc-wrapped-2026-04-13]] — the "internal-review" doc the feasibility brief pointed to; is an architecture review, contains no contract IP terms
• [[2026-05-05-build-spec]] — MAC landing-page spec enforcing the client-identifier grep audit (strictest posture)
• [[2026-05-11-practitioner-newsletter-acquisition-tactics]] — where the case-study-over-synthetic (Mechanic 5) preference originated

Sources

Vault:

• ~/rdco-vault/06-reference/research/2026-05-21-mammoth-client-field-study-feasibility.md
• ~/rdco-vault/06-reference/internal-review-mg-harness-cc-wrapped-2026-04-13.md
• ~/rdco-vault/01-projects/mac-landing/2026-05-05-build-spec.md
• ~/rdco-vault/06-reference/research/2026-05-11-practitioner-newsletter-acquisition-tactics.md
• ~/rdco-vault/01-projects/mammoth-growth/2026-05-05-sendoff-testimonials.md

Web:

• KTS Law — 4 Key Takeaways: Consulting Agreements, Who Owns the IP: https://ktslaw.com/en/Insights/Alert/2017/8/4-Key-Takeaways-Consulting-Agreements-Who-Owns-the-IP
• Genie AI — IP Rights in Operations Consulting Engagements: Who Owns What: https://www.genieai.co/en-us/blog/intellectual-property-rights-in-operations-consulting-engagements-who-owns-what
• Terms.Law — Residuals Clause (standalone NDA clause): https://terms.law/NDA/clause-library/residuals-clause.html
• Morgan Lewis — Residuals Clauses vs. Feedback Licenses: https://www.morganlewis.com/blogs/sourcingatmorganlewis/2025/08/residuals-clauses-vs-feedback-licenses-getting-the-balance-right-in-ip-agreements
• Cornell LII (Wex) — Work Made for Hire: https://www.law.cornell.edu/wex/work_made_for_hire
• BCLP — Contracting with consultants, how to protect your IP rights: https://www.bclplaw.com/en-US/events-insights-news/contracting-with-consultants-how-to-protect-your-ip-rights.html