Resolving Revocable Tacit License Exposure in Legacy Codebases After Employee Departures
A company resolves tacit license exposure by replacing oral permissions with written retroactive assignments or clean-room reimplementations.

Severance
Holding a git repository is not the same as owning the copyright in its trees. An engineer can spend years pushing commits without ever signing an intellectual property agreement; when they leave, the company retains the files, build scripts, and compiled binaries, but statutory title to the code stays with the author under federal copyright law. Section 204(a) of the United States Copyright Act provides that a transfer of copyright ownership is invalid unless an instrument of conveyance, or a note or memorandum of transfer, is in writing and signed by the owner of the rights conveyed.
Without that signature, title never moves. The company is left running on an implied, non-exclusive license created purely by conduct.
State contract law and federal copyright statutes operate on different tracks. Delivering source code to a shared repository grants permission to run the software, but because that permission stems from conduct rather than explicit consideration paid for an irrevocable transfer, the law treats it as an implied, non-exclusive license. Without independent consideration, that license can be revoked at any time by the author.
A tacit license granted without independent consideration remains revocable at the author’s discretion.
Two conflicting versions of the arrangement tend to surface during the exit interview. The enterprise views the history as straightforward work for hire, assuming wages bought clear ownership of every asset created. The engineer remembers building early prototypes on personal hardware before incorporation, writing foundational libraries on nights and weekends before human resources ever issued confidentiality and assignment agreements.
Both perspectives existed from the beginning, but routine work and regular payroll kept the disagreement hidden.
- Statutory title retention leaves copyright with the contributor whenever code is written outside formal common-law employment or before a written assignment is executed.
- Bare implied permission lets an enterprise compile and run code delivered with the contributor’s knowledge, but leaves distribution rights exposed to formal revocation at any point.
- Retroactive assignment exposure arises when later employment agreements omit explicit quitclaim language covering commits made prior to hire.
A resignation brings that exposure to the surface, leaving commercial services dependent on code that the original author can formally demand removed from production servers.
The code was effectively on loan while the relationship worked, and that loan ends with the resignation.

Wire
Repository architecture mirrors the underlying legal fractures. Every commit forms a cryptographic snapshot pairing an author string and timestamp with a parent hash, but that metadata cannot prove whether the contributor was an employee under agency law or a contractor working informally. In an equity financing, initial public offering, or acquisition, external counsel matches those commit dates directly against the effective dates of signed proprietary information agreements.

What Leaves the Building With an Unsigned Contributor?
Hardware stays behind, but the right to exploit the software commercially walks out with the contributor. While an implied license shields the company against infringement claims for past releases because the engineer consented to the initial commits, revocation ends that protection immediately. Once a formal letter withdraws the license, subsequent container builds, server deployments, and customer downloads become actionable copyright infringement under federal law.
Revocation converts subsequent commercial software distribution into actionable statutory infringement.
Failure to purge the contested routines exposes the enterprise to statutory damages and injunctive relief. Equitable defenses like estoppel rarely hold up. Federal courts require proof that the copyright holder knew the company claimed exclusive ownership, intended the company to rely on that belief, and that the company suffered detriment as a result.
Silence through product launches and funding rounds does not meet that standard against a registered author.
| Evaluation Attribute | Executed Written Assignment | Tacit Implied License |
|---|---|---|
| Statutory Grounding | 17 U.S.C. 204(a) compliant signed transfer instrument | Judicially created doctrine based on mutual conduct |
| Right of Revocation | Irrevocable asset transfer absent contractual breach | Revocable at author will absent independent consideration |
| Sub-licensing Authority | Full corporate power to license or transfer code | Non-transferable permission limited to internal deployment |
| Acquisition Due Diligence | Clean title verification through personnel records | Material closing condition requiring clean-up signatures |
| Litigation Exposure | Breach of contract claims governed by state rules | Statutory copyright infringement and federal injunctions |
When institutional acquirers identify unassigned intellectual property in mission-critical repositories, transaction momentum stops. Valuations fall to account for replacement engineering, and indemnity escrows expand to absorb potential infringement liabilities.

