Supporting argument 04
Accountability and Scope Control
Even a narrowly justified refusal system creates a broader ethical risk: once printers contain the infrastructure to inspect and block files, governments, manufacturers, or rights holders may attempt to expand it. A database created for illegal firearm parts could later include trademarks, copyrighted characters, replacement parts, or designs that compete with a manufacturer’s products. Each expansion may appear minor, but together they could convert a safety measure into general control over a machine its user owns.
Keep detection rules auditable and revisable
This possibility makes accountability and scope control conditions of ethical deployment. Schur’s discussion of Aristotelian practical wisdom emphasizes continuous learning and the willingness to remain flexible as knowledge and circumstances change (Schur 34). Institutions need the same adaptability. Detection systems will face new designs, new evasion methods, and evidence of unexpected harms. Their rules must therefore be auditable and revisable rather than treated as permanently correct. AB 2047 partly recognizes this need by requiring a “process for periodically reviewing emerging detection software techniques” (California Senate Judiciary Committee 5). Periodic technical review, however, does not by itself protect users from unjustified expansion.
Set substantive limits on scope
The history of technological protection measures shows why substantive limits are also necessary. Adu-Amankwa and Daly warn that these systems raise “issues about the overreach of IP protection” and may impair legitimate uses, including spare-part production (Adu-Amankwa and Daly 602). A system initially defended as anti-counterfeiting could consequently obstruct repair or lawful competition if a rights holder controls the blacklist. Governance must therefore publish what categories may be blocked and why, disclose error and appeal outcomes, require independent audits, and give affected users notice, human review, and remedies. Restrictions should expire unless periodically reauthorized, and adding a new category of prohibited design should require fresh evidence and public justification rather than a silent software update.
Require fresh justification for every expansion
These safeguards do not assume that every future restriction is illegitimate. They ensure that each expansion must independently satisfy the Proportionate Refusal Framework. Because control can spread more easily through code than through openly debated law, accountable governance must be built into the system before deployment. Without enforceable limits, even an initially defensible refusal mechanism grants too much unreviewable power over lawful manufacturing.