[00:00:00] Speaker 03: Case number 22-1757, Aprio, Inc. [00:00:04] Speaker 03: versus Neil Zachary at balance. [00:00:06] Speaker 03: Mr. Keenan for the appellant, Mr. Hutchins for the appellee. [00:00:12] Speaker 03: Good morning, Mr. Keenan. [00:00:14] Speaker 03: We'll hear from you. [00:00:15] Speaker 03: Thank you, your honor. [00:00:19] Speaker 03: Good morning and may it please the court. [00:00:22] Speaker 01: Gregory Keenan appearing on behalf on Neil Zachary. [00:00:27] Speaker 01: There are two rights granting contract provisions that issue in this appeal. [00:00:31] Speaker 01: First, there's Section 2.2's licensing provision. [00:00:35] Speaker 01: But importantly, Section 2.2's non-exclusive license cannot help APRIO's claim for a transfer of copyright ownership. [00:00:43] Speaker 01: That's because a non-exclusive license cannot transfer copyright ownership by the plain text of the Copyright Act. [00:00:51] Speaker 01: As such, nothing in Section 2.2 can establish a transfer of copyright ownership here. [00:00:56] Speaker 01: Second, their section 2.3 is assignment provision. [00:01:01] Speaker 01: But critically, section 2.3 is assignment provision only applies to copyright material made, quote, during the period of my service. [00:01:11] Speaker 01: In other words, during the period of Mr. Zachary's employment. [00:01:16] Speaker 01: As such, section 2.3 does not transfer any copyright in any software that Mr. Zachary created before his employment, such as the underlying code that was created in 2008, roughly seven years before his employment began. [00:01:31] Speaker 02: But in his copyright application, he said that the invention, so to speak, was created in 2016, which was during his employment, right? [00:01:44] Speaker 02: That's what he said, right? [00:01:46] Speaker 01: He registered it in 2016 and didn't identify it as a derivative work. [00:01:51] Speaker 01: That's right. [00:01:54] Speaker 02: But importantly, copyright registration doesn't set the parameters for copyright protection under the... Doesn't the application ask when the work was created? [00:02:12] Speaker 01: I believe it asked when he registered it and it asked if it was based on prior content, which he didn't flag it as a derivative work. [00:02:23] Speaker 02: That's true. [00:02:24] Speaker 02: So if he did not flag it as a derivative work, then how is it? [00:02:36] Speaker 02: And I believe that there were requests for admissions. [00:02:40] Speaker 02: which are binding, that's the whole purpose of them, right? [00:02:43] Speaker 02: Yes, your honor. [00:02:45] Speaker 02: So that we can narrow the issues for discovery in the civil case. [00:02:51] Speaker 02: So the request for admissions responses identified to work is being created in 2016, right? [00:03:01] Speaker 01: It requested an admission that wasn't a derivative work. [00:03:06] Speaker 01: So, can I quickly answer just regarding the registration and then directly address that? [00:03:11] Speaker 01: Sure. [00:03:12] Speaker 01: Okay. [00:03:12] Speaker 01: So, importantly, the Copyright Act itself clarifies in Section 408C1 that the administrative classification of the work has, quote, no significance with respect to the subject matter of the copyright or any of the exclusive rights protected by the title. [00:03:27] Speaker 01: And that's because copyright, even though we register them very often, as the Supreme Court has made clear in the Fourth Estate decision, copyright protection, it is granted immediately upon creation, whether or not you ever go and register anything. [00:03:42] Speaker 02: I understand that. [00:03:44] Speaker 02: But I thought that the application nonetheless asked the question of when the work was created. [00:03:54] Speaker 02: Am I wrong about that? [00:03:56] Speaker 01: Be honest, I don't know off the top of my head if it asked when it was created as opposed to if it was based off prior things, but even if it were. [00:04:05] Speaker 01: And 411B2 makes clear that certificate of registration satisfies requirements of this session regardless of whether the certificate contains any inaccurate information. [00:04:16] Speaker 01: So determining the scope of protection based off of information in the registration, [00:04:22] Speaker 01: I think a natural instinct, just as a matter of statute, probably isn't the proper way to determine the scope of protection. [00:04:28] Speaker 01: And that's, again, in part because if Mr. Zachary created the work in 2008, which he did create the base code, there's record evidence that he created a base code in 2008. [00:04:40] Speaker 01: The moment he does that, he receives protection into it, whether or not he registers anything with the copyright office at all. [00:04:46] Speaker 01: As to the admission itself, the admission was whether or not [00:04:52] Speaker 01: that edited code was a derivative work. [00:04:55] Speaker 01: There's two answers to that. [00:04:56] Speaker 01: Our first answer would be that derivative work is a defined term under the Copyright Act. [00:05:02] Speaker 01: So that's a purely legal conclusion, we would argue. [00:05:04] Speaker 01: Because the admission said, admit that the software is not a derivative work. [00:05:10] Speaker 01: The statute lays out that derivative work is a work based off of pre-existing material. [00:05:17] Speaker 01: And the statute also makes clear that any copyright and derivative work [00:05:21] Speaker 01: wouldn't extend to the underlying pre-existing material. [00:05:26] Speaker 01: In the alternative, even if we completely accepted the fact, let's say we were bound with this admission despite the fact that we think it's a legal admission as opposed to a factual admission or a factual admission leading to a legal admission, that still wouldn't change the fact that by operation of the Copyright Act, [00:05:47] Speaker 01: The provisions of Section 2.2 and 2.3 still wouldn't give access to, wouldn't give protection to that underlying material because the only provision that would be affected by this being a derivative work would be Section 103, which says that a derivative work protection doesn't extend to the underlying material, but there's also other provisions in the Copyright Act that don't require a work being a derivative work that clarify that you're not going to get the underlying. [00:06:17] Speaker 01: So Section 102A's originality requirement, for example, it's table stakes and copyright that you only get protection for what's called an original work or original components of a work. [00:06:31] Speaker 01: An original means not copied. [00:06:33] Speaker 01: So we know that he created work in 2008. [00:06:36] Speaker 01: We know that there was copying from that work into the new work. [00:06:39] Speaker 01: Even if we were stuck with the admission that it's not a derivative work, that doesn't change the fact that anything that's transferred in that edited code, it just can't give exclusive copyright to the elements that are copied and not original. [00:06:54] Speaker 01: And that's a matter not just of statute, as the Supreme Court clarified in Feist. [00:06:58] Speaker 01: That's a constitutional mandate. [00:07:00] Speaker 01: Copyright Act and the intellectual property clause limit the ability to text writings to original materials. [00:07:08] Speaker 01: And so to the degree there was a transfer and section 2.2 and 2.3 of the contract say, you know, it's not going to transfer anything prior to employment. [00:07:20] Speaker 01: The only portions of the work that are going to transfer over are the new works, not based off of the underlying work. [00:07:26] Speaker 01: And that's not just because of those provisions, but it's also because the copyright in that is not going to grant exclusive copyright ownership in anything that was copied or not original from any other. [00:07:38] Speaker 02: I'm not sure I understand where that gets you because the fight here isn't about whether or not he can, [00:07:47] Speaker 02: use or retain copies of the software as it was written in 2008, right? [00:07:55] Speaker 02: That's right. [00:07:58] Speaker 02: So what difference does it make if indeed he retains the copyright to the version that he wrote at that time? [00:08:08] Speaker 01: I think it goes a step further, Your Honor. [00:08:10] Speaker 01: It's that not just as you retain that copyright, but the transfer of the subsequent copyright would only give an exclusive ownership right in those portions of the work that were original, that weren't created. [00:08:22] Speaker 01: So essentially, the primary error that just respectfully shouldn't be affirmed here is that the district court below said each and every portion of the edited code [00:08:34] Speaker 01: Each and every portion of the edit code was granted to Aprio, and that doesn't make sense. [00:08:41] Speaker 02: I don't see how that argument makes sense in that revised the edited code can't work without what came before it. [00:08:58] Speaker 02: I mean, it all works together. [00:09:00] Speaker 02: you know, revised code builds on the old code. [00:09:04] Speaker 02: So you're trying to say that that Aprio only got a copyright to, you know, half a code, so to speak, the new half. [00:09:17] Speaker 02: But even if it needs the other half to work, it doesn't have a copyright to that half. [00:09:22] Speaker 02: I just don't understand your argument. [00:09:25] Speaker 01: Importantly, not exclusive copyright ownership. [00:09:28] Speaker 01: Remember, section 2.2 of the contract talks about a license, a non-exclusive license. [00:09:33] Speaker 01: So they might have an argument that they could make a licensed use of it. [00:09:36] Speaker 01: That's not what they asked for. [00:09:38] Speaker 01: They asked for a termination that they were the exclusive owner of each and every bit of the new code, including the portions of the code that they had copied. [00:09:46] Speaker 01: previous existing code from that base code. [00:09:49] Speaker 01: That's a very different thing. [00:09:50] Speaker 01: And actually, if I could just quote the provisions of the district court's opinion, where it's relying on an exclusive license code, [00:09:58] Speaker 01: in order to grant or a non-exclusive license in order to grant exclusive ownership. [00:10:03] Speaker 01: The court said, here it is enough to note that having created the base code in 2008 makes no difference for the purposes of APRO rights under paragraph 2.2. [00:10:10] Speaker 01: That may well be true, but 2.2 is not, it's a non-exclusive license is what it grants by its plain terms. [00:10:18] Speaker 02: What do we do with the fact that the company asked him whether or not there was [00:10:28] Speaker 02: This was a derivative work. [00:10:30] Speaker 02: There wasn't any works that he was claiming copyright ownership of and he did not identify it as such. [00:10:40] Speaker 01: Yes, Your Honor. [00:10:40] Speaker 01: I think you're referring to 2.2's requirement to disclose prior inventions and he didn't fill that out. [00:10:46] Speaker 02: I mean, how is the railroad supposed to run, so to speak, if given that opportunity to identify [00:10:58] Speaker 02: any prior reading works that you're saying that I intend to to retain the copyright of this and it's not. [00:11:07] Speaker 02: I'm not using it as part of my work for you at. [00:11:12] Speaker 02: This before I work for you and I have a copyrighted this that I want to retain. [00:11:18] Speaker 02: You're given the opportunity to identify that you don't. [00:11:24] Speaker 01: Yes, your honor, it seems. [00:11:27] Speaker 01: that seems that's the whole point. [00:11:29] Speaker 01: Well, it certainly might have implications for 2.2. [00:11:32] Speaker 01: But importantly, the language of 2.2 is pretty clear. [00:11:35] Speaker 01: The first sentence says inventions, which I made prior to the commencement of my service are excluded from the scope of this agreement. [00:11:45] Speaker 01: Later, it defines a term which is required for a prior invention disclosure. [00:11:49] Speaker 01: But notably, there are multiple requirements to qualify as that. [00:11:52] Speaker 01: So we would argue that doesn't qualify as a defined term within 2.2 of a prior invention. [00:11:57] Speaker 01: because it's not just an invention that was made beforehand. [00:12:00] Speaker 01: It's required that it's one that will be used in your service with the company. [00:12:07] Speaker 01: Mr. Zangary wasn't a software developer here. [00:12:11] Speaker 01: So this wasn't something that was within the service. [00:12:14] Speaker 02: So the district court found that this was used, the district court made a finding that this was used. [00:12:23] Speaker 02: Are you saying that that finding was clearly erroneous or that somehow we're supposed to overturn that finding? [00:12:31] Speaker 01: The legal error is that even if he failed, even if that were an okay finding and even if he failed to disclose on this prior invention form, it just doesn't change the fact that when you read the contract, [00:12:44] Speaker 01: 2.2 is bringing a non-exclusive license. [00:12:47] Speaker 01: So even if the failure to disclose has an implication for 2.2, at best, it's going to get you a non-exclusive license. [00:12:53] Speaker 01: It's not going to get you an exclusive ownership, which is what they saw in their receipt below. [00:12:59] Speaker 03: Any questions? [00:13:04] Speaker 03: All right. [00:13:04] Speaker 03: Thank you. [00:13:05] Speaker 03: We'll give you some time on rebuttal. [00:13:06] Speaker 03: Thank you very much, Your Honors. [00:13:15] Speaker 03: Good morning, Your Honors, John Hutchins for APRIO. [00:13:20] Speaker 00: So the CRR software was created in 2016 and that was admitted both in requests for admit and in the answer. [00:13:34] Speaker 00: Paragraph 40 of the answer affirmatively states by Mr. Zachary, [00:13:40] Speaker 00: that the CRR software was created, quote, during the time period, he was also an employee of Apprio. [00:13:48] Speaker 00: Full stop. [00:13:51] Speaker 00: Since the CRR software was created in 2016, admittedly, and of course, your honor is correct, copyright applications and copyrights themselves provide date. [00:14:02] Speaker 00: Here the date was 2016, also provided by Mr. Zachary. [00:14:07] Speaker 00: The copyrights at 692 and the applications at 950. [00:14:14] Speaker 00: Having been created in 2016, admittedly during the time of his employment, it was an assigned invention under section 2.3. [00:14:22] Speaker 00: 2.3 assigns any inventions created or reduced to practice during the period of employment whether [00:14:35] Speaker 00: Registrable or not? [00:14:40] Speaker 00: So I think the notion of which portions are registrable for copyright is a bit of a red herring. [00:14:47] Speaker 00: What's important, it was created in 2016, and admittedly so. [00:14:53] Speaker 00: Yet another reason it can't be a prior invention, subject to any exception of Section 2.2, is that no prior inventions disclosure form is filled out. [00:15:02] Speaker 00: Also, admittedly so. [00:15:06] Speaker 00: while I'm discussing admissions in general, whether a work is derivative or not, it's absolutely not pure question of law. [00:15:16] Speaker 00: In fact, it's a question of fact. [00:15:19] Speaker 00: And I'll cite to you folio impressions versus Bayer, 937F2nd, 759, and Atkins versus Fisher, 331F3rd, 988. [00:15:29] Speaker 00: It's a perfectly appropriate admission. [00:15:36] Speaker 00: that we're entitled to rely upon. [00:15:39] Speaker 00: So for all of those reasons, section 2.3 assigned the rights, and that's all the district court appropriately held. [00:15:52] Speaker 00: He also noted, as I just explained, section 2.2 could not apply, both because it wasn't a prior invention, because it was created in 2016, admittedly, [00:16:01] Speaker 00: and because it wasn't disclosed as it would have had to have been. [00:16:05] Speaker 00: And as to the issue of whether it was used in connection with his work, district court's opinion and the admitted facts he relies upon speaks for itself. [00:16:18] Speaker 00: Mr. Zakari, by his own telling, was working on a project for Aprio for the government to render their contract review more efficient. [00:16:29] Speaker 00: He created this software, he says, because he knew it would be useful. [00:16:34] Speaker 00: He brought it in to show to Apprio and Apprio's customer. [00:16:38] Speaker 00: He admitted the only reason he had access to Apprio and Apprio's customer and was able to do that was because of his employment. [00:16:45] Speaker 00: And then he states that Apprio told him to provide it to the government as a condition of his employment. [00:16:54] Speaker 00: And he did so and kept his job for the remaining 10 months until the contract ended. [00:17:03] Speaker 00: That describes use in connection with your employment. [00:17:09] Speaker 00: By definition, I would submit. [00:17:11] Speaker 04: Can I ask about the contract formation issue? [00:17:13] Speaker 04: And certainly you're on very strong ground there, but I just want to kind of play it out a little bit. [00:17:20] Speaker 04: Let's imagine that instead of making the admissions that you're suggesting Mr. Zachary made, that he had said deny, deny, deny. [00:17:27] Speaker 04: You could acknowledge those files without agreeing with them, correct? [00:17:32] Speaker 04: To say the last part of the question again, sir. [00:17:34] Speaker 04: You could acknowledge his denials without agreeing with his denials, correct? [00:17:41] Speaker 04: Yes. [00:17:42] Speaker 04: There's a difference between acknowledging and agreeing. [00:17:46] Speaker 04: There, theoretically there could be. [00:17:49] Speaker 04: Like if I said to my friend, hi Jackson, the weather's nice and he acknowledged my greeting, doesn't mean he's agreeing with me that the weather's nice, correct? [00:17:59] Speaker 04: Theoretically, that's absolutely the case. [00:18:01] Speaker 04: What's different here? [00:18:03] Speaker 04: What about the context here makes a difference? [00:18:05] Speaker 00: Because the context here is that under DC law, contract formation requires no specific magic word of I agree versus I assent versus I accept. [00:18:16] Speaker 00: Accept, which was admittedly used in the Forest case. [00:18:20] Speaker 00: That was the fact scenario in the Forest case where the court held contract formation. [00:18:26] Speaker 00: I assent can mean I agree to the contract. [00:18:29] Speaker 00: It could mean I assent that I received the contract. [00:18:34] Speaker 00: The Metropolitan case, which held that copyright assignments can be electronically assigned. [00:18:40] Speaker 00: The court discussed yes. [00:18:43] Speaker 00: There is no difference in kind between agree, accept, assent, acknowledge, yes. [00:18:50] Speaker 00: And DC law is crystal clear that what matters is the objective manifestation. [00:18:56] Speaker 00: What Aprio requested happened in this case to say acknowledge. [00:19:02] Speaker 00: And he acknowledged it. [00:19:04] Speaker 04: Was there some benefit to using the word acknowledge there as opposed to agree or were they just the same and either one would have worked? [00:19:12] Speaker 00: Either would have worked just as well. [00:19:13] Speaker 00: I mean, so when this issue came up, I actually cracked open my Black's Law Dictionary, which had been about 30 years. [00:19:21] Speaker 00: When I went to law school, it was given to me as a gift, as many law students get that as a gift, and acknowledge means to accept responsibility for. [00:19:32] Speaker 00: in general. [00:19:34] Speaker 00: So I think that there's nothing wrong with acknowledge. [00:19:38] Speaker 00: I'll also note that the term acknowledge also has been used for contract formation in exactly this scenario where an agreement is pulled up, you see the agreement, and you click acknowledge. [00:19:51] Speaker 00: That's the Fox versus computer world case, which was cited to the district court in this matter, 920 F sub second 90. [00:19:59] Speaker 00: And there an employee was being onboarded and he pulled up all the various onboarding agreements for his employment, one of which was an arbitration agreement. [00:20:11] Speaker 00: And he acknowledged it. [00:20:14] Speaker 00: And the DDC had no problem holding that acknowledging their manifested contract formation. [00:20:24] Speaker 00: But even if one were to quibble about that, and I don't think the law of DC and contract formation requires you to say, I agree, I agree to the agreement, versus I acknowledge I agree to the agreement, or I assent or yes. [00:20:38] Speaker 00: He has other objective manifestations, such as the 10 months he continued to accept consideration. [00:20:43] Speaker 00: And under DC contract law, DC allows for contract formation when a party accepts the consideration. [00:20:53] Speaker 00: What's the consideration for the assignment? [00:20:59] Speaker 00: 10 twelfths of the $150,000 he was paid for the ensuing 10 months. [00:21:04] Speaker 02: But he doesn't get any separate consideration or any sort of a license. [00:21:11] Speaker 02: That's a sign. [00:21:12] Speaker 02: No, that's correct. [00:21:14] Speaker 02: So he gives up all rights and earns no royalties whatsoever on [00:21:22] Speaker 00: his creation? [00:21:24] Speaker 00: Just his salary, which I say just. [00:21:26] Speaker 00: I mean, he was, his team of salary did $150,000 a year as a senior technical manager. [00:21:32] Speaker 00: And so, and that's the case whenever, I mean, that's no different than whenever these company agreements go into effect. [00:21:43] Speaker 00: And the consideration, by the way, is set out literally in the opening sentence. [00:21:49] Speaker 00: The title of the agreement is bold and cap saying it's an inventions assignment agreement. [00:21:54] Speaker 00: Immediately under that, it explains that consideration is his being retained as an employee and receiving. [00:22:00] Speaker 00: So I remember right that he tried to use this agreement against you. [00:22:04] Speaker 00: Well, that's the third manifestation. [00:22:07] Speaker 00: of assent objectively is that he hired a lawyer and brought suit to enforce the agreement in federal court. [00:22:16] Speaker 00: And that's a pretty strong objective manifestation that he intended to be bound, bringing a federal lawsuit to enforce a contract. [00:22:27] Speaker 00: And I'll go so far as to say that I'm certainly unaware of any case. [00:22:31] Speaker 00: I'm aware of a ton of cases that hold that the clicking the acknowledgement would have been enough. [00:22:35] Speaker 00: I'm aware of a bunch of cases saying that remaining employed for the 10 months and accepting the benefit would have been enough. [00:22:42] Speaker 00: And I'm unaware of no case in which someone attempted to enforce a contract and then was able to claim a secret subjective intention to not be bound that was later recovered in memory [00:22:56] Speaker 00: trumped, because if that were true, no contract known to man would ever be safe. [00:23:04] Speaker 00: And of course, that's not what DC law is extremely clear that it goes full bore into the objective theory of contract law. [00:23:13] Speaker 00: Unless your honors have any other question, I appreciate your time and I'll conclude. [00:23:18] Speaker 00: Thank you. [00:23:19] Speaker 00: All right, thank you. [00:23:22] Speaker 03: All right, we'll give you two minutes for rebuttal, Mr. Keenan. [00:23:28] Speaker 03: Thank you very much, Your Honors. [00:23:32] Speaker 01: To say quickly, to affirm beyond the interpretation whether or not a copyright was even transferred or what scope of copyright was transferred into this, we'd still have to affirm on both formation and Section 204 signature requirement. [00:23:51] Speaker 01: So just quickly, Section 204 requires any time a copyright is transferred, there's a signed requirement. [00:23:56] Speaker 01: While the E-Sign Act doesn't put electronic signatures on different footing, I don't think if we use paper and pen to just check something that said acknowledge, that would satisfy the ordinary meaning of signature. [00:24:07] Speaker 01: So it's not clear that regardless of the formation question, it satisfies Section 204's signature requirement of copyright act for transfer. [00:24:16] Speaker 01: Beyond that, I just want to reiterate that the Supreme Court advice said that a [00:24:21] Speaker 01: There was an important limitation on the protection of a copyright. [00:24:24] Speaker 01: The mere fact that a work is copyright doesn't mean that every element of that work is copyrighted. [00:24:28] Speaker 01: What's required is originality. [00:24:30] Speaker 01: Originality means not copied from something else. [00:24:34] Speaker 01: Beyond that, regardless of whether or not it's a derivative work, there's multiple provisions of the Copyright Act that are violated by essentially saying that this, [00:24:45] Speaker 01: This transfer under 2.3 transferred each and every component, including the copied components of the prior code. [00:24:53] Speaker 01: Section 102A is originality requirements. [00:24:56] Speaker 01: Section 103B, which makes clear that pre-existing materials that are copied don't extend to the derivative work. [00:25:03] Speaker 01: That's the only one that's affected by being a derivative, not section. [00:25:07] Speaker 01: 102A is originality 201B. [00:25:10] Speaker 01: 201D2 is divisibility. [00:25:15] Speaker 01: And finally, I think it's important that when he was fired, ultimately, ironically, he received a termination letter that asked him to, and it's at 3JA608, to acknowledge, it's an acknowledgement signature. [00:25:30] Speaker 01: So one thing that's important on the formation question is that the record shows that this company had made employees sign not just contracts, but also policies [00:25:45] Speaker 01: where they would acknowledge things. [00:25:46] Speaker 01: And even when he was fired, it required an acknowledgement signature, which I don't think was forming a contract. [00:25:51] Speaker 01: So I think there is a distinction between acknowledge and free. [00:25:56] Speaker 01: Thank you very much, Your Honor. [00:25:57] Speaker 01: Thank you. [00:25:58] Speaker 03: We'll take the case under advisement.