Legal Standard Governing Undocumented Founder Code Transfers Subject To Unresolved Promissory Reliance Claims

Undocumented founder code transfers leave copyright with authors under Section 204(a), exposing firms to reliance claims and non-exclusive license risks.

9 min

Writing

Federal copyright law separates software authorship from possession of a code repository through explicit statutory rules. Under Section 204(a) of the Copyright Act, an agreement transferring copyright ownership is invalid without a written instrument signed by the owner of the rights conveyed. An oral pledge between collaborators fails to assign intellectual property rights.

A developer who commits code to a shared production environment while relying on unexecuted equity promises retains legal title to those commits as the author. Without that signed document, statutory assignment cannot occur, leaving the enterprise with files it does not legally own.

Courts apply this rule strictly to early-stage technology companies where informal work precedes entity formation. When contributors write source code prior to incorporation or before executing formal proprietary information and inventions agreements, the author holds initial copyright under Section 201(a). An enterprise cannot fix the absence of a signed writing through later equity grants, board resolutions, or email threads discussing compensation.

Ownership remains anchored to the contributor until an executed document specifies the transfer.

A transfer of exclusive copyright rights without a signed writing leaves statutory ownership with the author regardless of corporate operational reliance.

The rules governing independent contractors make this boundary even sharper. Absent a common-law employment relationship, code contributed by a prospective partner is treated as independent contractor work. Under Section 101, the work-made-for-hire doctrine excludes software authored by non-employees unless both parties expressly agree in a signed written instrument that the work is a work made for hire, and the work falls into one of nine narrow statutory categories.

Outside instructional texts or collective works, software rarely qualifies under those categories. An enterprise relying on undocumented commits operates on borrowed architecture.

Graphite pencil lines render two tiny figures walking past a massive upright tool and a wound line on a pale gray vertical plane.

Statutory Writing Formalities in Source Architecture

To satisfy Section 204(a), the signed instrument must meet specific criteria. A signature can be executed electronically under the federal Electronic Signatures in Global and National Commerce Act, but the document itself must clearly state an intent to transfer intellectual property. Cryptographic commit histories, pull requests approved by maintainers, and developer tickets showing feature progress show that material was submitted, not that exclusive rights were assigned.

Courts consistently reject the idea that pushing code to an enterprise host constitutes assignment by conduct. Under federal standards, conduct alone transfers nothing. A contemporaneous written note stating that ownership transfers upon merging code turns the commit into a legal assignment; silence leaves the copyright with the author.

Shelf

An engineer might build features for eighteen months while equity documentation sits on a back burner. During that time, the repository fills with modules, schema designs, and algorithmic pipelines delivered without immediate cash compensation. The contributor provides these assets under the assumption that equity will follow the labor.

Meanwhile, the enterprise deploys the software into production, using shipped pull requests to demonstrate operational momentum.

Where an express assignment fails for lack of a signed writing, federal law constructs a non-exclusive implied copyright license to avoid immediate operational paralysis. Following Effects Associates v. Cohen, courts evaluate three objective criteria to determine whether a non-exclusive license exists:

  • Delivery of Protected Code occurs when the author hands complete source repositories to the enterprise without withholding access or encryption keys.
  • Creation at Enterprise Request requires evidence that the contributor wrote specific modules following product specifications developed alongside the commercial team.
  • Manifest Intent of Deployment involves conduct showing the author intended the software to be integrated into the enterprise product.

While an implied license shields the enterprise from immediate infringement liability, it conveys only limited, non-exclusive rights. The company gains the privilege to run the code, not exclusive control over it.

Graphite pencil and fine pen render a drawing featuring two tiny figures standing below a dark chair supporting an abstract geometric mass.

Non-Exclusive Licenses and Enterprise Fragility

Under federal copyright principles, non-exclusive implied licenses cannot be transferred to prospective buyers without the original author’s consent. An enterprise preparing for an asset sale or venture round often discovers that its core digital property sits on a revocable or non-assignable license. State contract law further complicates this baseline: while some jurisdictions treat an implied license backed by consideration as irrevocable, a license rooted in an unfulfilled promise of future equity rests on fragile ground.

The contributor retains the right to license identical architecture to commercial competitors. Delivering the code created working software for the business while preserving the developer’s legal right to use it elsewhere. Ultimately, the enterprise deployed an asset it cannot sell without permission, cannot pledge as collateral, and cannot protect if the creator duplicates it for someone else.

An implied license born of unfulfilled equity commitments grants the enterprise operational usage rights while denying it commercial exclusivity.

The software sits on enterprise servers, the product serves paying users, and the coder holds the underlying title until a financial settlement occurs. The parties may have built the platform together under the assumption that the equity allocation was already earned, but the legal title remains unassigned.

Promise

Detrimental reliance arises when informal founder discussions clash with later corporate restructuring. A prospective partner contributes critical software based on verbal assurances of a specific ownership stake, such as twenty percent of common shares upon incorporation. When the commercial founders later offer a one percent advisory grant or a contractor rate instead, the developer may invoke promissory estoppel under Section 90 of the Restatement (Second) of Contracts.

This claim requires a clear promise, reasonable and foreseeable reliance, and an injury that can only be remedied by enforcing the promise.

Graphite drawing features two disembodied hands measuring a torn slip with calipers above a tiny human figure standing on a surface.

