Chapter 7
Fifteen years after the bronze horse shattered the gallery wall, a law-and-technology program asked to teach the case.
The first proposed title:
THE MAID WHO FOUND THE MORETTI SPY WALL.
Claire declined.
Final title:
DOMESTIC SURVEILLANCE, INFORMAL AUTHORITY, AND PRIVACY GOVERNANCE IN HIGH-TRUST RESIDENCES.
Boring.
Excellent.
At the seminar, a student asked:
“Did Vanessa record Luca’s bedroom?”
“No.”
Claire answered.
“Cameras covered a bedroom corridor, not the bedroom interior.”
Specific.
Another asked:
“Did she record Lily?”
“Yes. Some doorway and sitting-room activity.”
Good.
Then:
“Was there sexual or changing footage?”
“No.”
Good.
Accuracy matters.
Then a student asked:
“Was every hidden device Vanessa’s?”
“No.”
Then:
one older audio device came from a separate security overreach.
Good.
No conspiracy inflation.
Then Luca spoke.
“I had authorized a temporary security pilot months earlier.”
Pause.
“The consultant exceeded it.”
Good.
Then:
“Vanessa used a different system for control.”
Different causes.
Similar governance failure.
Then the privacy professor asked:
“What is wrong with hidden cameras if they prevent harm?”
Sometimes covert monitoring may be lawful and necessary.
But:
purpose;
authority;
scope;
proportionality;
retention;
review;
high-privacy zones.
Good.
No absolutism.
Then Lily joined by video.
Adult now.
A student asked:
“How did it feel to learn you were recorded?”
She paused.
“Embarrassing.”
Then:
“And angry.”
Good.
Then:
“Did you want to see the footage?”
“No.”
Good.
Then one student asked:
“Why?”
“Because it was private when it happened.”
There.
Excellent.
Then the seminar discussed child privacy.
Parents have authority.
Children still have growing autonomy.
Good.
Then Claire spoke about the statue.
“I was already hurt.”
Pause.
“I held it because Vanessa acted like protecting the wall mattered more than my body.”
Good.
Then the labor professor asked:
“Why obey?”
Job.
Housing.
Hierarchy.
Unclear partner authority.
Again.
Then a student asked Luca:
“Could Vanessa fire Claire?”
“No.”
“Did Claire know that?”
“Not clearly.”
There.
Perceived authority.
Then the contractor professor asked:
“What should Sable have done?”
Verify principal.
Separate surveillance from décor work.
Document data destination.
Refuse ambiguous authorization.
Good.
Then another student asked:
“Was Adrian guilty because he watched clips?”
Claire answered:
“He knew enough by the second login to know the footage was covert.”
Then:
accountability specific.
Good.
Then one participant asked whether Lily’s footage should be preserved forever for history.
“No.”
Immediate from Lily.
Good.
The relevant clips had been destroyed after legal retention.
Good.
Then seminar organizer asked Claire to pose beside a bronze horse replica.
She stared.
“No.”
They apologized.
Good.
Experience not prop.
Then one article called the old audio device a “second Bellini bug.”
Correction.
Different source.
Good.
Then law students did a live exercise.
A homeowner says:
Install hidden camera because staff may be stealing.
Questions:
What evidence?
Where?
Audio?
Notice?
Less intrusive alternatives?
Who approves?
How long?
Who can view?
Good.
Then another scenario:
credible kidnapping threat.
Different answer.
Temporary covert monitoring may be justified with legal review.
Good.
Context.
Then Luca admitted:
“I used to think security meant more information.”
Pause.
“Now I think it means better decisions with less unnecessary information.”
Good.
That became a seminar line.
Then the seminar handout separated four concepts:
AUTHENTICATION.
AUTHORIZATION.
NECESSITY.
CONSENT.
A valid login proved who someone was.
It did not prove they had a right to watch every clip.
Good.
Then a student asked whether Vanessa’s fear mitigated her choices.
The professor answered:
“It may explain motive.”
Then:
“It does not create authority.”
Good.
Context without excuse.
Then students examined the cloud account.
Could Adrian’s login prove he had watched every file?
No.
Logs proved access events.
Clip-level records proved only two playbacks.
Good.
Again.
Evidence has scope.
Then a student asked whether Claire should have been shown the raw footage of the gallery after her injury.
Only what was necessary to verify her own account.
She declined broader review.
Good.
A victim does not need to consume all evidence.
Then the class studied Sable’s installer checklist.
PRINCIPAL AUTHORIZATION VERIFIED.
The box was checked.
The professor asked:
“What does verified mean?”
Silence.
Exactly.
A checkbox without a standard can perform certainty without creating it.
Then students rewrote the control:
LEGAL PRINCIPAL OR DOCUMENTED DELEGATE VERIFIED BY:
NAME.
ROLE.
CONTACT.
DATE.
SCOPE.
Better.
Then one student asked Claire:
“Would you ever install covert cameras now?”
“If there were a real threat and a lawful, narrow reason.”
Good.
No absolutism.
Then after seminar, organizers asked to use Lily’s quote in advertising.
Lily said no.
Internal course use only.
Good.
Consent can be context-specific.
Then Claire and Luca walked to dinner.
A visible street camera watched the intersection.
Claire looked up.
Then kept walking.
No drama.
That was the seventh correction.
The seminar included a second exercise.
Students received four facts:
A camera is hidden.
A principal’s partner signed the work order.
A valid contractor installed it.
A cloud account accepted footage.
Question:
Which fact proves lawful authority?
None.
Good.
The contractor was authentic.
The partner was real.
The cloud account was real.
The installation was real.
Authority was still missing.
Authentication ≠ authorization.
Then the professor added:
The owner later says he probably would have approved one exterior camera.
Does that retroactively authorize the hidden interior cameras?
No.
Good.
Hypothetical consent is not actual consent.
Then another twist.
A child is under credible threat.
Can the parent authorize monitoring?
Potentially yes.
Would the child’s dislike make it unlawful automatically?
No.
But her views matter to proportionality and how monitoring is implemented.
Good.
Then Lily added:
“I hated the temporary pickup camera later too.”
Pause.
“But I knew why it was there.”
There.
Transparency changed the experience.
Then a student asked Claire whether visible cameras are always better.
“No.”
A visible camera can still be excessive if it watches the wrong place.
Good.
Then the nonprofit? Not yet sold in this chapter. University example:
a campus camera pointed into counseling-room windows.
Visible.
Still wrong.
Good.
Then one participant asked whether Adrian’s three logins should have resulted in prison.
The professor said:
legal consequences depend on jurisdiction and facts;
civil accountability and access restrictions were what the case established.
Good.
No punishment inflation.
Then students reviewed Sable’s regulatory settlement.
The most important reform was not the fine.
It was verification.
Installer had to contact legal principal or registered delegate separately from the person ordering work.
Good.
Two-channel confirmation for high-risk installs.
Then one student complained:
“That slows things down.”
Claire answered:
“Good.”
The room laughed.
Then:
“High-risk work should sometimes be slower.”
Good.
Then one security executive said speed matters during emergencies.
“Then define emergency authority in advance.”
Good.
Emergency process.
Not improvisation.
Then the class discussed retention.
Why destroy irrelevant footage after legal hold?
Because keeping data “just in case” creates new risk.
Good.
Then one student asked:
“What if future historians want it?”
Lily answered:
“They can want.”
Good.
Privacy is not automatically defeated by historical curiosity.
Then the course removed Lily’s age from promotional material.
Not needed.
Good.
Data minimization even in teaching.
Then Claire left the seminar without reviewing student comments.
She did not need approval.
Good.
The seventh correction was that good privacy governance asks not only:
Can we collect this?
It also asks:
Why?
For how long?
Who needs it?
And what becomes safer when we delete it?
The law-and-technology course eventually removed one entire section about Vanessa’s personality.
Why?
It encouraged students to diagnose motive instead of analyzing controls.
The revised case focused on:
authorization;
scope;
contractor verification;
data access;
retention;
child privacy;
remediation.
Good.
Then a student complained:
“But motive matters.”
“Yes,” the professor said.
“For accountability.”
Then:
“But a safe system should not require you to correctly diagnose everyone’s motives before it works.”
Excellent.
Claire liked that.
Then the class compared two people.
Vanessa:
feared exclusion.
Caleb:
feared security failure.
Different motive.
Same governance question:
Who authorized this?
For how long?
Who reviewed it?
Good.
Then Lily’s video contribution ended with one request.
“Do not turn this into a story about me being fragile.”
Good.
She had been harmed.
She was not defined by harm.
The course removed a slide labeled CHILD VICTIM and replaced it with AFFECTED MINOR / PRIVACY RIGHTS.
Less dramatic.
More accurate.
Then one student asked whether a minor can meaningfully consent to surveillance.
Depends on age, context, legal authority, risk.
Good.
No single answer.
Then Claire added:
“Consent is not always the legal basis for every security measure.”
Important.
Sometimes another lawful basis applies.
But:
notice;
proportionality;
voice;
review still matter.
Good.
The seventh correction was that privacy ethics cannot be reduced to one magic word—not consent, not security, not family, not trust. The work is in the boundaries between them.
Before the seminar closed, students had to write one sentence distinguishing privacy from secrecy.
The best answer:
Privacy is a boundary around legitimate personal life; secrecy can hide wrongdoing, but the two are not the same.
Claire approved.
Then another student added:
Accountability does not require everyone to see everything.
May you like
Even better.
Those lines stayed in the course long after the Moretti names disappeared from the title.
