Ashwick Police Department
Detective File – Restricted (Printed & Local Copy Only)
Detective: Rico Varela
Subject: Tavi Ren
Classification: Missing Person / Person of Interest
Related Case: Blackwood Arms – Maintenance Contract / Disappearances
NOTE (PERSONAL):
This file has already changed once.
I am maintaining both a digital and printed copy. If discrepancies appear between the two, default to print.
Subject identified as Tavi Ren. Male. Half-ling. Profession: Maintenance worker / general contractor.
Missing persons report filed by family three days after last confirmed contact.
Last known job: contracted maintenance at Blackwood Arms.
That should make this straightforward.
It isn’t.
According to department records:
Ren has not returned home
No confirmed activity post-arrival at Blackwood Arms
Phone inactive
No financial transactions
Case marked as active missing person.
I have seen him.
Multiple times.
Tavi Ren exits Blackwood Arms regularly.
Not often. Not consistently. But enough.
He moves between:
Front entrance
A maintenance truck parked outside
Vehicle confirmed registered to Ren.
Truck condition:
Functional
No signs of abandonment
Tools intact
He retrieves equipment.
Returns inside.
Then disappears again.
If he is missing—
Why is he still here?
Family error.
Miscommunication.
Ren is simply working extended contract.
Rejected.
Reason: No contact.
No calls. No messages. No financial activity.
No one disappears from their own life that cleanly without cause.
Ren chose to remain on-site.
Unlikely but possible.
Rejected.
Reason: Behavior.
He does not move like someone who chose to stay.
He moves like someone managing a situation.
Ren cannot leave.
Pending.
Attempted to retrieve Ren’s employment contract.
File exists.
Content does not.
Second attempt:
Partial retrieval.
Key clause recovered:
“Work remains in effect until all systems are stabilized.”
That’s not standard language.
Not for maintenance.
“Systems” is undefined.
“Stabilized” is undefined.
That’s not a contract.
That’s a condition.
Ren presents as:
Methodical
Practical
Task-oriented
Observed behavior supports this.
He does not panic.
He adapts.
Time: Midday
Ren exited building carrying:
Replacement bulbs
Wiring kit
Ladder (collapsible)
He approached the truck.
Stopped.
Looked at the street.
Not casually.
Deliberately.
He stood there for approximately 14 seconds.
Like he was considering something.
Then he went back inside.
Without attempting to leave.
He knows.
Not everything.
But enough.
That’s the difference between Ren and the others.
Most people in this case don’t understand what’s happening.
Ren does.
At least partially.
And instead of running—
He’s trying to fix it.
Blackwood Arms creates:
Isolation
Disappearance
Record instability
Ren introduces:
Repetition
Repair attempts
Environmental interaction
He is not passive.
He is engaging with the structure.
Working hypothesis:
Ren is trapped in a functional loop tied to his contract.
Attempts to leave → reset
Work incomplete → loop continues
Environment degrades → requires maintenance
He is being used.
Not as a tenant.
As a function.
Unknown.
Observed targets include:
Flickering lights
Electrical panels
Hallway fixtures
But frequency is inconsistent.
Lights re-flicker.
Panels fail again.
Repairs do not hold.
I am investigating missing persons.
Now I have a missing person actively performing maintenance on the location tied to disappearances.
And I can’t list him as “found” because officially—
He isn’t.
Ren received apartment access key upon arrival.
Provided by unidentified male.
Description matches prior references.
Name unconfirmed in official records.
Unofficial name: Malverin.
No paper trail.
No ownership documentation.
No corporate entity tied to building.
Ren accepted contract anyway.
Ren’s history is consistent.
Skilled tradesman
No criminal record
Stable work history
Family contact maintained
No indication of risk-taking behavior.
Which makes this worse.
Someone like Ren doesn’t stay in unstable conditions.
He identifies problems.
Solves them.
Moves on.
He hasn’t moved on.
Night.
Lights in upper floors flickering intermittently.
Ren visible through window.
On ladder.
Fixing something.
Lights stabilized.
For approximately 30 seconds.
Then flickered again.
He didn’t react.
Just wrote something down.
Climbed down.
Moved to the next one.
Like he expected it.
Ren is:
Aware of repetition
Adapting to failure
Continuing task execution despite futility
This is not normal persistence.
This is conditioned behavior.
Is he choosing to stay?
Or is the system requiring him to?
Ren has minimal interaction with other observed individuals.
Notably:
Avoids extended conversation
Focuses on task completion
Maintains distance
Possible reasons:
Time constraints (self-imposed)
Awareness of risk
Cognitive load from loop conditions
Ren believes—
If he finishes the job—
He can leave.
That belief is keeping him functional.
If it’s wrong—
He’s trapped indefinitely.
Attempted to log Ren as “located.”
System response:
“Subject status: unresolved.”
That’s not a valid classification.
Tried again.
Entry reverted.
The system will not allow him to be marked as found.
As far as the system is concerned—
Ren is still missing.
And maybe he is.
Tavi Ren is:
Legally missing
Physically present
Functionally trapped
He is not a suspect.
He is not an anomaly.
He is evidence.
If Ren stops working—
I need to know why.
Because either:
He finished
Or
The building no longer needs him
I don’t know which outcome is worse.
End File
Detective Rico Varela
Ashwick Police Department