Audit
Remediation starts with a forensic review of the repository. Evaluating tacit license risk cannot be done through high-level architecture diagrams or executive interviews; counsel has to examine the version control tree file by file, tracing every contributor back to an executed agreement that predates their first pull request.
Commit histories provide an immutable record of origin. In systems that originated in incubators, dorm rooms, or hackathons, the earliest files usually carry the heaviest concentration of unassigned work. Those early commits frequently contain the core database schemas, persistence layers, and networking interfaces that the rest of the application rests on.
A complete repository audit correlates git author signatures with signed company covenants across every historical branch.
A structured isolation sequence segments the codebase into measurable liability zones:
- Commit author cross-referencing checks email metadata against payroll records to catch commits pushed before employment agreements took effect.
- Line attribution extraction runs blame tools to separate surviving legacy lines from later refactors and third-party libraries.
- Architectural coupling analysis evaluates how tightly those legacy routines bind to customer services to see whether modular extraction is practical.
When an audit reveals code written without signed transfer documents, management faces two choices: negotiate a retroactive assignment with the author or execute a clean-room reimplementation before a revocation notice arrives.
Unassigned code also creates immediate breach of standard intellectual property warranties in enterprise customer contracts, which routinely warrant that the software infringes no third-party rights.

Novation
Securing clean title after an engineer leaves requires a negotiated confirmatory assignment. A unilateral waiver drafted by company counsel means nothing if the author refuses to sign it. Obtaining that signature months or years after the fact requires fresh consideration, because past wages and expired equity grants do not satisfy contract requirements for a new transfer under state law.
Consider an early software architect who wrote twenty thousand lines of routing infrastructure during the six months before incorporation. If that architect worked for a modest hourly stipend without a signed agreement, left on poor terms, and saw unvested equity expire unexercised, any subsequent Series B financing that demands clear title warranties brings the omission to a head.
Requesting a retroactive signature on a standard assignment form leaves leverage entirely with the author, who can condition execution on cash, renewed equity, or consulting retainers at rates that climb each quarter.
A confirmatory assignment executed post-departure requires fresh consideration to extinguish the author’s statutory rights.
If negotiations break down, clean-room reimplementation is the standard operational alternative. The procedure insulates the engineering team from copyright claims by dividing functional analysis from code generation. A specification group examines the legacy code to document its inputs, outputs, and behaviors without copying implementation syntax; a second development group, with no prior exposure to the original files, writes replacement modules based solely on those functional specs.
That structural separation between teams neutralizes substantial similarity arguments in copyright litigation. Swapping out contested modules with clean-room code extinguishes implied license exposure permanently, allowing the enterprise to retire legacy codebases without negotiating under settlement pressure.
Leaving unassigned code in an active delivery pipeline increases replacement costs over time as new engineering builds directly on top of its interfaces.

Vault
Decommissioning unassigned assets demands permanent isolation in the version control system. Deleting files from the main branch leaves historical commits untouched in git object storage, and a git revert only adds a commit that removes lines while preserving the author log underneath. The contested tree remains present across every developer clone.
Full remediation requires rewriting repository history. Engineering teams use filter tools to purge unassigned files from every branch, tag, and ref across remote origins and local checkouts. Because rewritten hashes break downstream branches, developers must re-clone from the sanitized repository base.
Sanitizing commit history achieves nothing if the original code continues running on production servers or customer instances. Build pipelines must pull strictly from branches where every commit connects to a valid assignment agreement. An encrypted, read-only backup of the pre-scrubbed repository is placed in an access-restricted archive so counsel retains an evidentiary record should title ever be disputed.
While system architectures evolve quickly, underlying legal liabilities survive refactoring. Resolving tacit licenses through clean-room reimplementation or formal, compensated assignments restores legal title and commercial certainty to the software assets.
Whether an author who accepted employment wages without signing an assignment can defeat an equitable estoppel defense when revoking a license against an acquirer remains unsettled across federal courts.