IP Ownership in Local-First Sync Engines

The presumptive owner of a patentable invention is the human inventor. Not the company. Not the startup that funded the research. The individual who conceived it. This default surprises teams building local-first sync engines, where novel CRDT algorithms and conflict resolution methods emerge from distributed contributors working across jurisdictions.

Local-first software, as described in the 2019 Kleppmann et al. paper from Ink & Switch, treats the user's device as the primary data store. Offline functionality, peer-to-peer sync, and long-term data preservation are core principles. Developers building these systems routinely create potentially patentable innovations in data structures, merge protocols, and consistency algorithms. Without proper assignment clauses, the company may never own those inventions.

For patent attorneys advising these teams, the combination of open-source culture, cross-border contributors, and abstract algorithm work creates a specific set of IP ownership risks. This page outlines the contractual and procedural mechanisms that help secure clean title.

Last updated: March 2026. This page is informational only and not legal advice. Consult a patent attorney for your specific situation.

2 words

separate owning a patent from losing it: "hereby assign" vs. "agree to assign"

0 days

international patent rights remaining after public open-source commit

patent rights automatically transferred by employment alone (without written assignment)

U.S. states with statutes limiting employer invention assignment clauses

Why Sync Engine Teams Face Unique Ownership Risk

Local-first sync engine development differs from typical enterprise software work in three ways that complicate IP ownership.

Distributed contributors across jurisdictions. A CRDT library might have core contributors in California, Germany, and Singapore. Each jurisdiction has different rules about employee invention assignments. California Labor Code § 2870 prohibits employers from claiming inventions developed entirely on the employee's own time without employer resources. Washington (RCW 49.44.140) and Minnesota (Minn. Stat. § 181.78) have similar statutes. A blanket assignment clause that ignores these carve-outs may be unenforceable to the extent it conflicts with those statutory protections.

Open-source contribution before disclosure. Local-first projects frequently involve open-source components. A developer might contribute a novel merge algorithm to an open-source CRDT library before anyone files an invention disclosure. Once that code is public, international patent rights are lost under absolute novelty standards. In the U.S., you have 12 months under 35 U.S.C. § 102, but the clock is already running.

Abstract innovations with eligibility uncertainty. Conflict resolution algorithms, causal ordering protocols, and vector clock improvements sit in the zone that Alice Corp. v. CLS Bank International (573 U.S. 208, 2014) made uncertain under 35 U.S.C. § 101. This does not eliminate the need for assignment clauses. It means attorneys must evaluate patentability early to prioritize which discoveries warrant formal disclosure and prosecution.

Present Assignment vs. Future Promise: The Stanford v. Roche Lesson

The single most important drafting distinction in IP assignment law comes from Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., 563 U.S. 776 (2011). The Supreme Court held that Stanford's agreement language ("agree to assign") created only a future promise to assign rights, not an immediate transfer. A subsequent agreement with a third party using present-tense language ("I hereby assign") took priority.

The Federal Circuit reinforced this in Preston v. Marathon Oil Co., 684 F.3d 1262 (Fed. Cir. 2012), upholding present assignment language in an employment agreement. The court found that continued at-will employment provided sufficient consideration. It also found that vague prior invention disclosures were insufficient to carve out later-developed IP.

For patent attorneys drafting agreements for sync engine teams, the fix is straightforward. Use present-tense operative language. Never rely on "agrees to assign" or "will assign." The difference between these phrases is the difference between owning the patent and litigating over it.

Under 35 U.S.C. § 261, patent assignments must be in writing. Recording with the USPTO provides constructive notice to subsequent purchasers. For local-first teams that may be acquired or raise funding, recorded assignments eliminate title questions during due diligence.

Language	Effect	Risk
"I hereby assign"	Immediate present transfer of rights at signing	Low assignment is automatic upon conception
"Employee hereby assigns"	Immediate present transfer of rights at signing	Low assignment is automatic upon conception
"Agrees to assign"	Future promise requiring a separate assignment act	High third-party "hereby assign" takes priority
"Will assign"	Future promise requiring a separate assignment act	High third-party "hereby assign" takes priority

Drafting Assignment Clauses for Distributed Teams

