|
| 1 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf?** |
| 2 | +Yes. I am the [private] and copyright holder of the source code, acting on [private] behalf (not on behalf of a company). This is why [private] am filing from [private] personal address. |
| 3 | + |
| 4 | +**Does your claim involve content on GitHub or npm.js?** |
| 5 | +GitHub. |
| 6 | + |
| 7 | +**Please describe the nature of your copyright ownership.** |
| 8 | +I am the [private] and copyright owner of the source code in the repositories listed. [private] |
| 9 | +created and maintain the originals under [private] personal GitHub account, `[private]`. |
| 10 | + |
| 11 | +**Detailed description of the original copyrighted work allegedly infringed.** |
| 12 | +Proprietary, all-rights-reserved application source code that [private] wrote (data-connection, |
| 13 | +discovery, NLQ, agent, and pipeline systems). The repositories were public only briefly and |
| 14 | +inadvertently, and are now private. The listed `ooollc` repositories are complete, |
| 15 | +unauthorized copies of [private] repositories, including full commit history. |
| 16 | + |
| 17 | +**Original repositories (proof of ownership) — these are MINE, not infringing:** |
| 18 | +[private] |
| 19 | + |
| 20 | +(If any original is not reachable because it is now private, [private] can grant your team |
| 21 | +temporary access to verify authorship on request.) |
| 22 | + |
| 23 | +**Infringing repositories (please disable/remove) — the ENTIRE contents of each infringe:** |
| 24 | +- https://github.com/ooollc/fork.AODv3 |
| 25 | +- https://github.com/ooollc/fork.AOS-DCLv2 |
| 26 | +- https://github.com/ooollc/fork.AOS-NLQ |
| 27 | +- https://github.com/ooollc/fork.AOS-NLQ-Visual |
| 28 | +- https://github.com/ooollc/fork.AOS-pipeline |
| 29 | +- https://github.com/ooollc/fork.AOSFinOpsAgent |
| 30 | +- https://github.com/ooollc/fork.AOSRevOpsAgent |
| 31 | +- https://github.com/ooollc/fork.AOS_AAM |
| 32 | +- https://github.com/ooollc/fork.aos-cc-mcp |
| 33 | +- https://github.com/ooollc/fork.aos-video |
| 34 | +- https://github.com/ooollc/fork.aos.AOSRevOpsAgent |
| 35 | +- https://github.com/ooollc/fork.aos.AgenticDataConnect |
| 36 | +- https://github.com/ooollc/fork.aos.Farmv2 |
| 37 | +- https://github.com/ooollc/fork.aos.agentic-bolt |
| 38 | +- https://github.com/ooollc/fork.aos.autonomos-platform |
| 39 | +- https://github.com/ooollc/fork.aos.autonomos.tech |
| 40 | +- https://github.com/ooollc/fork.aos.console |
| 41 | +- https://github.com/ooollc/fork.aos.convergence |
| 42 | +- https://github.com/ooollc/fork.aos.dcl-onboarding-agent |
| 43 | +- https://github.com/ooollc/fork.aos.k-graph |
| 44 | + |
| 45 | +**Is the entire repository infringing, or specific files?** |
| 46 | +The entire contents of each listed `ooollc` repository infringe — they are wholesale copies |
| 47 | +of [private] repositories, not partial reuse. |
| 48 | + |
| 49 | +**Identify the full repository URL that is infringing.** |
| 50 | +All twenty `ooollc/*` URLs listed directly above. (Correcting [private] earlier entry: the |
| 51 | +infringing repositories are the `ooollc` copies — not [private] `[private]` originals.) |
| 52 | + |
| 53 | +**Regarding forks and GitHub ToS Section D5.** |
| 54 | +These are not legitimate forks arising from normal use of an openly licensed public |
| 55 | +repository. [private] repositories carried **no open-source license** — all rights reserved — and |
| 56 | +were public only briefly and inadvertently before [private] made them private. Section D5 permits |
| 57 | +forking of public repositories through GitHub's fork function; it does not grant any license |
| 58 | +to copy, retain, and redistribute all-rights-reserved source code, and it does not authorize |
| 59 | +these copies to persist after the originals were made private. No license, open-source or |
| 60 | +otherwise, was ever granted permitting the copying or continued distribution of this code. |
| 61 | +Each infringing repository is identified separately above. |
| 62 | + |
| 63 | +**Do you claim technological measures controlling access to your content?** |
| 64 | +No. |
| 65 | + |
| 66 | +**Is the work licensed under an open source license?** |
| 67 | +No. All rights reserved. |
| 68 | + |
| 69 | +**Best solution for the alleged infringement.** |
| 70 | +The reported content must be removed (repositories disabled). |
| 71 | + |
| 72 | +**Alleged infringer's contact information.** |
| 73 | +I do not have direct contact information for the account holder. The infringing account is |
| 74 | +`ooollc` (https://github.com/ooollc); any contact details are held by GitHub. |
| 75 | + |
| 76 | +**Good-faith belief.** |
| 77 | +I have a good-faith belief that use of the copyrighted material described above is not |
| 78 | +authorized by the copyright owner, its agent, or the law. |
| 79 | + |
| 80 | +**Fair use.** |
| 81 | +I have considered fair use. These are complete, verbatim copies of proprietary source code, |
| 82 | +serving as substitutes for the originals; this is not fair use. |
| 83 | + |
| 84 | +**Perjury statement.** |
| 85 | +I swear, under penalty of perjury, that the information in this notification is accurate and |
| 86 | +that I am the copyright owner of an exclusive right that is allegedly infringed. |
| 87 | + |
| 88 | +**I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.** |
| 89 | + |
| 90 | +**Contact.** |
| 91 | +Phone: [private] |
| 92 | + |
| 93 | +**Signature.** |
| 94 | +[private] |
0 commit comments