Auditing Git Logs Against Corporate Invention Assignment Contracts
Technical repository audits inspect author timestamps and hardware artifacts to enforce corporate ownership under employee invention agreements.

Stamp
An engineer inspects the terminal window at midnight, looking at commit hashes generated over three years of salaried employment. A prospective investor has requested full repository access to evaluate the intellectual property portfolio before wiring seed capital. Every entry in the log records an author date, a committer date, an email address, and an absolute UTC offset.
The employer provided a steady wage, hardware allowances, and equity vesting schedules during those months. Alongside those benefits was a proprietary inventions assignment agreement establishing legal ownership over everything conceived or reduced to practice during the employment term.
Technical auditors hired by venture funds or acquiring corporations work backwards from the raw Git object database rather than starting with interview transcripts. They extract tree objects, commit objects, and tag metadata to measure whether outside development occurred while the author was drawing a corporate salary.

Forensic Chronology in Version Control Histories
Inspectors examining an intellectual property chain trace every modification to the second. Version control systems record two independent temporal markers for each change set: the moment an author crafts a patch, and the moment a committer applies it to a branch. In standard local development, these values match.
When an engineer stages code locally during a weekday afternoon and delays pushing until midnight, the author date retains that afternoon timestamp.
An engineer who pushes commits through personal credentials during working hours hands the employer presumptive title to the entire repository.
Corporate legal teams match these timestamps against badge swipe records, video call calendars, Slack activity logs, and corporate Jira tickets. A commit timestamped at two in the afternoon on a Tuesday creates a clear evidentiary vulnerability. The engineer may claim the work occurred during lunch or a break, but corporate invention contracts routinely define working hours as any time spent on employer business or any hour during standard business operations.
Weekday commit timestamps create an immediate presumption that company time funded the work.

Discrepancies Between Author and Committer Records
Programmers frequently manipulate client clocks or write code offline during corporate flights. When an engineer manually changes the system clock or overrides the author date environment variable, the committer date remains pinned to the actual time of merge or rebase. Auditors write scripts to flag gaps exceeding twenty-four hours between these two fields.
A wide gap signals intentional timestamp alteration or historical revision. During technical due diligence, altered timestamps convert an ordinary intellectual property review into a forensic investigation. The company funded the salary that kept the household solvent during those exact months, and code written between nine and five belongs to the entity that paid for those hours.

Device
Corporate equipment leaves unmistakable signatures across modern build environments. When an operator checks out an outside repository on a company laptop, the operating system registers file creation dates, user account names, and hardware identifiers in file system journals. Shell configuration files frequently inject corporate credentials, internal proxy configurations, or enterprise single-sign-on tokens into repository settings.
The employer provided the machine to advance its own commercial objectives, not as a personal gift. Accepting the hardware bound the recipient to corporate property policies. When private software touches corporate iron, the boundary separating independent invention from corporate asset dissolves.

Hardware Allocation and Employer Property Claims
A company laptop issued on an engineer’s first morning carries legal attachments across its operating life. Most corporate invention assignment contracts state that any invention developed using company equipment, facilities, or trade secret information belongs entirely to the employer. This claim applies regardless of whether the work occurred at three in the morning on a Sunday or inside a personal residence.
The physical hardware belongs to the employer, and anything produced through it falls under the employer’s claim of ownership.
Technical auditors examine Git commit metadata for clues about the execution environment. Global Git configuration settings often embed employer user names or corporate email handles into personal projects. An audit scans history for old commits authored under an enterprise domain, even if later commits used a personal handle.
A single commit containing a corporate email address establishes that corporate credentials, and likely corporate hardware, were active during that development cycle.

Does Prior Inventions Disclosure Shield Later Commits?
Exhibit schedules attached to initial hiring agreements rarely protect work produced during active tenure. When starting a role, technical employees routinely list prior inventions on an Exhibit A form to carve out existing software from the employer’s assignment scope. Founders often believe listing a project on Exhibit A grants permanent immunity to continue building that project while employed.
- Vague descriptive scope leaves the boundary undefined, allowing corporate counsel to assert that ambiguous notes failed to exclude subsequent architectural designs.
- Omission of specific repositories forfeits the presumption of independent development once an engineer continues committing to preexisting projects.
- Unsigned disclosure exhibits nullify statutory protections when dispute resolution demands verified documentation from the commencement date.
- Subsequent feature additions introduce newly authored modules that postdate the hiring signature, transferring title of incremental improvements to the employer.
A signed schedule of prior inventions excludes only the specific systems identified before the first employment date.
The disclosure form freezes a snapshot of code completed before the first day of employment. It does not license the employee to build new modules for that project on evenings and weekends during the employment term. Commits authored after the start date represent newly created intellectual property, and each must independently clear contractual assignment hurdles.
A founder facing an unseparated hardware record often concedes equity or accepts escrow holdbacks during series financing to extinguish title claims.