Where Does Detrimental Reliance Create Equity Entitlement?

The main hurdle in promissory reliance claims is proving that a clear promise was made regarding equity. Early conversations among co-founders often involve general optimism about potential upside rather than precise mathematical commitments. Courts look at email exchanges, instant messages, cap table models, and pitch decks to determine whether the founders made a firm promise or merely expressed an intention.

Vague terms derail reliance claims. Statements that a founder will be “taken care of” or receive a “substantial stake” fall short of an unambiguous commitment. In contrast, when parties agree on a specific equity percentage, vesting schedule, and acceleration terms, the promise meets the standard for clarity.

A second obstacle is showing that the reliance was reasonable. Experienced software developers are generally expected to understand corporate formalities. An engineer who works for years without insisting on a written agreement will face arguments that relying on unwritten promises for so long is unreasonable as a matter of law.

In litigation, evidence of detrimental reliance usually falls into three categories:

  1. Forfeited Alternative Earnings involves proof of concrete job opportunities declined in order to build the software.
  2. Direct Financial Outlay includes server fees, software licenses, and development tools paid for out of pocket without reimbursement.
  3. Uncompensated Engineering Time covers documented hours delivered well below market rates.

Relief under promissory estoppel is discretionary. Courts can award expectation damages by granting the promised equity, or limit recovery to reliance damages by compensating the individual for the reasonable value of their work. The distinction between ordering equity delivery and awarding cash restitution determines whether the claimant ends up on the cap table or receives a delayed contractor fee.

Whether an oral equity promise can overcome state statutes of frauds governing securities transactions remains unsettled across several jurisdictions.

Three small dark figures stand beneath a massive upright metal shovel within a graphite pencil drawing crossed by a fine line bearing tally marks.

Preemption

Litigation over undocumented code transfers often creates tension between federal copyright law and state common law. Section 301(a) of the Copyright Act preempts state claims that seek rights equivalent to exclusive copyright protections. When a developer brings state claims for unjust enrichment, conversion, or quantum meruit based on unauthorized software use, courts evaluate whether the claim includes an extra element that changes its underlying nature.

Comparison of Federal Copyright Transfer Standards and State Promissory Reliance Doctrines
Legal Element Copyright Act Section 204(a) State Promissory Estoppel Quantum Meruit Claim
Doctrinal Source Federal Statutory Law State Common Law Equity State Quasi-Contract
Evidentiary Floor Signed written instrument Clear promise and reliance Reasonable value of services
Subject Matter Ownership of exclusive rights Detriment from broken pledge Unjust retention of benefit
Statutory Preemption Governs copyright directly Survives preemption test Frequently preempted
Form of Relief Title declaration or injunction Equity interest or reliance damages Restitution of market wage

Under the extra element test, a state claim survives federal preemption if it requires proof of qualitative elements beyond copying, distributing, performing, or displaying the work. Promissory estoppel survives because it requires proving an express promise and detrimental reliance. The claim focuses on broken commercial expectations rather than the exclusive right to reproduce code.

Unjust enrichment claims arguing that a company benefited simply by copying software modules are routinely preempted. The plaintiff must allege a benefit beyond basic copyright reproduction. Framing the dispute around uncompensated services turns it into a quantum meruit claim, which can clear the preemption hurdle.

A state claim avoids copyright preemption when its legal elements require proof of broken commercial promises rather than unauthorized software reproduction.

A contributor attempting to reclaim code repositories faces preemption if conversion claims simply mirror copyright infringement. While physical storage media can support a conversion claim, the intangible source code falls squarely within federal domain.

Equitable remedies are no substitute for an executed agreement when venture investors inspect corporate title.

Two tiny figures pass beneath a massive measuring rule intersecting a darkened display within this graphite drawing.

Tally

Resolving undocumented code contributions requires distinguishing clearly between past work and future corporate ownership. When an enterprise fails to secure written code assignments early on, the issue usually surfaces during due diligence. Venture capital firms require clear intellectual property rights before investing.

A single unresolved claim from an early developer can stall financing, force an expensive settlement, or require a complete rewrite of the codebase.

Clearing title to an unassigned repository requires a detailed intellectual property audit. Counsel must identify every commit submitted by unassigned developers, check commit timestamps, and review communications to define the disputed work. The company then faces three main options for clearing the cloud on its title:

A confirmatory assignment is the cleanest resolution. The contributor signs a retroactive agreement assigning all historical copyrights to the company. In return, the enterprise grants a defined equity allocation or a cash payment.

This replaces vague promises with explicit, binding terms.

If settlement negotiations fail, the enterprise must resort to technical isolation. Architects initiate a complete rewrite, removing every line of code written by the unassigned contributor. The engineering team conducts this work in a clean-room environment, documenting that the new software relies solely on fresh specifications without referencing the old repository.

The business incurs significant cost to rebuild architecture that a single early agreement would have secured.

Failing to formalize developer terms at the start virtually guarantees paying for the software twice: first in operational uncertainty, and later in a costly settlement or rewrite.

Six fields, each writing its own terms

The terms are written where they belong. Each field holds three desks, and every entry a desk writes raises the terms it uses, each term given a meaning, a mechanism and the places it appears. The record on these pages stays first person and hand made; the fields grow the nomenclature.