A well-drafted assignment clause for a local-first sync engine team should address five elements.

Scope of assigned inventions. Define what is covered: inventions conceived or reduced to practice during employment, using company resources, or related to the company's business. Be specific about the technical domain. "Synchronization protocols, conflict-free replicated data types, operational transformation algorithms, and peer-to-peer data merging methods" is more defensible than "all inventions."

Present-tense assignment language. Use "hereby assigns" rather than "agrees to assign." Stanford v. Roche is clear on this point.

State-law carve-outs. If contributors are in California, Washington, Minnesota, or other states with invention assignment statutes, include a notice that the agreement does not apply to inventions developed entirely on the employee's own time without company resources. California Labor Code § 2870 requires this notice in writing.

Prior invention schedule. Require contributors to list all prior inventions at the time of signing. Preston v. Marathon Oil found that vague prior invention disclosures were insufficient to exclude later work. The schedule should be specific: invention name, date of conception, brief description, and whether a patent application has been filed.

Contractor-specific provisions. Many local-first teams use independent contractors for specialized CRDT or distributed systems work. Contractors do not automatically assign patent rights to the engaging company. Work-for-hire doctrine under 17 U.S.C. § 101 applies to copyrights, not patents. Every contractor agreement should include an explicit patent assignment clause covering inventions developed in the scope of the engagement.

Key action: Audit every contributor agreement in your organization today. If any agreement uses "agree to assign" or "will assign" instead of "hereby assigns," replace it. A single phrase is the difference between clean title and a title defect that surfaces during due diligence.

Invention Disclosure Before Open-Source Release

Local-first teams face a timing problem that most software companies do not. The culture of open-source contribution means novel algorithms can be published to GitHub before anyone considers whether a patentable invention exists.

Once code is publicly available, patent rights are lost in jurisdictions with absolute novelty requirements, including Europe, China, Japan, and Korea. In the U.S., a 12-month grace period exists under 35 U.S.C. § 102. Relying on that grace period is a poor strategy. It provides no protection internationally.

The disclosure timeline: Invention disclosure must happen before any public release, conference presentation, blog post, or commit to a public repository. Build this workflow into the team's development process rather than trying to recover rights after the fact.

The solution is a structured invention disclosure process. Every sync engine team should maintain invention disclosure forms that capture:

The technical problem being solved
The proposed solution
How it differs from known prior art
The date of conception
The date of first reduction to practice
Any planned publications or open-source releases

Some teams use tools that scan local codebases for potentially novel implementations as part of their disclosure process. One example is the ObviouslyNot scanner at app.obviouslynot.ai, which runs locally so no code leaves the developer's machine. Tools of this type can help surface candidates for disclosure review without creating a public disclosure event.

Open Source and Implied License Conflicts

Patenting a sync engine innovation that also exists in an open-source library creates a tension that patent attorneys must address directly.

Apache 2.0 Patent Grant

Apache 2.0 includes an express patent license in Section 3, distinct from its copyright license. Contributing code covered by a pending or issued patent under Apache 2.0 grants a royalty-free patent license to all recipients for that contribution.

Implied Patent Licenses

Permissive licenses without express patent terms may still create implied patent licenses under equitable estoppel principles. Even silence on patent rights does not guarantee that contributing code preserves those rights.

Dual-Licensing Strategy

For teams maintaining both a commercial product and an open-source CRDT library, a dual-licensing model may be appropriate. The patent covers the commercial implementation. The open-source version uses a different approach or operates under the applicable license's patent grant.

Alice Eligibility Framing

Many CRDT and sync algorithms involve mathematical operations on data structures. After Alice, frame discoveries around specific technical improvements: reduced network bandwidth, faster convergence in offline-to-online transitions, or more efficient storage in conflict resolution.

This does not mean you cannot patent sync engine innovations. It means you must coordinate the patent filing with the open-source strategy. File before contributing to the open-source project. Decide which implementations remain proprietary and which are contributed. Document the boundary clearly.

Due Diligence Checklist for Clean Title

When a local-first sync engine company enters a funding round or acquisition, the acquiring party will audit IP ownership. Gaps in assignment chains are among the most common findings that delay or reduce deal value.