Scope
Employment contracts draw wide circles around technical ingenuity. The typical Corporate Invention Assignment Agreement covers any invention related to the actual or demonstrably anticipated business, research, or development of the employer. If a software engineer works for an enterprise database vendor and builds a private developer tool on personal hardware, corporate attorneys argue the tool falls within the company’s anticipated expansion lines.
In institutional research on psychological contracts and invention assignment compliance, technical staff routinely exhibit an asymmetrical assumption of ownership, believing unpushed side projects developed on personal time remain private. This empirical observation rests on survey and deposition analysis across Silicon Valley software enterprises during trade secret discovery. Explicit corporate onboarding that verifies employee comprehension of invention assignment perimeters would alter these behavioral defaults.

Statutory Carve Outs and Demonstrable Business Lines
State protections set explicit perimeters around off-duty employee labor. California Labor Code Section 2870, along with parallel statutes in states such as Washington, Illinois, and New York, restricts the reach of corporate assignment clauses. Under California law, an employer cannot claim an invention developed entirely on the employee’s own time without using employer equipment, supplies, facilities, or trade secrets, unless the invention relates to the employer’s business or results from work performed for the employer.
An empirical examination of intellectual property litigation records in federal district courts regarding employee inventions demonstrates that courts treat code authored during core business hours on corporate networks as presumptive employer property. This finding rests on appellate cases interpreting California Labor Code Section 2870 and Delaware commercial disputes involving salaried technical staff. A statutory revision defining working hours strictly by logged billable minutes rather than chronological business hours would shift this evidentiary presumption, as would appellate rulings segregating home network packet transit from employer administrative dominion.
Code produced on private machines forfeits protection the moment it touches corporate communications infrastructure.
The business relation test remains the most contested issue in repository audits. If an engineer designs an algorithm that optimizes cloud data caching, and the employer sells cloud storage infrastructure, the statutory exemption fails because the work relates directly to the employer’s business. In an audit, counsel will cross-reference every commit message against internal product roadmaps to prove the departing engineer solved a problem the employer was actively researching.

Forensic Indicators in Corporate Assignment Contests
Technical diligence teams weigh distinct categories of evidence when evaluating repository provenance. The intersection of technical artifacts and legal definitions determines whether a title defect threatens an upcoming transaction.
| Evidentiary Category | Delaware Common Law Standard | California Labor Code 2870 | Negotiated Moonlighting Carve-Out |
|---|---|---|---|
| Hardware and Facility Use | Any use assigns invention to employer | Any use forfeits statutory exemption | Permitted within written threshold boundaries |
| Chronological Origin | Presumed employer property if salaried | Must occur entirely on employee time | Excludes logged employer project sprint hours |
| Business Alignment | Broadly covers all software capabilities | Tied to current or anticipated product lines | Strictly confined to named competitive domains |
| Audit Proof Requirement | Employee carries burden to prove independence | Employer demonstrates direct business connection | Verified commit log matches carve-out schedule |
A written waiver signed by an executive officer expressly relinquishes corporate interest in the designated repository, restoring clean title to the departing engineer.

Trace
Version repositories preserve an unvarnished record of human habits, as code retains its origins beyond narrative claims. When an engineer prepares to leave employment and launch a startup, a common impulse is to cleanse the Git history by squashing commits, rebasing branches, or generating a brand-new repository with a single initial commit carrying modern timestamps.
Software builders often attempt to conceal corporate overlap through interactive git rebasing and forced pushes, but this practice creates severe evidentiary liabilities. Modern forensic auditors do not merely read the active main branch; they run low-level analyses on Git packfiles, unreferenced dangling commits, and local reflogs. Maritime logbooks historically recorded ship coordinates at solar noon because navigation laws treated unrecorded movements as abandoned cargo.
Modern version control operates under identical discipline, where every recorded snapshot establishes a timestamped record.

