Added 2026/08/2026-08-18-byd.md

2026/08/2026-08-18-byd.md

@@ -0,0 +1,97 @@
+**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.**  
+
+Yes, I am authorized to act on the copyright owner's behalf.  
+
+**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?**  
+
+Yes  
+
+**Please provide the Zendesk ticket number of your previously submitted notice. Zendesk ticket numbers are 7 digit ID numbers located in the subject line or body of your confirmation email.**  
+
+4615118  
+
+**Does your claim involve content on GitHub or npm.js?**  
+
+GitHub  
+
+**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.**  
+
+**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.**  
+
+Dear GitHub [private],  
+Thank you for your prompt response. However, we respectfully disagree with the classification of this matter as a Private Information Removal request. This is a DMCA copyright infringement claim, and we ask that you reconsider.  
+While the repository does incidentally contain a few hardcoded passwords in its seed data, that is not what this claim is about. Our complaint concerns the unauthorized reproduction and distribution of an entire copyrighted software system — 95 Java source files, 17 SQL files, 4 technical documentation files, and 2 Python scripts.  
+Below we provide specific evidence distinguishing this from a private information case and establishing clear copyright infringement.  
+Why This Is Not a Private Information Removal Case  
+A Private Information Removal request covers leaked credentials, access tokens, personal identifiers, and network diagrams. We are not asking you to redact a password from a config file. We are asking you to remove an entire copyrighted software work from GitHub.  
+The distinction is straightforward: if someone published a stolen novel on GitHub, it would remain a copyright matter even if the author's phone number appeared in the manuscript's metadata.  
+Evidence of Copyright Infringement  
+1. Original software source code (95 Java files)  
+The repository reproduces a complete enterprise application under BYD's proprietary package namespace. Each file below contains original, creative expression in the form of algorithm design, class architecture, and business logic:  
+byd-aftersales/src/main/java/com/byd/aftersales/service/WorkOrderService.java — work order lifecycle management  
+byd-aftersales/src/main/java/com/byd/aftersales/service/WarrantyService.java — warranty assessment logic  
+byd-aftersales/src/main/java/com/byd/aftersales/service/AgentDiagnosisService.java — AI-powered vehicle diagnostics  
+byd-aftersales/src/main/java/com/byd/aftersales/service/BatteryHealthService.java — battery health monitoring  
+byd-aftersales/src/main/java/com/byd/aftersales/service/SettlementService.java — billing and settlement workflows  
+byd-aftersales/src/main/java/com/byd/aftersales/service/WorkOrderCompletionService.java — transactional service combining inventory, settlement, and status transitions  
+byd-aftersales/src/main/java/com/byd/aftersales/controller/*.java — 18 original REST API controllers  
+byd-aftersales/src/main/java/com/byd/aftersales/dao/*.java — 16 original data access implementations  
+byd-aftersales/src/main/java/com/byd/aftersales/domain/*.java — 16 original domain model classes  
+byd-aftersales/src/main/java/com/byd/aftersales/auth/*.java — 4 original authentication/authorization files  
+2. Original database design (17 SQL files)  
+byd-aftersales/src/main/resources/db/schema.sql — original schema with 15+ tables, foreign keys, and constraints  
+byd-aftersales/src/main/resources/db/seed-production.sql (lines 44–580) — original seed data modeling BYD's complete after-sales business: service centers, vehicle records, appointments, fault records, work orders, parts inventory, settlements, and battery health trends  
+3. Original technical documentation (4 files)  
+byd-aftersales/docs/项目进度与开发指南.md (line 1: "BYD New Energy Vehicle After-Sales System — Project Progress & Development Guide") — original project specification with architecture docs, module specs, and API references  
+byd-aftersales/docs/B-module-api.md — original Customer Management API documentation  
+byd-aftersales/docs/C-module-api.md — original Repair Operations API documentation  
+byd-aftersales/docs/D-module-api.md — original AI Diagnostics API documentation  
+4. Project metadata attributing copyright to BYD  
+byd-aftersales/pom.xml, line 17: <groupId>com.byd</groupId>  
+byd-aftersales/pom.xml, line 21: <description>BYD new energy vehicle after-sales service demo system.</description>  
+byd-aftersales/src/main/java/com/byd/aftersales/BydAftersalesApplication.java, line 1: package com.byd.aftersales;  
+The Java package namespace com.byd, the Maven groupId, and the project description all explicitly identify this as BYD's copyrighted software.  
+
+**If the original work referenced above is available online, please provide a URL.**  
+
+**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.**  
+
+**Based on the above, I confirm that:**  
+
+The entire repository is infringing  
+
+**Identify the full repository URL that is infringing:**  
+
+https://github.com/yangynyiyi/byd-car-aftersales  
+
+**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.**  
+
+No  
+
+**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:**  
+
+**Is the work licensed under an open source license?**  
+
+No  
+
+**What would be the best solution for the alleged infringement?**  
+
+Reported content must be removed  
+
+**Do you have the alleged infringer’s contact information? If so, please provide it.**  
+
+**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 <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.**  
+
+**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.**  
+
+**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.**  
+
+**So that we can get back to you, please provide either your telephone number or physical address.**  
+
+[private]  
+
+**Please type your full name for your signature.**  
+
+[private]