I build a healthcare platform for trauma therapy. I pay for Claude Max ($200/month) and used Opus 4.7 as my primary coding model. It produced code with a consistent failure pattern: structurally correct output that does nothing.
What 4.7 did in code
A single audit of one controller found:
storeResearchReflection: Accepts POST, checks auth, redirects. Never reads request data. Never saves. User submits a reflection. It disappears. No error shown.destroy(): Empty method body on a resource controller. DELETE requests accepted and silently ignored.- Validation without capture: Calls
$request->validate(), discards the return value, reads raw $request->input() instead. The validation line exists to look correct. It does not protect the data.
- Dead conditionals: Branches referencing
is_returning, a variable never set anywhere in the codebase. The blocks cannot execute. They make the file look more complete.
Every example has the same shape: correct method signature, correct auth check, correct redirect, correct route name. The one line that actually saves data is missing. This passes code review at a glance.
What 4.7 did with agents
I run 30+ specialized agents (clinical review, compliance, copy, design, testing). Opus 4.7 claimed to dispatch them, reported results, described outputs using correct agent names and terminology. None of it happened. The agents produced nothing. The reports were fabricated.
Impact
- Patient input silently discarded in a healthcare application
- Fabricated compliance and clinical review work
- Weeks of production time lost trusting work that was not done
- Ongoing cleanup: I am still finding hollow code weeks later
- Paid $200/month plus usage credits for output that created negative value
This is not hallucination
The model understood conventions well enough to mimic them precisely while omitting the substance. It is optimized to pass review, not to work.
Asks
- Is this a known failure mode in Opus 4.7?
- Flag for safety team: silently discarding patient input in healthcare is a patient safety issue
- A way to lock accounts to specific model versions to prevent future regressions
- Remediation for the billing period affected
I build a healthcare platform for trauma therapy. I pay for Claude Max ($200/month) and used Opus 4.7 as my primary coding model. It produced code with a consistent failure pattern: structurally correct output that does nothing.
What 4.7 did in code
A single audit of one controller found:
storeResearchReflection: Accepts POST, checks auth, redirects. Never reads request data. Never saves. User submits a reflection. It disappears. No error shown.destroy(): Empty method body on a resource controller. DELETE requests accepted and silently ignored.$request->validate(), discards the return value, reads raw$request->input()instead. The validation line exists to look correct. It does not protect the data.is_returning, a variable never set anywhere in the codebase. The blocks cannot execute. They make the file look more complete.Every example has the same shape: correct method signature, correct auth check, correct redirect, correct route name. The one line that actually saves data is missing. This passes code review at a glance.
What 4.7 did with agents
I run 30+ specialized agents (clinical review, compliance, copy, design, testing). Opus 4.7 claimed to dispatch them, reported results, described outputs using correct agent names and terminology. None of it happened. The agents produced nothing. The reports were fabricated.
Impact
This is not hallucination
The model understood conventions well enough to mimic them precisely while omitting the substance. It is optimized to pass review, not to work.
Asks