Written assignment agreements. Every contributor who touched patentable code must have signed a written assignment agreement using present-tense assignment language.

Recorded USPTO assignments. All issued patents and pending applications must have assignments recorded at the USPTO under 35 U.S.C. § 261 to provide constructive notice to subsequent purchasers.

State-law compliant carve-out notices. Contributors in California, Washington, Minnesota, and similar jurisdictions must have received the required statutory notice and carve-out in their agreements.

Completed prior invention schedules. All contributors must have signed specific prior invention schedules at the time of hire or engagement, not vague catch-all disclosures.

Invention disclosure records with dates. Disclosure dates must precede any public release, open-source commit, conference presentation, or blog post.

Open-source contribution review documentation. Records showing that open-source contributions were reviewed for patent conflicts before publication must exist and be accessible.

Missing any of these creates a title defect. In the worst case, a former contributor who never signed an assignment may retain ownership of a key patent. The company cannot enforce it, license it, or sell it without that person's cooperation. Stanford v. Roche demonstrated that even a major research university can lose patent rights over a single phrase in an assignment clause. A small sync engine team carries the same risk with less margin for error.

Frequently Asked Questions

Does an employment relationship automatically transfer patent rights to the employer?

No. Under U.S. law, the presumptive owner of a patentable invention is the human inventor. The employment relationship alone does not transfer patent rights. You need a written assignment agreement. The Supreme Court confirmed this in Stanford v. Roche, 563 U.S. 776 (2011). Without a written assignment using present-tense language ("hereby assign"), the inventor retains title.

What is the difference between "agree to assign" and "hereby assign"?

Stanford v. Roche drew a clear line. "Agree to assign" is a promise to transfer rights in the future, which requires a separate assignment act to be effective. "Hereby assign" operates as an immediate, present transfer of rights at the moment the agreement is signed. If a contributor signs a "hereby assign" agreement with a third party after signing an "agree to assign" with your company, the third party may own the patent. Always use present-tense assignment language.

Can we require assignment of inventions a developer creates on their own time?

It depends on the state. California Labor Code § 2870 prohibits employers from claiming inventions developed entirely on the employee's own time, without employer equipment, and unrelated to the employer's business. Washington (RCW 49.44.140) and Minnesota (Minn. Stat. § 181.78) have similar statutes. For local-first sync engine teams, this is particularly relevant because developers may work on personal CRDT projects that overlap with their employer's technology. Your assignment clause must include the statutory notice and carve-out for each applicable jurisdiction.

Do independent contractors automatically assign patent rights through work-for-hire?

No. Work-for-hire doctrine under 17 U.S.C. § 101 applies to copyrights, not patents. For patent rights in inventions developed during a contracting engagement, ownership depends on the contract and applicable law. Without an explicit written patent assignment clause in the contractor agreement, the contractor may retain ownership of patentable inventions, regardless of who funded the work. Every contractor agreement for technical work should include a specific patent assignment provision.

How does open-source contribution affect patent ownership?

Contributing code to an open-source project grants downstream users a copyright license under the project's license terms. Depending on the license, it may also affect patent rights. Apache 2.0 includes an express patent license grant in Section 3, separate from its copyright license. Contributing patented code under Apache 2.0 grants a royalty-free patent license to all recipients. Even licenses without express patent terms may create implied patent licenses. File patent applications before contributing code to public repositories, and review open-source license terms for patent implications.

Are CRDT algorithms patentable after Alice?

Possibly, but with significant uncertainty. Alice Corp. v. CLS Bank (573 U.S. 208, 2014) made abstract ideas implemented on generic computers potentially ineligible under 35 U.S.C. § 101. Many sync engine innovations involve mathematical operations on data structures. To improve patentability prospects, frame discoveries around specific technical improvements: reduced bandwidth, faster convergence, or more efficient storage. An attorney experienced in software patents after Alice should evaluate each discovery individually.

Your sync engine may contain inventions you don't know about yet.

Novel CRDT algorithms, conflict resolution methods, and merge protocols are often patentable. The ObviouslyNot scanner runs locally on your machine. No code leaves your device.

Scan your codebase free