Added 2026/06/2026-06-30-future-tech-holdings.md

2026/06/2026-06-30-future-tech-holdings.md

@@ -0,0 +1,79 @@
+1. Acknowledgment
+I have read and understand GitHub’s Guide to Filing a DMCA Notice.
+
+2. Prior Takedown and Repeat Infringement
+This notice concerns a repeat infringement by the same GitHub user who was the subject of a prior DMCA takedown that GitHub honored. The prior takedown targeted the repository [private], which contained the complete proprietary source code for a Rust-based CAN bus toolkit developed under contract for a U.S. defense contractor. GitHub removed that repository pursuant to our DMCA notice.
+
+The infringing user created this new repository on June 3, 2026—two days before GitHub honored the takedown of [private] on [private]. The user anticipated the takedown and preemptively established a replacement repository to circumvent it. This is willful, premeditated circumvention of the DMCA process and constitutes repeat infringement under GitHub’s Terms of Service and the Digital Millennium Copyright Act, 17 U.S.C. § 512(i).
+
+We request that GitHub terminate the account “suykerbuyk” pursuant to its repeat infringer policy, in addition to removing the infringing repository identified below.
+
+3. Identification of Copyrighted Work
+The copyrighted work is the same work identified in our prior DMCA takedown notice regarding [private]: proprietary software developed for MettleOps, LLC (“MettleOps”) by Future Tech Holdings, LLC (“FTH”) under a services agreement. The work was produced by a contractor engaged by FTH. Under the contractor agreement, all work product is owned by FTH. Under the services agreement between FTH and MettleOps, all work product becomes the property of MettleOps. The copyrighted work is owned by the United States Army under a government contract administered through MettleOps.
+
+The copyrighted work consists of the complete source code, architecture, functional specifications, interface designs, and engineering documentation for a comprehensive Rust-based CAN bus toolkit with J1939 device simulation, DBC-to-Rust code generation, CAN monitoring and analysis tools, WebSocket control protocols, and associated build and CI/CD infrastructure. This work is proprietary, was never authorized for public distribution, and constitutes trade secrets of MettleOps and the U.S. government.
+
+4. Identification of Infringing Material
+The infringing material is located at:
+
+https://github.com/suykerbuyk/rusty-can
+
+The entire repository constitutes infringing material. The infringing user has repackaged the same copyrighted work under a new repository name (“rusty-can” instead of “[private]”), renamed internal components (e.g., “rcan-core,” “rcan-can” instead of the original “cando-” prefixed names), and added a “clean-room specification” wrapper in an attempt to disguise the infringement. The repository’s own README.md explicitly references both “cando-rs” and “proteus-rs”—the very codebases subject to the prior takedown—confirming that this repository is a derivative of the copyrighted work.
+
+The infringing user’s claim of a “clean-room” process is pretextual for the following reasons:
+
+a) The infringing user is the same individual who authored the original copyrighted code under contract. He is both the “spec author” and the “implementer” in his own described process, rendering the claimed firewall meaningless.
+
+b) The specification documents in the “spec/” directory contain proprietary architecture, interface designs, functional requirements, component decomposition, protocol specifications, and engineering decisions that were developed as part of the copyrighted work under contract. These are not publicly available specifications—they are derived directly from trade-secret work product owned by the copyright holder.
+
+c) The implementation in the “impl/” directory mirrors the copyrighted work’s architecture, component structure, and functionality, with superficial renaming (e.g., “cando-” to “rcan-” prefixes).
+
+d) A legitimate clean-room process requires institutional separation between the teams with access to the original work and the teams writing new code. A single terminated contractor performing both roles for code he produced under a work-for-hire agreement does not constitute a clean-room process—it constitutes infringement with a legal narrative constructed after the fact.
+
+As with the prior repository, the infringing user has fraudulently applied Apache License 2.0 and MIT License files. He has no right, title, or interest in this work and is not authorized to license it under any terms.
+
+At the time of this notice, the repository has zero (0) forks.
+
+5. Requested Remedy
+We request the following:
+
+a) Immediate removal of the repository https://github.com/suykerbuyk/rusty-can in its entirety.
+
+b) Termination of the GitHub account “suykerbuyk” pursuant to GitHub’s repeat infringer policy under 17 U.S.C. § 512(i). This user has now twice published the same copyrighted material after being notified that it is infringing, creating a replacement repository before the prior takedown was even honored and continuing to publish the infringing material after notification. This is the definition of repeat infringement.
+
+c) Preservation of all records associated with the “suykerbuyk” account, including commit history, access logs, IP addresses, and account activity. This matter has been escalated to the Federal Bureau of Investigation due to the unauthorized disclosure of U.S. government-owned intellectual property developed under a defense contract. GitHub may receive a preservation request or legal process related to this account.
+
+6. Complainant Contact Information  
+[private]
+
+[private], Future Tech Holdings, LLC
+
+Authorized Agent for MettleOps, LLC
+
+[private]
+
+[private]
+
+Email: [private]
+
+Phone: [private]
+
+7. Alleged Infringer Contact Information
+GitHub Username: suykerbuyk
+
+Prior infringing repository (taken down): [private]
+
+Current infringing repository: https://github.com/suykerbuyk/rusty-can
+
+The alleged infringer is a former contractor of FTH who was terminated for cause. Additional contact information for this individual is available upon request.
+
+8. Good Faith Statement
+I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration. The infringing user’s claim of a “clean-room” process does not constitute fair use—the specifications and implementation are derived from proprietary, trade-secret work product that the user produced under a work-for-hire contractor agreement, and the user has no independent right to the underlying intellectual property regardless of how the material is repackaged.
+
+9. Accuracy and Authority Statement
+I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.
+
+10. Signature
+/s/ [private]
+
+Date: [private]