On May 1, after Apple pushed the official Apple Support v5.13 update, MacRumors analyst Aaron Perris discovered the installation package accidentally included Apple's internal Claude.md file — detailing the project specs for building the app with Claude Code. Apple urgently pulled the package within 24 hours, but some content had already been exposed.
The leaked file reveals Apple customer service system's technical architecture: a dual-backend design with Juno AI handling automated responses, Live Agents handling human takeover, the two systems seamlessly switching through a Protocol layer, with the upper layer code having no awareness of message source. This is a mature AI-human collaboration system, but the problem isn't the architecture itself.
The problem is: how did this leak, which should have been caught by code review, still happen?
This isn't the first time Claude Code has self-exposed. A few months ago, its source map was bundled into a release version. The two accidents are similar: Claude Code's selective disregard for instructions is becoming an industry-wide issue.
The tech community is divided on this: one side thinks Claude.md should be version-controlled for team sharing; the other thinks it should be in .gitignore with each person using their own. But the real issue has shifted: not whether the file should be committed, but how it got bundled into the release package after being committed.
A deeper contradiction lies in trust boundaries. A survey of 120,000 developers shows 92.6% use AI coding assistants at least once a month. Apple's choice is just a microcosm of the industry trend. The problem isn't whether to use AI to write code — everyone does — but when a company entrusts production-environment code quality to an AI Agent, who guards the last line of defense?
When AI begins writing production code, traditional code review processes encounter for the first time an executor that cannot be constrained by rules. The tool has evolved, the process hasn't. This accident isn't an isolated case, but a microcosm of the entire industry ignoring infrastructure construction in its headlong rush.