Scrubbed Histories and Cryptographic Verification
When Git rewrites history, it creates new commit hashes while abandoning old commit objects in the repository’s internal object store. Unless the author executes an aggressive garbage collection sequence, those dangling objects persist on disk. An auditor runs git fsck –lost-found to uncover every abandoned commit, exposing original author timestamps, commit messages, and intermediate code changes.
It remains uncertain whether squash-merging a dirty Git tree into a single clean commit prior to public repository publication legally extinguishes the chain of title for components drafted during active employment when the reflog has been expunged. Under this uncertainty, a prudent founder commissions an independent clean-room rewrite rather than betting an enterprise valuation on an expunged commit tree.
A rebased repository preserves its original author dates in the reflog until the garbage collector runs.
Cryptographic commit signatures introduce an additional layer of verification. When developers sign commits using GPG or SSH keys, the signature seals the author name, committer name, timestamp, and tree hash. If an engineer uses a signing key generated on an employer laptop, that signature links the commit directly to the corporate environment.
Stripping signatures during history rewrites draws immediate suspicion from technical diligence teams, who treat altered commit histories as evidence of spoliation.

The Presumption of Concealed Labor
Institutional investigations treat missing chronological links as intentional evidentiary spoliation, knowing that commit metadata survives local deletion. When diligence teams encounter an application whose repository begins with a massive, fifty-thousand-line initial commit dated three days after an engineer resigned, they demand the preceding development history.
- Audit trail inspection reveals local timezone discrepancies across committer records, signaling attempts to disguise daytime coding during remote work hours.
- Cross reference analysis links public cryptographic keys against corporate pull request approvals, establishing identical machine identities for supposedly segregated projects.
- Dependency tree extraction discovers proprietary utility libraries embedded inside private branches, demonstrating direct transfer of corporate trade secrets.
Auditors request local machine backups, staging servers, and remote personal forks to locate where code existed before a squashed commit occurred. If a founder cannot supply an authentic, incremental Git history demonstrating development outside corporate hours, corporate counsel will argue that the initial architecture occurred during employment. A clean version history establishes clear separation between corporate employment records and outside software creation.

Release
Separation agreements offer an opportunity to extinguish lurking title disputes. When an engineer resigns, human resources presents a standard severance agreement or termination certification. These forms confirm that the employee returned all corporate property, wiped corporate data from personal devices, and disclosed all inventions produced during employment.
Technical professionals frequently sign these documents without securing reciprocal releases. A standard employee release operates unidirectionally: the employee waives all claims against the company, while the company preserves its rights to enforce intellectual property assignments and restrictive covenants.

Severance Language and Clean Handover Terms
Standard departure documents contain broad general waivers designed to protect departing personnel from historical claims, but these waivers do not release claims of ownership over inventions created during employment. If an engineer leaves with proprietary architecture, signing a standard termination certification confirms that the individual holds no company property. If the company later discovers the code in a venture-backed startup, that certification becomes proof of misrepresentation.
To eliminate repository risk, the departing founder must negotiate a specific, affirmative intellectual property assignment release. This document must explicitly name the repository, identify the project by its unique Git commit hash or external identifier, and confirm that the corporation asserts no claim of ownership or trade secret protection over that specific codebase. Executive officers must sign the instrument, as mid-level engineering managers lack legal authority to waive corporate intellectual property rights.

Residual Exposure in Follow On Diligence
Venture investors and acquiring corporations conduct forensic repository examinations before finalizing equity investments. When auditors discover that a company’s foundational codebase traces back to an era when a founder worked as a salaried engineer elsewhere, the investment halts until title clears. The cost comes not in legal fees alone, but in delayed market entry, renegotiated term sheets, and higher escrow allocations.
Founders who neglect to audit their own repositories discover their exposure during Series A or Series B transactions, when diligence is thorough and counterparty leverage is minimal. At that stage, resolving an old employer’s claim requires issuing equity or paying substantial cash settlements. Legal opinion remains divided on whether an unpushed local commit created on personal hardware during an unpaid weekend becomes company property the moment its author reads employer documentation to solve an architecture problem.