44 Złota 44 Reviews What happened — documented
CONTENTS
12 bizarre questionsBetrayal mapSpa gameMod gameWhat happenedElectrical safetyCharacter assassination & isolationGDPR & legalUrgent inspectionCorrection recordGood nameRegisters
CURRENTSTARTWhat 300,000 PLN / year actually bought
PUBLIC DOCUMENTATION FOR FUTURE TENANTS, BUYERS, OWNERS, INVESTORS AND AGENTS

What 300,000 PLN / year rent actually bought at Złota 44.

This is what happened during a tenancy costing approximately 300,000 PLN per year. The screenshots and dated correspondence are the resident’s documentation. Decide whether the expectation matches the documented reality.

DISABILITY-CODED RECORD

A disabled resident paying 300,000 PLN/year asked if his apartment was electrically safe. He had also disclosed a neurological vulnerability. The Administration did not answer. They let him be publicly character-assassinated as “mentally unstable/on drugs”. This is the documented record.

THE SAFETY-GUARANTEE CLOCK

How long the “no irregularities / safety requirements” guarantee has been standing.

“No irregularities have been found and the building therefore meets the safety requirements.” — Złota 44 / Admus email, 18 April 2025, 12:38 PM
Running since the reassurance entered the written record
000days
00hours
00minutes
00seconds

Every second above is time since that reassurance stood while the 18–22 Ω question remained unanswered.

12 BIZARRE QUESTIONS TL;DR — Read the 12 most bizarre questions they still refuse to answer.

The strangest refusal points, screenshots first. For people who need the pattern before the entire archive.

Start the 12 bizarre questions →
THE BETRAYAL MAP How a Housing Community, their “Unaffiliated Foreign Proxy”, and a Management Company All Betrayed Each Other — Documented in Their Own Words

Internal tension becomes externally visible — snowballing into 84+ logical contradictions and 150+ unanswered questions.

Open the betrayal map →
Satirical side quest Play “Złota 44 Spa — The Boyfriend Test.”

A dark interactive game about proxy-authority, access control, relationship verification, and the word “unaffiliated” doing industrial-grade labor.

Start the spa game →
New: interactive moderation simulator Play “Złota 44 Mod — The Ban Button.”

A dark satirical game about Reddit-mod energy, proxy authority, GoPro surveillance, WhatsApp panic and the common-area ban button IRL.

Start the mod game →
THE STARTING POINT

This started with electrical shocks.

The resident had disclosed a documented neurological vulnerability. A technician had already identified a grounding issue in at least one outlet, tightened screws and left. The shocks and abnormal electrical behaviour continued — including a bathroom light switching off computer equipment and shocks reported at elevator panels.

He did not accuse them of causing the shocks. He asked a narrower question: can you verify whether the electrical system is safe? They never answered it. That left a neurologically vulnerable resident inside the apartment without knowing whether ordinary electrical use could shock or injure him.

WHAT THEY KNEW

Shocks. Neurological vulnerability. A real outlet-grounding issue.

Their technician had already found a grounding problem. The shocks continued. They knew the resident had a documented neurological vulnerability.

WHAT HE ASKED

Verify the safety. Explain the 18–22 Ω readings.

If 18–22 Ω was safe, name the standard and say so. If it was not, explain what was repaired. They did neither.

WHAT FOLLOWED

They did not answer the safety question. They attacked the person asking it.

They refused direct CCTV answers, intercepted the police report, distributed a drugs / mental-health character assassination through the resident WhatsApp group labelled “Official WhatsApp group,” removed the resident from that channel, refused the Article 15 request, weaponized legal machinery over two free bottles of mineral water, then missed their own “urgent” inspection deadline and blamed the disabled resident.

THE LOGICAL ENDPOINT

They gaslit a resident who had disclosed a neurological vulnerability — and attacked his credibility instead of addressing the hazard that threatened his condition.

The cold record: electrical shocks can trigger seizure-related conditions. Seizures can be fatal through SUDEP, injury or aspiration. The resident disclosed a neurological vulnerability. The resident is also neurodivergent. The Administration knew about the reported shocks. Their own documentation contained 18–22 Ω readings. They still refused the technical answer and the resident-channel response became drugs / mental-health character assassination.

THE COLD MATH

The gap between hazard and catastrophe is not large.

  • Electrical shocks can trigger seizures.
  • Seizures can be fatal.
  • The neurological vulnerability was disclosed.
  • The shocks were reported.
  • The 18–22 Ω readings were in their own record.
  • The smear was never withdrawn.
THE RESPONSE THEY CHOSE

They did not answer the safety question. They attacked the person asking it.

The resident reported electrical shocks and disclosed a neurological vulnerability for which electrical shock exposure was a serious medical concern.

The Administration’s ecosystem enabled an “unaffiliated representative” — an apparent authority figure — to tell 120+ residents that the same person appeared mentally unstable, under the influence of unknown substances and that “zero irregularities” had been found.

Resident

“I’m experiencing electrical shocks. I have disclosed a neurological vulnerability. This is serious.”

Administration-side record

“Mental issues / unknown substances.” “Zero irregularities found.” “No further answers will be provided.”

NEURODIVERGENCE IS NOT INSTABILITY

Neurodivergence is not instability.

The resident disclosed a neurological vulnerability so the Administration would understand why electrical-safety confirmation was medical necessity, not preference. The resident is also neurodivergent.

Neurodivergence is not mental illness. It is not instability. It is not substance abuse. The traits attacked in the record — persistence, refusal to let go, detailed documentation and tight logical chaining — are part of the resident’s neurotype itself.

Calling that person “mentally unstable” is not just an insult. The traits they attacked — persistence, refusal to let go, detailed documentation and tight logical chaining — are the same traits that made the resident keep documenting instead of going quiet.

The Administration-side response was to enable an “unaffiliated representative” — an apparent board / authority figure in the resident environment — to frame him in front of 120+ residents as psychologically unstable and under the influence of unknown substances. The resident provided a clean psychiatric evaluation and negative drug tests. The Administration has never withdrawn the smear.

They attacked him for displaying the traits that made him harder to dismiss. They tried to pathologise the traits that documented their liability. That is equivalent to mocking someone for a wheelchair — then telling 120 neighbours the wheelchair user is “lazy” for not taking the stairs.

The message to every resident with a condition — neurological, neurodevelopmental, or otherwise — is clear: disclose it to this Administration, and the disclosure can become a weapon used against you. The resident disclosed a neurological vulnerability. It was weaponized. What neurodivergent resident would disclose a condition after seeing what happened?

The disclosure meant to ensure his safety became the weapon used to destroy his credibility.

The resident disclosed a neurological vulnerability in good faith. The purpose was clear: electrical safety was a medical necessity, not a preference.

A resident reporting electrical shocks who is also neurologically vulnerable can be neutralized by calling him “mentally unstable.” A resident who understands technical electrical details can be discredited by suggesting he is “under the influence of unknown substances.” The smear targeted the exact credibility point created by the medical disclosure.

If the resident had been injured by an electrical fault, the documented defense path would have been: “we thought he was making it up because he was unstable.” That is not a safety protocol. That is the record they created.

This is not a routine tenant dispute. It is a documented disability-targeting pattern: the safety disclosure made in good faith became the vector of attack, with screenshots, timestamps and an unwithdrawn smear. The traits used to attack his credibility are the same traits that made the record impossible to bury.

The electrical hazard could have been verified. The administrative hazard is deeper: a disclosed vulnerability became a credibility target.

MEDICAL RECORDThe psychiatric evaluation was clean.
DRUG TESTSThe drug tests were negative.
TECHNICAL RECORDThe electrical record was real.
EXPECTATION VS DOCUMENTED REALITY

You decide whether the service matched the price.

Expectation

A standard-based answer after electrical shocks and a disclosed neurological vulnerability.

Reality

Computer, mouse, chair, carpet, clothing and towel. They never answered the 18–22 Ω question.

Expectation

A disclosed neurological vulnerability makes electrical-shock reports a safety priority, not a personality issue.

Reality

The resident-channel response was drugs / mental-health character assassination, a ban from the official WhatsApp correction channel, common-area restriction, and no withdrawal after clean medical and drug-test rebuttal.

Expectation

A resident who disclosed neurological vulnerability is treated with safety-focused accuracy, not credibility attacks.

Reality

The disclosed vulnerability became part of the credibility attack: “mental issues” / “unknown substances,” no same-channel correction, no withdrawal and no accountability.

Expectation

If the issue “exists only in your apartment,” identify the apartment-specific cause.

Reality

An explanation built from objects found in almost every apartment. Was this the only apartment in Złota 44 with a mouse, chair, clothes and a towel?

Expectation

After a GDPR Article 15 deadline failure, communication becomes more transparent, written and traceable.

Reality

Post-it notes routed through concierge. Company, technician and insurance identities withheld. No written arrival confirmation before their own deadline.

Expectation

A direct CCTV answer: was the door visible, and did anyone touch the lock?

Reality

They refused to show the footage, refused to state the retention period, and refused to answer whether the door was visible or whether anyone had touched the lock. The police report was intercepted.

Expectation

Legal machinery addresses court threats, character assassination, data-access failures and police-report interception.

Reality

They weaponized a law office against the resident over two FREE bottles of mineral water. They issued no correction, no withdrawal, no reprimand and no documented sanction for the Unaffiliated Foreign Representative who made court threats, circulated the drugs / mental-health character assassination, displayed internal email and CCTV knowledge, and intercepted the police report.

Expectation

A Polish prestige building does not enable a foreign authority-like actor who disrespects the integrity of the Polish people under its name.

Reality

The attacked resident defended Poland immediately. The Administration enabled the Unaffiliated Foreign Representative who disrespected Polish integrity; later, the disabled, neurologically vulnerable resident who defended it was smeared as mentally unstable and under unknown substances.

Expectation

An “urgent” inspection is confirmed, documented and completed.

Reality

Approximately 83 days of delay. They miss their own deadline. Then they place “no confirmation from you” directly above the resident’s repeated written confirmations.

Public-copy policy: private names, emails, apartment number, phone numbers, medical identifiers and unrelated personal data are redacted. The operative wording, dates and sequence remain visible.

CHAPTER 01WHAT HAPPENED
The complete sequence

They did not answer the safety question. They attacked the person asking it.

They left a neurologically vulnerable resident without electrical-safety verification. Then came move-out pressure, a vulnerable door and blocked CCTV verification, police-report interception, character assassination in the official resident channel, blocked correction channels, refusal of the Article 15 request, legal machinery over free water, urgency theatre, a missed deadline and a false “no confirmation” narrative.

01APRIL 2025

They refused to answer whether the electrical system was safe

Their technician had already found a grounding issue. The shocks and abnormal electrical behaviour continued. They refused to say whether 18–22 Ω was safe or identify the standard.

0217 APRIL 2025

Move out instead of verify

The “unaffiliated representative” writes that administration has had enough, further technicians cost money, and people replace the resident even when the problem exists.

03LATE APRIL 2025

They left the door vulnerable and blocked CCTV verification

The lock feels looser. The rosette is missing. Metallic-impact audio is recorded. The resident asks to check CCTV. They refuse the footage, refuse the retention period, and refuse to answer whether the door is visible. The lock was never fixed during the tenancy.

04LATE APRIL–MAY 2025

The Unaffiliated Foreign Representative intercepted the police report

After a significant Złota 44 stakeholder says “you should call the police,” the Unaffiliated Foreign Representative who presented himself as “Management board member of Z44” is notified before the resident who made the call. He arrives equipped with a GoPro and microphone, intercepts the police report, and isolates the officers from the resident inside an area where the resident’s access had been removed.

05LATE APRIL–MAY 2025

Character assassination. Then isolation.

“Mental issues / under the influence of unknown substances” is distributed to more than 120 residents through the WhatsApp group advertised as “Official WhatsApp group,” together with a court threat. The character assassination is never withdrawn. The resident is banned from the same official WhatsApp channel and common-area access is restricted, eliminating his ability to correct the false narrative there.

06OCTOBER–NOVEMBER 2025

They refused the Article 15 request

The Article 15 request specifies data, logs, CCTV, recipients, dates and a narrowed fallback. The deadline expires. The controller and processing structure then use “lack of organizational and technical capacity” as the stated reason to avoid producing the data they run.

07NOVEMBER–DECEMBER 2025

They weaponized a law office over two FREE bottles of mineral water

They answer an insurer request by clearing themselves of liability. Then a law office formalizes a 30-day restriction against the resident over two free bottles of mineral water. They document no comparable sanction for the Unaffiliated Foreign Representative behind the court threats, character assassination, data-access questions and police-report interception.

08NOVEMBER 2025–FEBRUARY 2026

Urgency theatre after the GDPR deadline failure

Immediately after the Article 15 deadline failure is escalated, they call an inspection urgent and link it to safety and insurance. Then they delay it approximately 83 days while routing communication through concierge and post-it notes and withholding company, technician and liability details.

099 FEBRUARY–MARCH 2026

They miss their own deadline and blame the resident

The resident repeatedly confirms and stays available. They miss their own deadline, then write “no confirmation from you.” Exact correction questions later receive “all questions answered” and “matter resolved.”

CHAPTER 02ELECTRICAL SAFETY ORIGIN
18 April–15 May 2025 / actual email screenshots

The question was “am I safe?” They refused to answer it and wrote: “no further answers will be provided.”

THE CORE RECORDReported electrical shocks. A documented neurological vulnerability. Repeated requests for technical verification. Then: “no further answers will be provided.”

The administration knew about the shocks, the documented neurological vulnerability and the prior outlet-grounding issue. The resident asked them to verify whether the electrical system was safe and explain the documented readings.

EMAIL 01 OF 12 · 18 APRIL 2025“No irregularities” — then computer, mouse, chair, carpet, clothing and towel.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Administration response on electrical shocks and static electricity
Administration response to reported shocks: “no irregularities,” followed by computer, mouse, chair, carpet, clothing and towel.
EMAIL 02 OF 12 · 18–21 APRIL 2025The resident repeatedly asks for the missing 18–22 Ω answer and documents the neurological risk.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Repeated electrical-safety verification requests and neurological-vulnerability notice
The resident asks for the missing 18–22 Ω answer and records the neurological vulnerability and elevator-panel shocks reported by others.
EMAIL 03 OF 12 · 22 APRIL 2025The unresolved electrical question and the first CCTV request appear in the same dated thread.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
CCTV request, repeated 18–22 ohm question and administration closure response
The first CCTV request and the unresolved electrical question appear in the same dated thread.
EMAIL 04 OF 12 · 22–23 APRIL 2025The resident pins the safety implication. The administration replies: “no further answers will be provided.”
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Resident safety-verification email followed by no-further-answers response
The resident asks who reviewed the footage and whether the reassurance includes the 18–22 Ω readings. The signed response refuses further answers.
THE NEXT PHASEThey had not solved or verified the electrical problem. They had only stopped answering. Then the door, lock and CCTV problem began.
EMAIL 05 OF 12 · 29 APRIL 2025After door and lock concerns, the resident again documents electrical risk, neurological vulnerability and the CCTV blind spot.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Email documenting electrical reliance, neurological vulnerability and door-CCTV concerns
After the lock and door problem begins, the resident again records the electrical risk, neurological vulnerability and CCTV blind-spot problem.
EMAIL 06 OF 12 · 30 APRIL 2025Administration response: “answers ... already been provided.” Further information goes to the owner.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Administration response saying answers were already provided and redirecting further information
They claim the answers were already provided, refuse the direct questions, and push the record to the apartment owner.
EMAIL 07 OF 12 · 6 MAY 2025One final request for technical clarification. The 18–22 Ω question still goes unanswered.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
The resident's final written request for clarification of the 18–22 ohm readings
The final written chance asks whether their lawyers were given the full technical and medical record.
THE DODGE They answered the final 18–22 Ω request with a blanket safety claim, an owner redirect and “unfounded accusations.”
EMAIL 08 OF 12 · 7 MAY 2025They refuse the 18–22 Ω question, redirect to the owner, and call the documented safety concerns “unfounded accusations.”
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Administration response to the final 18–22 ohm clarification request
They refuse the 18–22 Ω question, redirect responsibility to the owner, and call the resident’s documented concerns “unfounded accusations.”
THE FOLLOW-UP THEY FORCED The resident then put the complete technical contradiction in writing and copied the energy regulator.
EMAIL 09 OF 12 · 8 MAY 2025After the dodge, the resident sends the complete electrical-safety record to the administration and the energy regulator.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
First page of the resident electrical safety escalation copied to the energy regulator
The resident sends the complete electrical-safety record to the administration and the energy regulator.
EMAIL 10 OF 12 · 8 MAY 2025The responsibility shift, omitted measurements and repeated “zero irregularities” assurances are placed side by side.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Second page of the resident electrical safety escalation
The responsibility shift, omitted measurements and repeated “zero irregularities” assurances are placed side by side.
EMAIL 11 OF 12 · 8 MAY 2025The same record documents the character assassination, the wider safety risk and the demand for correction.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Third page of the resident electrical safety escalation
The same record connects the unresolved safety question to the resident-channel character assassination and the demand for correction.
EMAIL 12 OF 12 · 15 MAY 2025Their next answer: contact the apartment owner.
ACTUAL EMAIL SCREENSHOT · TAP TO OPEN FULL SIZEOPEN FULL SIZE ↗
Final page of the resident electrical safety escalation and the next administration response
Their next answer is still: contact the apartment owner.
What happened nextThey still refused to answer the technical question.

On 7 May, they refused the 18–22 Ω question, shifted responsibility to the apartment owner and labelled the documented safety concerns “unfounded accusations.” They still did not name the standard or say whether the readings were acceptable.

The resident then sent the full contradiction to the administration and copied the energy regulator. Their next answer was still: contact the Owner.

Why it mattersThe complete record was placed in front of them.

The values, the later omission, the neurological-vulnerability disclosure, the loose wiring, the repeated safety assurances, the legal-counsel question and the wider risk to residents were all put in writing.

They still refused the central technical question.

DOCUMENTED RECORD01
TECHNICAL PDF / ELECTRICAL READINGS

18–22 Ω

WHAT THIS DOCUMENT SHOWS

The technical-report excerpt showing the 18–22 Ω readings.

Record 01Technical PDF
THE NUMBER IN THEIR RECORD18–22 Ω

It appears in the technical-report excerpt.

THE ONLY QUESTION

Are those values acceptable under the applicable standard — yes or no?

THE ANSWER STILL MISSING

If acceptable: state the standard. If not: state the fix.

Electrical report excerpt showing 18 to 22 ohm readings
Technical-report excerpt. The values are shown as written. The question is not reassurance. The question is the standard.
Open question

If yes, name the standard. If no, explain what was fixed.

CHAPTER 03CHARACTER ASSASSINATION AND ISOLATION
What happened · how the resident documented it

They did not answer the safety question. They attacked the disabled resident asking it. This is what disability discrimination looks like in the record.

The resident asked for verification. He had disclosed neurological vulnerability. They answered with move-out pressure, authority games, internal-information leaks, a drugs / mental-health character assassination in the official resident channel, and removal from the same channel before he could correct the record.

THIS IS DISABILITY-DISCRIMINATION EVIDENCE

They tried to pathologise the traits that documented their liability.

Persistence, detailed timestamps, tight logic, medical disclosure, refusal to disappear — those were the traits that preserved the record. Those were the traits they tried to convert into “mental issues” and “unknown substances.”

DOCUMENTED RECORD02
WHATSAPP MESSAGE / OPERATING DOCTRINE

“Replace the person who notices.”

WHAT THIS DOCUMENT SHOWS

A private warning that people who keep questioning the system are replaced instead of the problem being fixed.

Record 02Verbatim messageOperating doctrine
“Im just telling to u as a friend and please don't share it, here in Poland people don't want to be questioned or be under pressure, they will simply change you with someone who has no problem with this even if exist.”
Verbatim message warning that the person who notices a problem gets replaced instead of the problem being fixed
Verbatim message received before the later escalation. Unrelated conversation context omitted.
Why it matters

This was written before the later escalation. It says the quiet part out loud: if the questions continue, replace the person asking instead of fixing the problem.

THE RESIDENT’S IMMEDIATE RESPONSE

The “Unaffiliated Foreign Representative” disrespected the integrity of the Polish people. The attacked resident defended it.

WHAT THE STATEMENT MEANT

A foreign “Unaffiliated Representative” allowed and enabled to operate under Złota 44 authority perception told the resident:

“In Poland, they don’t fix problems — they replace the person who notices.”
THIS IS NOT A GENERIC INSULT

This is the literal operating doctrine of the Soviet / communist system that occupied Poland from 1945 to 1989. Under that system, problems were not solved — the people who identified them were removed.

The “Unaffiliated, Foreign Representative” attributed this mechanism not to any specific regime, but directly to the Polish national character itself.

Plain reading: he was saying that this is Polish people’s nature now — that replacing the person who notices is still how Polish people behave. Not a false stereotype left behind by occupation. Not a dead regime’s residue. A present-tense claim about Polish people.

The resident — Swedish, not Polish — immediately recognized the insult and responded:

“My experience with Polish people has been incredibly positive — personally and professionally. I could easily live anywhere in the world, but I specifically chose Poland because of how deeply people here understand and value respect, honesty & integrity — my personal core values. I respect them deeply as a nation, and actually genuinely feel stronger patriotism towards Poland than Sweden.”
ACTUAL WHATSAPP SCREENSHOT · TAP TO OPEN FULL SIZE OPEN FULL SIZE ↗
Resident response defending Polish integrity after the unaffiliated representative claimed Polish people replace the person who notices problems
The response appears directly after the representative’s message about Polish people replacing the person who notices problems. The resident’s response defends Poland and Polish integrity.
THE BUILDING SYMBOL
ARCHITECTURAL INTENT

“The wing-shaped façade takes inspiration from the wings of the Polish eagle, countering the Communist-era Palace of Culture situated directly across and celebrating a new age of democracy in Poland.”

The Administration is the Polish team representing a Polish prestige building described by its architect Daniel Libeskind as intentionally designed to symbolize the free Polish eagle — a counterpoint to the Soviet-"gifted" Palace of Culture across from it.

That Administration enabled the “Unaffiliated, Foreign Representative” who invoked the logic of Poland’s communist occupation against its own people while operating under Złota 44 authority perception.

Złota 44 beside the Palace of Culture and Science in Warsaw
Złota 44 beside the Soviet-"gifted" Palace of Culture. The symbolism is not abstract; it is literally across the skyline.
THE LOBBY CONTRADICTION

The first thing you see when you enter Złota 44 lobby is Libeskind’s beautiful words. His heart is on that wall.

Right in front of Libeskind’s love letter to ojczyzna — inside his literal post-Communist freedom monument — a “Foreign Unaffiliated Representative” operated under proxy-authority enabled by the Administration, intercepted the police report, while wearing a GoPro and microphone.

Not in some shady back-office. Literally in front of the architect’s heart: his declaration of love for the very thing being betrayed.

The neurodivergent resident has many times pointed out the unfortunate irony of how they deploy proxy-governance inside a post-Soviet freedom monument. They have not yet taken any opportunity to clarify or correct this extremely inappropriate... “asset-management style”.

Złota 44 lobby wall text for the exhibition Być jak Daniel Libeskind
Złota 44 lobby wall text: “Być jak Daniel Libeskind” — Being Like Daniel Libeskind.
THE LOBBY CONTRADICTION

The building is Daniel Libeskind’s love letter to ojczyzna — the free Polish eagle, the wing-shaped façade, the architectural counterpoint to the Soviet-“gifted” Palace of Culture across the skyline.

Inside that love letter, the lobby wall displays an exhibition called “Być jak Daniel Libeskind”Being Like Daniel Libeskind. It is a portal into the architect’s intimate inner world.

Direct transmissionHand to paper. Nothing mediating. The purest form of communication.
TransparencyThe sketches reveal everything — his character, sensitivity, history, visual memories, even his mood.
Truth-tellingNo software. No filters. Just the architect’s mind transmitted directly.

This is what Libeskind’s inner world values. This is what he chose to place inside his love letter to Poland.

Right in front of that portal — in front of the architect’s inner world, his celebration of transparency and direct transmission — a “Foreign Unaffiliated Representative” operated under proxy-authority enabled by the Administration.

He intercepted the police report. He wore a GoPro and a microphone. He isolated police officers from the resident inside an area where the resident’s access had been removed.

Not in some shady back-office. Literally in front of the portal to Libeskind’s inner world — the world that values transparency, directness, and truth.

And what logic did the Administration enable, right there, in front of that wall?

Soviet occupation logic.
“In Poland, they don’t fix problems — they replace the person who notices.”
— Unaffiliated Foreign Representative

Truth-obscuring. The epistemology of authoritarianism. Attributed directly to the Polish national character itself.

The wall celebrates truth-telling.

The Administration enabled truth-obscuring.

In front of the wall.

Inside the love letter to Poland.

The neurodivergent resident has many times pointed out the unfortunate irony of how the Administration deploys proxy-governance inside a post-Soviet freedom monument. They have not yet taken any opportunity to clarify or correct this extremely inappropriate asset-management style.
THE REVERSAL Instead, they publicly validated his logic by allowing the resident who defended Poland to be framed as “mentally unstable” to 120+ neighbours.

The Administration enabled the Unaffiliated Foreign Representative who disrespected the integrity of the Polish people. The disabled, neurologically vulnerable resident who defended Polish integrity was character-assassinated.

THE DIRECTOR’S AUTHORITY ANSWER

The Quality Assurance Director’s official in-person statement — routed through two young Polish female proxies, functioning as emotional responsibility / liability / plausible-deniability shields — was:

“Anyone can claim to be whoever they want to be.”

It appears as if some patriarchies operate like it is still 1973 — when the official truth was whatever the Party said, and something else still dominated the skyline.

THE OCCUPATION PATTERN — 1945–1989
“Anyone can claim to be whoever they want to be.”

Official statement delivered by the Quality Assurance Director, routed through two young Polish female proxies. The epistemology of authoritarianism.

What happened to Polish people who defended Polish integrity during the occupation?

They were targeted. People who spoke truth about the system were labelled “mentally unstable”, “nervous disorders”, “anti-social personality”. Psychiatric diagnosis was a tool of political suppression.

  • Isolated from their communities.
  • Subjected to legal harassment.
  • Surveilled. Police report intercepted. Reports filed. Access restricted.
  • Framed as the problem.

This is not ancient history. This is the documented pattern of how the occupation operated.

What happened to a resident who defended Polish integrity inside Libeskind’s free Polish eagle?
THE OCCUPATION PATTERN — 1945–1989 ZŁOTA 44 — 2025
Labeled mentally unstable “Mental issues / under the influence of unknown substances” — distributed to 120+ residents.
Isolated from the community Removed from the official WhatsApp group. Common-area access restricted.
Subjected to legal harassment Law office engaged over two bottles of mineral water. “Good name” invoked.
Surveilled and intercepted CCTV withheld. Police report intercepted by a foreigner with a GoPro. Instagram stories monitored by the official account.
Framed as the problem The person asking for electrical safety verification became the target. The safety question was never answered.

Question: did anyone in the Administration recognise what they were doing?

The pattern is not subtle. It is one of the most documented patterns in Polish history. Yet they still managed to replicate it in 2025.

If they failed to recognise it: that is a catastrophic failure of historical awareness for an institution operating inside a literal post-Soviet freedom monument.

This is literally why the resident even disclosed his medical conditions in good faith. He ignored the flawed, corrupt logic of the “Foreign Unaffiliated Representative”, assuming there was no way the Administration could be that unaware; however, they decided to stick with their proxy-strategy even after it was pointed out to them.

THE STATEMENT “They simply change you with someone who has no problem with this even if exist.”
THE RECORD They did not fix the problem. They replaced the problem with the person who noticed it.

Electrical questions were not answered. CCTV questions were not answered. Authority questions were not answered. Data-access questions were not answered. The resident was removed, restricted, smeared and isolated.

Then they character-assassinated that same resident to 120+ neighbours as “mentally unstable” and “under the influence of unknown substances.”

That is the documented reversal.

Open question to the Administration: is Daniel Libeskind’s office aware of how his monument to ojczyzna is being managed?
And why did you send “good name” cease-and-desist legal letters to the person defending your own national integrity — rationing his two bottles of free mineral water like it is still 1973 — in the legal good-name of the post-Soviet freedom monument?
DOCUMENTED RECORD03
WHATSAPP MESSAGE / DEVELOPER + “SOME INSTITUTES”

They spoke to the developer and “some institutes.” Their conclusion: 18–22 Ω “seems normal.”

WHAT THIS DOCUMENT SHOWS

The message saying the developer and “some institutes” were consulted and that 18–22 Ω “seems normal.”

Record 03“Unaffiliated” representativeInternal knowledge paradox

The person later described as unaffiliated wrote that “they talked to the developer and also some institutes.” The result was not an identified standard, threshold, calculation or signed technical explanation. It was: “Numbers seems normal for them.”

AFTER THE DEVELOPER + “SOME INSTITUTES”18–22 Ω “seems normal.”No named standard. No threshold. No calculation. No written technical basis.
Redacted WhatsApp screenshot showing unaffiliated representative discussing administration reports, developer, institutes and pressure
Plain reading

They escalated the question to the developer and unnamed “institutes,” then reduced the technical answer to “seems normal.” The same message came from the person later described as unaffiliated, who somehow knew what the administration, developer and technicians had concluded.

DOCUMENTED RECORD04
THREE-PART SEQUENCE / HEALTH + CHARACTER ASSASSINATION + AUTHORITY

“Your health is the most important.” Two weeks later: character assassination.

WHAT THIS DOCUMENT SHOWS

The move-out-for-health message, the later drugs / psychological-issues character assassination and the sender’s authority self-description placed in one sequence.

Record 04Replacement pressureHealth / move-out pressure

On 17 April, the Unaffiliated Representative told the resident to move out because “your health is the most important.” Two weeks later, the same resident was character-assassinated as under unknown substances or suffering psychological issues. The Unaffiliated Foreign Representative had presented himself through “Zarząd Złota 44” and as “Management board member of Z44” before administration relabelled him unaffiliated.

17 APRIL / PRIVATE MESSAGE“your health is the most important”
Redacted WhatsApp screenshot showing move-out-for-health pressure and message about replacing the person who notices problems
The resident is told to move out for his health.
TWO WEEKS LATER / RESIDENT CHANNELUnknown substances / psychological issues
Resident-channel message alleging unknown substances or psychological issues; profile image redacted
Two weeks later, the same resident is publicly character-assassinated through drugs and mental-health claims.
AUTHORITY SELF-DESCRIPTION“Management board member of Z44”
Redacted WhatsApp screenshot showing a message signed as management board member of Z44
He presents himself as building authority; administration later calls him unaffiliated.
The sequence

Health was first used to push the resident out. Two weeks later, drugs and mental-health claims were used to destroy his credibility in the resident channel. The Unaffiliated Foreign Representative presenting himself as “Zarząd Złota 44” / “Management board member of Z44” was then relabelled unaffiliated.

DOCUMENTED RECORD05
OFFICIAL-CHANNEL SIGN + RESIDENT MESSAGE

Character assassination through the “Official WhatsApp group”

WHAT THIS DOCUMENT SHOWS

The physical sign labels it “Official WhatsApp group.” The character-assassination message was distributed through that channel.

Record 05Resident-channel message

More than 120 residents received a drugs / mental-health character assassination, a court threat and an announcement that the resident had been removed.

Sign identifying the Official WhatsApp group; active invitation QR redacted
Physical sign identifying the “Official WhatsApp group.” The active invitation QR is redacted; the label remains visible.
Resident-channel message alleging unknown substances or psychological issues; profile image redacted
The character assassination circulated in the resident channel. The wording and timestamp remain visible.
What it did not answer

It answered none of the safety, CCTV, GDPR, insurance or authority questions. It attacked the resident instead.

DOCUMENTED RECORD06
REDACTED MEDICAL DOCUMENT

The formal medical record destroys the character assassination.

WHAT THIS DOCUMENT SHOWS

The medical certificate directly destroys the drugs / psychological-instability claims: no psychosis, no delusions, no substance addiction, stable mental state, logical, coherent and factual presentation.

Record 06Medical rebuttalSensitive data redacted

The resident channel portrayed the resident as drugged or psychologically unstable. The medical certificate records the opposite: no psychosis, no delusions, no substance addiction, stable mental state, logical, coherent and factual presentation.

REDACTED MEDICAL DOCUMENT · OPEN FULL SIZEOPEN FULL SIZE
Redacted English medical certificate excerpt directly contradicting psychosis, delusion and substance allegations
English certificate excerpt. Nonessential diagnosis and medication details are redacted; the findings that directly destroy the resident-channel character assassination remain visible.
Why this matters

They attacked his sanity and sobriety. The formal medical record directly destroys both claims. They were given an explicit correction route. They refused. The character assassination remains uncorrected in the channel from which they removed him.

The character assassination traveled. The UODO-facing breach analysis remains invisible.

DOCUMENTED RECORD07
AUTHORITY SELF-DESCRIPTION

“Best regards, (REDACTED), Management board member of Z44”

WHAT THIS DOCUMENT SHOWS

The resident-facing actor signing as “Management board member of Z44” before being described as unaffiliated.

Record 07“Unaffiliated” representativeManagement-board self-description

The same resident-facing actor signs a message as “Management board member of Z44.” Later, responsibility is distanced by calling him unaffiliated.

Redacted WhatsApp screenshot showing a message signed as management board member of Z44
Why it matters

If the title was false, why was it allowed to stand? If it was true, why deny responsibility?

SUPPORTING AUTHORITY RECORD A
SEPARATE RESIDENT / INFORMAL POWER WARNING

A separate resident described the same informal-power structure.

WHAT THIS DOCUMENT SHOWS

A neighbour at Złota 44 independently described informal power, blurry lines between security, administration and owners, and said “they kind of waged a war against me at some point.”

Separate resident Unprompted warning Informal power

A neighbour at Złota 44 sent these messages during the events documented on this page. The resident had no stake in the dispute. The messages were unprompted.

A SEPARATE RESIDENT SHARES A SIMILAR EXPERIENCE “[He] has a lot of informal power over the building. Security staff is willing to do inappropriate things. The lines between security, administration and home owners association seem quite blurry. [He] seems to have the most power. As a tenant you have less power than you think. You need to be on good terms with everyone — even being rude to the cleaning staff could have negative consequences. They kind of waged a war against me at some point.”
Separate resident message stating the unaffiliated representative has informal power, security staff is willing to do inappropriate things, and tenants have less power than they think
Separate resident warning: informal power, security staff, gossip, owners, administration and tenant vulnerability.
Separate resident message stating the lines between security, administration and owners association are blurry and they kind of waged a war against the resident
When asked what “informal power” meant, the neighbour described blurry lines between security, administration and owners, then added: “they kind of waged a war against me at some point.”
WHAT THIS CONFIRMS
  • The “unaffiliated representative” had real power — confirmed by a separate resident.
  • The Administration’s “unaffiliated” claim is contradicted by residents inside the building.
  • Security staff doing “inappropriate things” was known to other residents.
  • The authority structure was not clear to residents: “blurry lines” between security, administration and owners.
  • The culture of pressure and retaliation was not isolated to one dispute.
  • The resident was not the first target. A neighbour also described being “waged war” against.
Why it matters

The Administration called the resident “mentally unstable” for documenting what another resident independently described. The screenshots are preserved. The pattern is confirmed.

SUPPORTING AUTHORITY RECORDB
AUTHORITY PERCEPTION / SEPARATE WITNESS

The “unaffiliated” person was also understood as Head of Security.

WHAT THIS DOCUMENT SHOWS

A separate person stated that the same actor was “head of security,” then confirmed he had told her that himself.

Authority perceptionSeparate personName redacted

Złota 44’s later position was that this person was private / unaffiliated. The documented social reality around the building was different. In this separate conversation, the other person refers to him as “the head of security.” When asked directly, she answers: “Yes as far as I know, he told me that one time.”

If the administration says he was unaffiliated, then the question becomes worse: why was an unaffiliated person able to generate repeated authority-perception inside and around the building without correction?
Chat screenshot stating the head of security was behind the resident and some tenants walked by
Separate conversation. The other person identifies “the head of security” as present nearby.
Chat screenshot where the resident asks head of security and the other person identifies the actor; name redacted
Name redacted. The other person links the “head of security” description to the same actor.
Chat screenshot confirming the actor told the other person he was head of security, followed by administration saying he does not work there
When told the administration said he does not work there, the response is: “Really? Okay interesting. But he told me that few months ago.”
Why it matters

This is not the resident inventing authority. It is another separate person recording the same basic social fact: people understood him as building authority. Either he had authority, or the building allowed an unauthorised person to repeatedly appear as authority. Both versions are a serious authority problem.

SUPPORTING AUTHORITY RECORDC
ADMINISTRATION INBOX / UNPROMPTED STATEMENT

Another person volunteered that he “reads all the emails.”

WHAT THIS DOCUMENT SHOWS

A different person, unprompted, states that the “unaffiliated” actor reads the administration emails and “shouldn’t.”

Email-access paradoxSeparate personUnprompted

The resident asked for the email address to the Złota board. Without being asked whether the actor read the administration inbox, a separate person volunteered: “reality is unfortunately he reads them all,” followed by “He shouldn’t” and “So you can mention him in your email.”

This is the same email-access paradox from another direction. The actor himself commented on the resident’s private emails. A separate person later volunteered that he reads the administration emails. If this was false gossip, why was this authority perception circulating at all? If it was true, the “unaffiliated” story becomes worse.
Chat screenshot asking for Złota board email; other person says the actor reads all emails and they do not think there is an official email
The resident asks for the board email. The other person volunteers that the actor reads all emails.
Chat screenshot where separate person says reality is unfortunately he reads them all, he should not, and the resident can mention him in email
The other person adds: “He shouldn’t” and “So you can mention him in your email.” Private contact detail redacted.
Why it matters

The issue is no longer one private message or one resident’s interpretation. Multiple separate records point to the same authority problem: people understood him as inside the building’s authority and information flow while the administration later tried to describe him as outside it.

DOCUMENTED RECORD08
PRIVATE EMAIL-KNOWLEDGE PARADOX

“Writing fucking email with chat gpt…”

WHAT THIS DOCUMENT SHOWS

The person described as unaffiliated gave stylistic feedback on the resident’s administrative emails: “writing fucking email with chat gpt.” The screenshot is the point: an allegedly unaffiliated person was commenting on the style of private administrative correspondence.

Record 08Email-access paradoxUnaffiliated representative

The person described as unaffiliated representative gave stylistic feedback on the resident’s emails: “writing fucking email with chat gpt.”

Redacted WhatsApp screenshot showing unaffiliated representative commenting on emails and ChatGPT
The paradox

A person cannot describe Mona Lisa’s facial expression without seeing the painting. He either read the emails, received them, or was briefed. Each option requires an explanation of the data path.

DISABILITY-CODED HARASSMENT / ACCESSIBILITY TOOL MOCKERY

They mocked the disabled resident’s executive-function accommodation tool.

Before the formal GDPR Article 15 request, the resident had already raised CCTV, access, safety and preservation questions. The response from the “Unaffiliated Representative” was not a technical answer. It was cognitive-status mockery: “writing fucking email with chat gpt… makes u look idiot in front of others.”

That matters because ChatGPT was being used as an executive-function accommodation tool by a disabled / neurodivergent resident attempting to communicate precisely with an institution that kept refusing precision. Mocking that tool is not harmless banter. It is disability-coded harassment.

The disabled neurodivergent resident used ChatGPT to see through the fog of institutional gaslighting. The administration-side environment used WhatsApp to character-assassinate a disabled person to 120+ neighbours. The tool-user produced an 84-contradiction register, two interactive games, and a permanent archive. The disability-accommodation mockers still cannot answer a single yes/no question about electrical safety. The cat spins.

GDPR CHAIN PROBLEM

“Unaffiliated,” yet functionally the most affiliated person in the building?

“Unaffiliated” and “inside the personal-data flow” cannot both remain vague.

If the “Unaffiliated Representative” reviewed CCTV footage, received CCTV-derived information, obtained resident-conduct information, or had knowledge of administrative emails, then the issue is no longer only “authority perception.” It becomes a personal-data processing problem.

As the controller/processor structure invoked in your own legal position, you had to be aware of the personal-data chain. You either disclosed personal data to an unaffiliated person, or you allowed an allegedly unaffiliated person to function inside the personal-data processing chain without explaining his role. Both versions require answers.

Open question: how does this coexist with “unaffiliated,” and where is his Article 28 contract, data-processing agreement, or written authorization?

OPEN QUESTION TO THE ADMINISTRATION — STILL UNRESOLVED.

This question is directly linked to the “ChatGPT bulshits” message. The resident’s precise, structured written safety / security / GDPR questions were not answered; they were converted into a stylistic defect and circulated through the same “unaffiliated” actor.

Only Administration had access to the resident’s administrative emails. The Unaffiliated Foreign Representative did not receive those emails from the resident.

If you claim this unaffiliated individual does not have access to your official inbox, then “ChatGPT bulshits” must have been directly communicated to him from your office.

Either this unaffiliated individual reads your official emails directly, or stylistic assessments of those emails are being directly conveyed to him by Admus / Housing Community representatives. There is no third clean option.

This is consistent with information spontaneously volunteered by Złota 44 stakeholders: that he “reads all the emails,” that he “shouldn’t,” and that residents understood him as holding building authority. These statements were not extracted, suggested or prompted. They were offered without being asked.

If the Administration wants to claim “anxiety among residents,” then it should identify the actual source of that anxiety: an allegedly unaffiliated individual repeatedly perceived as building authority, linked to internal information, and never meaningfully corrected by the institution that now claims he had nothing to do with it.

Open question linked to “ChatGPT bulshits”: does Złota 44 expect residents to intentionally pre-emptively downplay linguistic accuracy, logical structure or chain-of-reasoning to be taken seriously when reporting obvious safety, security and personal-data violations?

If no answer is given, then you clearly assert that residents should lower their IQ when communicating with you.

STILL UNRESOLVED — If you treated him as inside the CCTV/email information flow, why was he later described as unaffiliated, and where is the Article 28 authorization?

DOCUMENTED RECORD09
INTERNAL PRESSURE / ADMIN-FEEDBACK ROUTING

“I’m in the middle and from both sides I feel a quite pressure.”

WHAT THIS DOCUMENT SHOWS

The “unaffiliated” representative saying he was in the middle, felt pressure from both sides, and was relaying Administration’s position based on documents and technician reports.

Record 09Pressure routingAdministration feedbackUnaffiliated representative

The same person says he recommended the resident to the owner and apartment, is now “in the middle,” feels pressure “from both sides,” and then relays Administration’s position: based on documents and technicians’ reports, they “don’t need more to prove.”

Redacted WhatsApp screenshot showing unaffiliated representative saying he is in the middle, feels pressure from both sides, and relays administration feedback based on documents and technicians reports
Why it matters

If he was truly unaffiliated, why was he relaying Administration’s technical-evidence position to the disabled resident? Why is an allegedly unaffiliated representative positioned between the resident, the owner, the apartment, the documents, the technician reports and Administration’s “we don’t need more to prove” stance?

DOCUMENTED RECORD10
PUBLIC-FACING ACCOUNT / STORY VIEW

The “official” Instagram watched the resident’s private stories while questions remained unanswered.

WHAT THIS DOCUMENT SHOWS

The same laminated sign outside the administration office presented both Instagram and WhatsApp as official. The “official” Instagram account then watched the resident’s private stories while the administration claimed limited capacity for the questions.

Record 10Public visibilityOfficial account context

The laminated sign outside the administration office presented the Złota 44 Instagram and the resident WhatsApp group as official. The story-view record shows the official Instagram context viewing the resident’s personal Instagram material almost immediately after posting, while the administration used “lack of organizational and technical capacity” as the stated reason not to answer the resident’s documented questions.

Story view screenshot showing public-facing Złota 44 official context and documented timeline
THE CAPACITY QUESTION

Question: how does silently following the resident’s personal Instagram constitute a good use of limited “organizational and technical capacity,” while answering the 150+ direct questions in the unanswered-question register does not?

If they had capacity to watch, they had capacity to clarify. They chose monitoring over answering.

The capacity question

How does silently following the resident’s personal Instagram constitute a good use of “organizational and technical capacity,” while answering the maintained unanswered-question register does not?

STILL UNRESOLVED. If the official account had time to monitor the resident’s personal Instagram activity, why did the administration not have time to answer even one of the direct safety, CCTV, GDPR, authority, insurance or correction questions?
CHAPTER 04GDPR, INSURANCE AND LEGAL PRIORITIES
What happened · how the resident documented it

They blocked accountability, then weaponized the legal system against the resident.

The Article 15 request supplied exact dates, exact data categories and a narrowed fallback. They refused it. Then they produced legal-office timing contradictions, a self-issued insurance acquittal and a 30-day legal restriction over two free bottles of mineral water.

POST-TENANCY CONTACT / DATA-REMOVAL PARADOX

Schrödinger’s OIIA Cat — The Personal Data Paradox

ACTUAL EMAIL SCREENSHOT · MARCH 19, 2026 · OPEN FULL SIZEOPEN FULL SIZE ↗
March 19, 2026 email thread: Administration says the resident’s contact details were removed; resident replies, So how did you contact me now
ACTUAL EMAIL SCREENSHOT · APRIL 16, 2026 · OPEN FULL SIZEOPEN FULL SIZE ↗
April 16, 2026 email: Housing Community finds no grounds for conducting further correspondence

On March 19, 2026, the Administration wrote that the resident’s contact details had been removed from the contact database.

The resident — whose profile picture is OIIA Cat, visible in the email screenshots — replied eleven minutes later:

“So how did you contact me now?”

On April 16, 2026 — nearly one month later — the Administration responded that the Housing Community found no grounds for conducting further correspondence.

They used his contact details to inform him that his contact details had been removed. When asked how this was possible, they declared the matter closed.

Schrödinger’s personal-data paradox: the OIIA Cat contact info both exists and doesn’t exist at the same time. The Administration is simultaneously able and unable to contact the resident. The waveform only collapses when someone asks how.
Institutional high-school-girlfriend logic: this is the institutional equivalent of your high-school girlfriend messaging you “I’ve blocked you!!!” on the platform she just blocked you on. Needing to let you know she’s “done with you” so badly that it overrides all logic. Needing to have the last word so desperately she unblocks you to deliver it.
Fluffy-pink logic box“I’ve blocked you. This is me telling you I’ve blocked you. On the platform I blocked you. Which you can see because I haven’t blocked you. But I have. I’m telling you right now. That I’ve blocked you. Don’t reply to this. You can’t anyway. Because you’re blocked. Which is why I’m messaging you. To tell you.”

The emails are preserved. The timestamps are preserved. The OIIA Cat is still alive. The question hangs forever.

How did you contact him if his contact details were removed?
STILL UNRESOLVED.
ACCESS-CONTROL RECORD / MANUAL CHANGES / MISSING LOGS

Access restrictions, manual changes and missing logs.

The Administration later stated that system errors had been ruled out. If system errors were ruled out, then the access restrictions were not random failures. They were manually applied or manually maintained.

The same office that could request the card number, check the card, refresh access, restore access and verify system status later refused to provide the relevant ACS / access-control logs in the GDPR Art. 15 process.

1

July 14–15, 2025 — card number requested. Card checked. Access refreshed to rule out system issues.

Same timing as the “Dear Neighbours” character-assassination message.

The access restrictions coincided with the “Dear Neighbours” smear / character-assassination message.

ACTUAL WHATSAPP SCREENSHOT · OPEN FULL SIZEOPEN FULL SIZE ↗
WhatsApp screenshots showing card number request, card check and access refresh to rule out system issues
The administration asks for the card number, checks the card and writes that access was refreshed “to rule out any system issues.” If system errors were ruled out, the restriction requires a manual explanation.
2

January 6 — access to the 8th floor added back. No explanation given for the original removal.

No explanation was given.

The continued avoidance of explaining the timing immediately after the GDPR Art. 15 deadline failure / UODO escalation is concerning.

ACTUAL WHATSAPP SCREENSHOT · OPEN FULL SIZEOPEN FULL SIZE ↗
WhatsApp screenshot showing 8th floor access added back without explanation for original removal
Access is added back. The resident asks why it was removed. No explanation is provided.
3

January 7 — compensation requested for days of wrongful access denial.

No explanation was given.

The continued avoidance of explaining the timing immediately after the GDPR Art. 15 deadline failure / UODO escalation is concerning.

ACTUAL WHATSAPP SCREENSHOT · READ-RECEIPT POINT MARKED · OPEN FULL SIZEOPEN FULL SIZE ↗
WhatsApp screenshot showing compensation request for days of wrongful access denial, with read receipt area marked
The resident requests compensation for the days he was denied access to a service he paid for. The read-receipt area is marked because the next open question is why read receipts disappeared immediately after this compensation request.

STILL UNRESOLVED

  • STILL UNRESOLVED — Why did the access restrictions happen at the same time as the “Dear Neighbours” character-assassination message?
  • STILL UNRESOLVED — Why has the Administration avoided explaining the timing of these bans immediately after the GDPR Art. 15 deadline failure / UODO escalation?
  • STILL UNRESOLVED — If system errors were ruled out, who manually applied or maintained the access bans?
  • STILL UNRESOLVED — How did the common-area ban happen at the same time as the leak of false sensitive personal data in the official WhatsApp group?
  • STILL UNRESOLVED — If access could be checked, refreshed, restored and verified, why were the ACS / access-control logs later withheld in the GDPR Art. 15 request?
  • STILL UNRESOLVED — Why were WhatsApp read receipts disabled immediately after the financial-compensation request?
  • STILL UNRESOLVED — Why was another ban introduced in December / January, and why was no explanation ever sent after one of the Administration’s employees promised one in front of other staff?
Open question to the Administration: if any of these points require correction, why was no clarification provided during the many earlier opportunities to do so?
4

October 9, 2025 — common-area access discovered disabled again. Formal confirmation request + GDPR access request sent.

Restriction first. Explanation missing.

The resident asked for the effective date/time, authority, rule, decision-maker, notice, immediate restoration, access-control data and CCTV.

ACTUAL EMAIL SCREENSHOT · OPEN FULL SIZEOPEN FULL SIZE ↗
Email screenshot titled Common Area Access requesting confirmation and GDPR access request
The resident requested immediate confirmation of the restriction, the exact authority / rule behind it, proof of notice, restoration of access and GDPR access to related access-control data and CCTV. No clear explanation was provided.

STILL UNRESOLVED

  • STILL UNRESOLVED — Explain how this October access restriction coincides with the “unaffiliated representative” being one of the only few people present in the common area when the resident was speaking with his neighbour, who said this same individual had presented himself as “head of security.”
  • STILL UNRESOLVED — Explain how this perceived authority-figure appears within the context of every unexplained access restriction applied by the Administration’s office.
  • STILL UNRESOLVED — If the Administration claims this is pure coincidence, it must also accept that future probability calculations will be placed next to that statement.
GDPR ESCALATION / URGENT INSPECTION / BASIC ASSET MANAGEMENT

Disabled resident attempts to educate Admus on basic asset-management principles.

The inspection appeared less than 24 hours after the GDPR deadline was escalated. The resident put the timing, probability, insurance risk and basic asset-management problem in writing. The Administration still proceeded as if “urgent” meant adjectives, not execution.

THE INSURANCE LESSON

The disabled resident attempts to educate the “Able” administration on how to not fuck up their insurance coverage.

ACTUAL WRITTEN RECORD · TAP TO OPEN FULL SIZEOPEN FULL SIZE
Written note explaining that the inspection appeared less than 24 hours after GDPR escalation, calculating 0.27 percent timing probability, and describing asset management concerns
The resident calculated the timing anomaly and described the inspection timing as non-adherence to basic asset-management principles.
THE TIMING P = 0.27%

Under a neutral baseline, an inspection appearing less than 24 hours after GDPR escalation is approximately 1 day out of 365. The resident even used a far more generous — 12× wider — 30-day window: 3.33%.

THE POINT

A tenant should not have to remind a prestige-building administration that sudden “insurance” language, after a GDPR deadline failure, creates second-order consequences for reputation, trust, insurance and asset value.

THE REVERSAL

The disabled, neurologically vulnerable resident was not only asking safety questions. He was explaining basic asset management to the administration while they were missing deadlines, avoiding answers and creating new contradictions.

Open question: why did a resident have to explain probability, timing, insurance risk and second-order asset-management effects to the administration of one of Poland’s most prestigious residential buildings?
THE KEBABGATE FILES / CCTV CAPACITY TEST

The mysteriously missing 20 PLN kebab was solved in 10 hours.

A separate resident at Złota 44 made a mistake. He took a kebab that was not his. Value: approximately 20 PLN. The neighbour’s own words describe what happened next: security footage reviewed, location triangulated, resident identified, and 20 PLN collected.

ACTUAL MESSAGE SCREENSHOT · OPEN FULL SIZEOPEN FULL SIZE ↗
Separate resident message saying the administration triangulated his location and collected 20 PLN after a mistakenly taken kebab
The neighbour’s own words: “They triangulated my location and came to collect 20 zloty the next day” and “It took a total of 10 hours to review and triangulate my location and collect the 20zł of the mistakenly taken kebab.”
THE CAPACITY QUESTION

They had capacity for a kebab. They claimed no capacity for GDPR.

The legal letter says they lacked the “organizational and technical capacity” to produce access logs, CCTV data and the Article 15 material requested by the resident.

Yet a 20 PLN kebab apparently triggered CCTV review, location triangulation, resident identification, rapid deployment and collection of funds.

If you can triangulate a 20 PLN kebab in 10 hours, why can’t you produce access logs under a lawful GDPR request?

THE TWO PATHSThere is no third door.
If the legal letter was trueIf the kebab response was true
They cannot track access, review footage, identify residents, or produce the requested records. The kebab recovery should have been impossible.They have surveillance, tracking, identification and deployment capability. The Article 15 refusal was not a capacity shortage.
THE PRIORITY STRUCTUREWhat receives resources, and what receives “matter resolved.”
ItemValueResponse timeAction / avoidance
Missing kebab20 PLN10 hoursCCTV review, location triangulation, personnel deployment, fund collection
Electrical safety verification for a neurologically vulnerable residentMedical necessityNever answered“No further answers will be provided”
GDPR Article 15 requestLegal rightDeadline expired“Lack of organizational and technical capacity”
Character-assassination withdrawalReputational / disability-coded credibility attackNever withdrawn“Matter resolved”
This is not a capacity problem. This is a priority structure.

The Administration has organizational and technical capacity for kebabs. It claims to lack it for legal compliance, safety verification and correction of false statements.

STILL UNRESOLVED — explain why a 20 PLN kebab could be triangulated in 10 hours while access logs, CCTV records and Article 15 data remained unanswered.

DOCUMENTED RECORD11
ARTICLE 15 REQUEST / NARROWED FALLBACK

They called a precise request “broad” and ignored its built-in fallback

WHAT THIS DOCUMENT SHOWS

The 9 October Article 15 request showing defined dates, a one-hour CCTV window, named data categories and a narrowed fallback.

Record 11GDPR Article 15 scopeNarrowed fallback included

The later letter called the request broadly formulated. The 9 October email shows dates, a one-hour CCTV window, named data categories, requested formats, preservation language and a fallback if the full request was considered too heavy.

Redacted 9 October GDPR Article 15 access request showing defined time windows, requested logs/CCTV, and fallback disclosure path
Why it matters

The fallback was explicit: provide the cardholder audit trail, provide the last 30 days of access events, and schedule the rest. They did none of it.

DOCUMENTED RECORD12
GDPR LEGAL POSITION / EDITED ADMUS TEXT / DATE PROBLEM

They Edited ADMUS Out of Their Own GDPR Legal Position. The Disabled Resident Caught It Instantly.

WHAT THIS DOCUMENT SHOWS

The dates do not fit. The February text does not match the October legal position. The exact sentence naming ADMUS is the part that disappeared. The same record also exposes the professional-management problem: ADMUS stayed operational, then disappeared from the legal wording when responsibility mattered.

Record 12Legal position edited23 / 24 / 26 OctoberADMUS removedStill unresolved

They pretended to paste the legal position. ADMUS is the exact part missing.

VISIBLE RECORD · FEBRUARY 16 · THE CAT SEES EVERYTHING
Resident email dated February 16 catching identity and liability distancing: ADMUS is not used once and everything is framed as Housing Community only
VISIBLE RECORD · DATE PROBLEM + MISSING ADMUS
Composite screenshot showing February 16 administration email, the claimed October 23 reply issue, the October 26 legal letter date, and the missing ADMUS fragment

ADMUS was named. The October legal text named the Housing Community and “the company providing administrative services,” namely ADMUS sp. z o.o.

ADMUS disappeared. The February 16 email presented the “fragment relating to this” without that ADMUS sentence.

The dates still do not fit. They claimed October 23 receipt. On October 24, they said the law office was still processing. The letter shown is dated October 26.

The capacity problem remains. They identify who controls the data and who operates the system. Then they use “lack of capacity” as the stated reason not to produce the data.

THE PROFESSIONAL-MANAGEMENT PROBLEM

Why are you throwing “the Housing Community” — the client you’re supposed to represent — under the bus after creating 84 documented contradictions and 150+ unresolved questions?

You are supposed to be the professional management company.

And your response is to quietly delete yourselves from the legal documentation and leave the Housing Community to clean it up?

Why wasn’t “Housing Community” conveniently fragmented out instead of ADMUS?

THE “GOOD NAME” INCENTIVE GRADIENT

“If ADMUS genuinely believed its name was “good,” why remove it from the legal writing when authority and credibility would logically be most useful? Why remove a social-proof advantage when you need it the most?”

“If your name was “good,” then ADMUS and Director [REDACTED] should appear more often as the contradictions and stakes increased — not less.”

Your incentive gradient suggests that you do not actually consider your name “good” to begin with.

THE DIRECTOR DISAPPEARANCE PROBLEM

At the beginning, the resident was dealing with Director [REDACTED].

Director [REDACTED] himself asserted his “zero irregularities / safety requirements” position, even though it was logically incoherent.
Director [REDACTED] answered the creepy proxy-weirdness with: “Anyone can claim to be whoever they want to be.”
Then, as the contradictions increased, Director [REDACTED] became less visible.

Director when reassuring. No Director when accountable.

A CHRISTIAN-COUNTRY LEADERSHIP PROBLEM

This leadership style sits even stranger in a country whose public identity is deeply tied to Christianity.

In Genesis, Adam hiding behind Eve is not recorded as leadership. It is recorded as shame.

OIIA CatOIIA Cat disapproves of the institutionalisation of Adam’s Shame.

The pattern here is hard to miss: a Director avoided direct accountability while routing the interaction through two young Polish female proxies.

This is not masculine leadership. It is liability-shielding with women placed in front.

Inside a building marketed as a post-Communist freedom monument to ojczyzna, while an “Unaffiliated Foreign Representative” roleplayed proxy-authority, the Director’s model of responsibility was apparently:

let the young women absorb the emotional awkwardness we created.

Zero opportunities have been taken to correct the record.

Maybe because there were no 18–22-year-old women nearby to press “send,” translate the accountability, or remove the next inconvenient name from the legal fragment.

I shouldn’t be telling you this, but...

Their philosophy is clear.

If we fuck something up — blame the nearest young woman in sight.

Message screenshot describing Administration shifting blame onto staff.
THE WARNING THEY IGNORED

He told them exactly what would happen — and then they did it anyway. 8 months later.

On 6 May 2025, the resident warned Administration that ongoing avoidance and ambiguity would amplify shared liability, create internal tension, suspicion and confusion, and eventually make internal inconsistencies externally visible.

May 6 email warning that avoidance and ambiguity amplify shared liability and create internal tension, suspicion and confusion.
May 6: the resident warns that ambiguity creates internal tension, suspicion and confusion.
May 6 email warning that internal inconsistencies and unresolved tension inevitably become externally visible.
May 6: the resident warns that internal inconsistencies inevitably become externally visible.
MAY 6 WARNINGAmbiguity creates shared-liability fog.

If responsibility is kept vague, the internal failure mode eventually becomes visible. In an environment where everyone tries to avoid responsibility, betrayals are structurally inevitable.

FEBRUARY 16 RESULTHousing Community stayed. ADMUS disappeared.

The October legal position named both. The February “fragment” kept the Housing Community visible and removed the ADMUS sentence.

This is the same pattern. Not “similar.” The same. The resident warned them that responsibility ambiguity would turn into visible internal inconsistency. Eight months later, the responsibility-chain inconsistency was sitting in their own copied legal text.

The pattern repeats itself. The cat spins.

The resident did not need internal access to see the fault line. He described the fault line before it surfaced.

The disabled resident warned the Administration about the self-destructive consequences of its own behaviour, while attempting to give them face-saving exits — despite already being character-assassinated by their Unaffiliated Foreign Representative for proxy-authority.

The Administration refused those exits, repeated the same behaviours, and then left the proof in 84+ contradictions.

Still a better love story than Twilight.

He told them exactly what would happen — and then they did it anyway. 8 months later.
THE PROXY BLAME-CHAIN

First they threw their proxy under the bus. Later they threw their client under the bus.

Administration shifts blame onto its proxy, the Unaffiliated Foreign Representative, when the disabled, neurologically vulnerable resident raises safety concerns.

After the proxy’s emotional outburst, the disabled resident soothes his crippling anxiety.

Ironically, the proxy character-assassinated him as “psych/drug issues” one week later.

Just another day at Złota 44. Not weird at all.
April 25 WhatsApp message where the resident tells the Unaffiliated Representative that someone else’s self-inflicted negativity should not be projected onto him.
April 25: the resident identifies projection and ambiguity before the character assassination.
April 25 WhatsApp message saying blame placed on the Unaffiliated Representative may reflect the Administration’s reluctance to communicate transparently or take accountability.
April 25: the resident tells him the “blame” may reflect their own reluctance to communicate transparently.
April 25 WhatsApp message where the Unaffiliated Representative says he personally checked with security, owners are blaming him, and then mocks emails written with ChatGPT.
Same sequence: he “personally checked with security,” says owners are blaming him, then mocks the disabled resident’s executive-function accommodation tool.
Only Administration had the emails. If the Unaffiliated Foreign Representative knew the resident’s “ChatGPT bulshits” emails, the question is not style. The question is who inside the Administration gave him the content, summary or assessment of those private administrative emails.
APRILthey threw their disposable proxy under the bus

Unresolved internal tension got placed on the Unaffiliated Foreign Representative. It became externally visible as character assassination. Later disowned as “Unaffiliated.”

FEBRUARYThey threw their client under the bus.

Rinse-and-repeat in February. Housing Community stayed visible. ADMUS disappeared.

Zero irregularities found.

The resident tells them he sees the pattern, and warns them it self-destructs their reputation.

They never calibrate their strategy.

THE EXACT PART THEY LEFT OUT“and the company providing administrative services for part of the common property, namely ADMUS sp. z o.o., based in Warsaw.”

STILL UNRESOLVED — Why was ADMUS removed from the processing structure between October 26 and February 16?

STILL UNRESOLVED — Who authorized the removal of ADMUS from the legal position?

STILL UNRESOLVED — If the February 16 email was a “copy-paste” of the legal position, why does the text not match?

STILL UNRESOLVED — Why is “and the company providing administrative services for part of the common property, namely ADMUS sp. z o.o., based in Warsaw.” the exact fragment missing?

STILL UNRESOLVED — If the reply was allegedly received on October 23, why did the Administration write on October 24 that the law office was still processing it, and why is the legal letter dated October 26?

STILL UNRESOLVED — Did the law office approve the edited version, or did the Administration edit a legal position without authorization?

STILL UNRESOLVED — Why was ADMUS removed instead of “Housing Community,” if the February 16 text was supposed to be a faithful copy-paste of the legal position?

STILL UNRESOLVED — If ADMUS considered its name a credibility asset, why did ADMUS disappear from the legal wording precisely when authority, credibility and responsibility mattered most?

They acted through ADMUS operationally. Then, when liability and GDPR responsibility were questioned, ADMUS disappeared linguistically. If the name was “good,” it should have appeared more as the stakes increased — not less.
DOCUMENTED RECORD13
LEGAL CORRESPONDENCE

They weaponized a law office over two FREE bottles of mineral water.

WHAT THIS DOCUMENT SHOWS

The legal-office sentence weaponizing a 30-day restriction over two free bottles of mineral water.

Record 13Legal correspondence
“the removal of two bottles of mineral water from the club area.”
Legal letter excerpt stating that the restriction reason was removal of two bottles of mineral water
Verbatim excerpt from the forwarded legal correspondence.
CHAPTER 05THE INSURER REQUEST
Liability insurer request / response

Asked for the insurer. Answered with their own acquittal.

Request ≠ responseThe resident requested the insurer’s name, policy number, coverage scope and claims contact. The response supplied none of them.

The actual request and the actual response are shown below. The request asks for four policy details. The response supplies none of them and replaces disclosure with the Housing Community’s own liability conclusion.

01 / The request — 21 November 2025Identify the insurer and the policy.
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Redacted email requesting insurer name, policy number, scope of coverage and claims-contact details
Four specific policy details were requested, together with related safety-compliance documentation.
FIVE DAYS LATERTHE QUESTION CHANGES INSIDE THE RESPONSE
02 / The response — 26 November 2025“No damage … caused by the Housing Community.”
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Redacted Złota 44 Admus reply refusing the policy number because no damage was found that was caused by the Housing Community
The response provides a liability conclusion instead of the requested insurer information.
The response, translated into plain English
“We investigated ourselves, decided we’re innocent, and therefore you cannot have the policy number.”
THE WORDING PROBLEM — STILL UNRESOLVED

They did not write “no damage exists.” They wrote that no damage was found that was caused by them.

Their sentence does not clearly rule out the existence of damage. It only claims that no damage was found that was caused by the Housing Community.

If they meant “no damage exists,” why not say that?

If they used language that does not explicitly rule out damage, how can that sentence become “therefore there is no basis to provide the policy number”?

And why did they start investigating “damage” before the resident had even identified a specific damage claim? If the resident had not yet stated the hypothetical damage, what exactly did they investigate, using which measurements, and against which scope?

AskedWho is the insurer?
AnsweredWe are not responsible.
WithheldInsurer name. Policy number. Coverage. Claims contact.
CHAPTER 06THE “URGENT” INSPECTION
Contemporaneous written record

After failing Article 15, they suddenly called an inspection urgent. Then they left it unresolved until after the disabled resident moved out.

Same dated threadRepeated confirmations appear immediately above the administration’s statement.
Email inbox screenshots showing the resident chasing the inspection and reminding Złota 44 after delayed urgent-inspection correspondence.
Additional contemporaneous recordReminder / follow-up screenshots showing the resident chasing the allegedly urgent inspection instead of avoiding it.
Email thread list showing several resident messages on 7 and 9 February followed by Złota 44 writing “as there was no confirmation” on 9 February.
Same thread contradictionMultiple resident emails appear before the Administration’s 9 February “as there was no confirmation” message.

Any rational person would expect communication to become more transparent and documented after a GDPR Article 15 deadline failure — not less. They did the opposite: withheld identifiers, routed notices through concierge and post-it notes, left unresolved until after move-out, missed their own deadline, and wrote “no confirmation from you” above repeated confirmations.

DOCUMENTED RECORD14
9 FEBRUARY EMAIL THREAD / THEY MISS THEIR OWN DEADLINE

They miss their own deadline, then attempt last-second narrative damage control.

WHAT THIS DOCUMENT SHOWS

The 9 February email thread where they miss their own deadline and then write “no confirmation from you.”

Record 14Inspection schedulingNo-confirmation contradiction

The administration proposed 9 February at 12:00. The resident confirmed availability repeatedly, asked for the missing company / technician / insurance identifiers, reminded them again, and stayed available. They miss their own deadline. At 13:25, they wrote: “as there was no confirmation from you… the inspection did not take place.”

9 FEBRUARY 2026They miss their own deadline.Then: “no confirmation from you.”
Redacted Gmail thread showing multiple written confirmations and reminders before Złota 44 wrote that there was no confirmation from the resident
9 February 2026 — they miss their own deadline, then write “no confirmation from you” beneath repeated written confirmations and reminders. Personal identifiers redacted.
What happened

They made the resident reserve the day, stay available, request the company / technician / insurance details, and keep reminding them to confirm. They miss their own deadline, provide none of the required identifiers, and then write the failure onto the resident’s side of the ledger.

Plain reading

They miss their own deadline before attempting last-second narrative damage control.

Administration position“The tenant refused access.”

Written record: “yes, I will provide access,” followed by requests for identity, scope and liability details.

Administration position“The tenant did not confirm.”

Written record: 9 February availability and repeated prior scheduling attempts before they miss their own deadline.

Later narrative“The inspection was urgent and clear.”

The emails record delay, post-it routing, unanswered reminders and repeated scope changes.

CHAPTER 07THE CORRECTION RECORD
Correction record

They received exact questions, proof requests and a REFUSE option. They answered with “matter resolved.”

The written forkIdentify the author. Correct the health / substance statement. Produce transmission proof. Answer each question. Or write “REFUSE.”

The screenshot on the left shows one correction email. The cards on the right pull out the correction route from that email set and from the written question register shown immediately below, so each quote sits inside the correct record context.

Redacted March 3, 2026 email offering Złota 44 Administration direct yes-no correction choices and documenting unresolved contradictions
3 March 2026 — correction opportunity and contradiction noticeNames and private addresses redacted
Author / character-assassination correction fork — source: question register below
“If you refuse to identify the author and refuse to correct the statement, confirm that you are choosing to leave false health/substance allegations uncorrected on record — yes or no.”

Source note: the exact health/substance correction fork is visible in the written question-register screenshot in the next section. It is surfaced here because it is the central correction path they were given.

Explicit refusal option
“Please answer each yes/no question directly. If you refuse to answer any specific question, state ‘REFUSE’ explicitly next to it.”
Advance notice of publication
“If my previous inquiries remain unresolved, I will publish an in-depth, evidence-only full timeline — screenshots and dates — including a structured map of contradictions and logical inconsistencies.”
24 February deadline
“If you do not respond by 12pm 24 Feb, I will treat your silence as maintaining your last written position(s) without correction.”
CHAPTER 08THE WRITTEN QUESTION REGISTER
One email / contradiction sets 0–11

The exact questions they received. Twelve contradiction sets. They answered none of them point by point.

One maintained recordIdentity. Official WhatsApp. CCTV retention. They miss their own deadline. Controller / processor confusion. “No confirmation.” Insurance. CCTV access. Legal dates. The drugs / mental-health character assassination.

The email converts their own statements into numbered yes/no questions, proof requests and correction demands. It tells them to answer directly or write REFUSE. They supplied no point-by-point answer.

THE DOCUMENTFour consecutive screenshots of the actual email as sent. Read 01 → 04. The screenshots remain the primary record; private identities and the apartment number are redacted.
0Identity / liability distancing
1Official WhatsApp signage
2CCTV retention + “matter resolved”
3They miss their own deadline
4“Email only” vs post-it / concierge
5Controller / processor confusion
6“Attempted contact” / “no confirmation”
7Self-adjudication / insurer withheld
8CCTV viewing by an “unaffiliated” actor
9Front-desk confirmation of non-response
1023 October legal time-travel
11False drugs / mental-health character assassination
Page 01 of 04Questions 0–2Identity / official channel / retention
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Redacted first screenshot of the numbered contradiction email covering identity, official WhatsApp signage and CCTV retention
The email opens by defining a valid answer, then begins the numbered question register.
Page 02 of 04Questions 3–6They miss their own deadline / channel drift / GDPR roles / no confirmation
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Second screenshot of the numbered contradiction email covering the missed deadline, communication channels, GDPR roles and no-confirmation language
The inspection, channel and GDPR contradictions are placed side by side.
Page 03 of 04Questions 7–9Self-adjudication / CCTV authority / systemic non-response
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Redacted third screenshot of the numbered contradiction email covering the insurer response, CCTV access and front-desk non-response
This page contains the “we investigated ourselves” insurer logic in the resident’s original email.
Page 04 of 04Questions 10–11Legal dates / drugs and mental-health character assassination
ACTUAL EMAIL SCREENSHOTOPEN FULL SIZE ↗
Fourth screenshot of the numbered contradiction email covering the claimed 23 October law-office reply and the health-substance allegation
The email ends with the legal-date contradiction and the direct demand to identify and correct the drugs / mental-health character assassination.
The recordThis is the literal email record they received: twelve numbered contradiction sets, ending with a direct-answer-or-REFUSE instruction.
CHAPTER 09THE GOOD NAME PROBLEM
Article 23 / “good name” / documented reality

They Protected the Name. Not the Standard.

They keep making references to “their good name.”

A good name is not a phrase in a legal letter. A good name is what remains after competent safety verification, transparent data governance, traceable authority, accurate recordkeeping, timely inspection execution, correction of false statements, and basic asset-management competence.

The record shows something else.

THE GOOD NAME PROBLEM IS ALSO THE DISABILITY PROBLEM

They sent cease-and-desist to a disabled resident for documenting disability-discrimination evidence.

The “good name” they invoked is the name that enabled a character assassination against a neurologically vulnerable resident.

A disabled resident has given you 30+ respectful opportunities to correct the record. You have used none of them. Every day of silence leaves the disability-discrimination evidence standing.

THEIR OWN LEGAL LETTEROPEN FULL SIZE ↗
Legal letter excerpt invoking good name, competence, honesty, diligence, reliability, anxiety among residents, Article 23 and content described as mocking
The legal letter invokes “good name,” competence, honesty, diligence, reliability, trust, “anxiety among residents,” Article 23 / 24 and content it describes as “of a mocking nature.”
01

Their “Good Name” Is Not as Good as They Believe

They described the resident’s public statements as being “of a mocking nature” and damaging to their good name.

The resident was reproducing their own statements word for word:

“No irregularities found.”“Mouse.”“Chair.”“Carpet.”“Changing clothes.”“Wiping your hands with a towel.”“Anyone can claim to be whoever they want to be.”“Lack of organizational and technical capacity.”“Two bottles of mineral water.”“No confirmation from you.”“Matter resolved.”

If repeating their exact words damages their good name, the damage was already inside the words. They authored the material. The resident preserved it. Calling the repetition “mocking” is admitting that their own statements are humiliating when placed beside dates, screenshots, and what happened next.

A disabled resident, in a “prestige, luxury” building, cannot be expected to take responsibility for the building Directors / Administration’s own emotional reactions. If they subjectively interpret their own security/GDPR-statements as “mocking”, perhaps it’s time for some introspection.

Their self-perception is contradicted by their own operational environment.

THE CONCIERGE WROTE — ON TEXT, SCREENSHOT PRESERVED
“I have to run to the administration office anyway because they’re ignoring other residents too.”
THE STATEMENT AS PLACED IN THE WRITTEN QUESTION REGISTEROPEN FULL SIZE ↗
Written question register recording the concierge statement that other residents were also being ignored
The original concierge text screenshot is preserved. This crop shows the statement placed into the formal written question register sent to the administration, with a direct opportunity to deny it.

Other residents responded by describing their own problems. The reputational issue did not begin because one person repeated their statements. Their own front desk was already recording that other residents were being ignored.

02

If “Good Name” Mattered, Correction Was the Obvious Route

The administration was repeatedly given direct opportunities (on over 30 separate occasions) to protect its reputation through the one method that actually works: correct the record.

A disabled resident has given you 30+ respectful opportunities to correct the record. You have used none of them. Every day of silence leaves the disability-discrimination evidence standing.

They could have explained the 18–22 Ω readings, identified the applicable standard, corrected inaccurate dates, produced transmission proof, answered whether the apartment door was visible on CCTV, disclosed the CCTV retention period, identified who authorized the “unaffiliated representative,” explained his access to internal information, corrected the health/substance character assassination, corrected the false “no confirmation” statement, identified the insurer, and completed the allegedly urgent inspection on time.

Instead, they wrote:

“Matter resolved.”

So their theory of reputation becomes: we will not correct the record, we will not answer the contradictions, we will not produce the receipts — but documenting our refusal damages our good name.

No.

A reputation unsupported by receipts is branding.

03

Their Institutional “Good Name” Received Lawyers. The Resident’s Name Received Character Assassination.

A person presented himself as “Management board member of Z44.” He used the Złota 44 name as authority. He circulated the health/substance character assassination to the resident group advertised as the official WhatsApp group. He used court-threat language. He banned the resident from the same official WhatsApp channel. His conduct created GDPR questions. He inserted himself into the police interaction.

The administration later called him private and unaffiliated.

What did the Quality Assurance Director do to protect the resident’s name?

No same-channel correction.No withdrawal.No notice to residents.No identified investigation.No identified sanction.No correction of the court-threat language delivered under the Złota 44 name.

A disabled resident paying approximately 300,000 PLN per year was subjected to a public character assassination by someone impersonating authority under the building’s “good name.” The Quality Assurance Director — whose title literally contains the word “quality” — did nothing.

The “good name” they invoked is the name that enabled a character assassination against a neurologically vulnerable resident.

But when the administration’s abstract institutional “good name” was challenged, the legal machinery activated.

And what conduct did they successfully formalize through a law office?

The removal of two free bottles of mineral water.

That is the priority structure.

Their institutional name received lawyers.The resident’s name received character assassination and a ban from the correction channel.

That is not quality assurance. That is selective reputation protection.

04

Their “Good Name” Did Not Protect Polish Integrity

The “good name” argument becomes even worse beside the Polish-integrity record.

The “Unaffiliated Foreign Representative” operating under Złota 44 authority perception disrespected the integrity of the Polish people by attributing a Soviet / communist “replace the person who notices” mechanism directly to the Polish national character itself.

He was not describing a false stereotype created by occupation. He presented the mechanism as Polish people’s present-tense nature. The attacked resident immediately corrected the Unaffiliated Foreign Representative and defended Poland.

The Polish Administration enabled the Unaffiliated Foreign Representative who disrespected Polish integrity. It ignored the disabled, neurologically vulnerable resident who defended it.

Then the record moved exactly where the foreigner said it would: the problem was not fixed; the person noticing the problem was removed, restricted, smeared and isolated.

That is not protection of a good name. That is acting in alignment with the insult against Poland.

They sent legal letters over two bottles of mineral water in the “good name” of a post-Soviet freedom monument — while leaving the resident who defended Polish integrity character-assassinated.

05

Why Is “Good Name” Their Primary Concern?

Why not good safety verification?

Why not good GDPR compliance?

Why not good authority control?

Why not good recordkeeping?

Why not good governance literacy so they do not confuse “processor” and “controller”?

Why not good adjective-consistency and legal linguistic precision, so they do not confuse “authorised” and “certified”?

Why not good and transparent authority structure?

Why not good compliance with basic asset-management principles — such as not delaying an allegedly urgent, insurance-compromising inspection for approximately 83 days, until the disabled resident moved out?

If “good name” carries such high priority, why stop signing the emails with “Director”?

They invoked urgency, insurance, and the safety of residents, employees, and guests.

Then they delayed the inspection. Then they missed their own deadline. Then they wrote “no confirmation from you, so there was no inspection” directly above the resident’s repeated written confirmations.

They used the prestige of the building and the language of authority to demand compliance. When it was time to execute the process they controlled, they missed their own deadline and tried to write their failure onto the resident.

That is poorly performed authority theatre. It is not a good name supported by quality delivery.

06

If “Good Name” Is the Concern, Why Pretend It’s About “Anxiety Among Residents”?

The legal letter says the resident caused “unwarranted anxiety among the building’s residents.”

Let that sit for a second.

Złota 44 markets itself as Warsaw’s most prestigious address. High-net-worth individuals. CEOs. People who presumably handle boardroom pressure, market volatility, and actual high-stakes decisions.

And the Administration’s legal position is that these same people are so psychologically fragile that the Administration facing difficult questions caused those residents crippling anxiety.

There is no version of reality where that actually makes sense.

The record is clear on who was actually anxious: the Administration. The “unaffiliated representative” complained that owners and administration were blaming him. Pressure was cascading through their own office. The Director stopped signing as Director. ADMUS quietly deleted itself from legal documents.

That’s where the anxiety lived. Not in the residents’ apartments. In the Administration’s inbox. In their WhatsApp panic and pocket-dialling to the disabled resident (“Freudian finger-slip”). In their legal-office scramble over two bottles of mineral water.

They felt pressure. They wrote it in the residents’ name.

Unless “the residents” is a new legal term meaning “the Administration’s emotional state,” this is psychological projection dressed up as a legal argument.

Starting to see the pattern yet?

Take something that belongs to you, and put it on someone else.

Unaffiliated Foreign Representative’s Soviet-occupation operational logicProjected onto Polish national character.
Their own office-anxietyProjected onto the residents, cease-and-desist style.
Their own inspection-deadline failurePut onto the disabled resident.
The liabilityPut onto the Housing Community. ADMUS conveniently fragmented out.
The authority problem“Anyone can claim to be whoever they want to be.”

Once seen, it can’t be unseen. The fog is lifting. The cat spins.

07

If “Good Name” Is the Concern, Why Ruin It With Cease-and-Desist Letters Over Two Free Bottles of Mineral Water?

They engaged a law office. They drafted a formal letter. They formalized a 30-day common-area restriction.

Over two free bottles of mineral water.

This is not a side issue. This is the calibration sample for their judgment.

Why should anyone trust the subjective interpretation of someone who actively chose to send cease-and-desist-style letters over bottles of mineral water?

If this is how they assess proportionality, priority, resident conduct, and reputational risk — if two bottles of free water trigger legal machinery while a health/substance character assassination under the building’s name triggers nothing — why should any resident, owner, buyer, investor, or agent trust their interpretation of what “looks bad,” what “damages their good name,” or what supposedly causes “anxiety”?

Is that decision-making fit to represent one of Warsaw’s highest-profile residential assets?

The Water Is Not the Scandal.The Water Is the Receipt.

It records what they considered worthy of legal machinery — and what they did not.

08

“Good Name” Is Being Used to Change the Subject

The factual question is: did they deliver competent safety verification, data governance, authority control, inspection execution, and correction procedures?

Their preferred question is: did the resident damage our good name by publicly describing what we did?

That shift is the whole trick. It moves scrutiny away from their performance and onto the person documenting their performance.

THE INPUTSSafety. Compliance. Transparency. Correction. Traceability. Execution.
THE OUTPUTA good name.

They skipped the inputs and tried to litigate the output.

09

A Good Name Is Not a Self-Issued Certificate

It is what remains after the receipts are shown.

The administration invoked “good name” while refusing the verification, correction, transparency, and execution that would have supported one.

When their own statements were repeated word for word, they called the repetition mocking.

When their own concierge documented that other residents were also being ignored, the problem was already operational.

When a person presenting himself as “Management board member of Z44” circulated a health/substance character assassination under the Złota 44 name, the Quality Assurance Director did not correct it. In fact, his official statement in person was “Anyone can claim to be who they want to be.”

When two free bottles of mineral water were removed, a law office found capacity.

When an allegedly urgent, insurance-compromising inspection required competent execution, they left it unresolved for approximately 83 days, missed their own deadline, blamed the disabled resident, and apparently handled it only after he moved out — if it was ever completed at all.

Good name without receipts is misleading branding. Good reputation with receipts is asset management.

They protected the label and abandoned the standard.

10

Expectation vs Documented Reality

Expectation

A good reputation earned through documented safety, compliance, transparent authority, and competent asset management.

Documented reality

“Good name” invoked against screenshots containing their own statements.

Expectation

A Quality Assurance Director corrects a health/substance character assassination circulated under the building’s name against a resident paying approximately 300,000 PLN per year.

Documented reality

No correction, no withdrawal, and no identified sanction. Legal-office formalization appeared over two free bottles of mineral water.

Expectation

An “urgent,” insurance-compromising inspection is executed immediately and documented precisely.

Documented reality

Approximately 83 days unresolved. Post-it notes through concierge. They miss their own deadline. Then they write “no confirmation from you.” Any later inspection happened only after the disabled resident moved out — if it happened at all.

11

Starting to See the Pattern Yet?

Take something that belongs to you, and put it on someone else.

Unaffiliated foreign representative’s Soviet-occupation operational logic? Project onto Polish national character.

Their own office-anxiety? Project onto the residents, cease & desist style.

Their own inspection deadline failure? Onto the disabled resident.

The liability? Put it on the Housing Community. ADMUS conveniently fragmented out.

The authority problem? “Anyone can claim to be whoever they want to be.”

Once seen, it can’t be unseen. The fog is lifting. The cat spins.

Why should anyone trust their interpretation of “mocking,” “anxiety,” or reputational harm when their own public optics-judgment produced law-office escalation over two free bottles of mineral water?
CHAPTER 10THE CONTRADICTION REGISTER
Logical inconsistency register

84 contradictions in one maintained record.

Position A / Position BEach entry places two maintained positions side by side and identifies the conflict.

Dates, quotations, screenshots and formal positions are placed beside each other. The contradiction is written underneath.

EVERY CONTRADICTION BELOW REMAINS STILL UNRESOLVED. “Matter resolved” did not reconcile the positions. “All questions answered” did not answer them. Every entry remains open unless corrected with a specific document, date, name and explanation.
Eighty-four contradictions across safety, CCTV, GDPR, insurance, authority, legal correspondence, public monitoring, access restrictions, disability-targeting, neurodivergence, technical time-travel logic, the missing ADMUS fragment and the Polish-integrity reversal.
L-62Article 23 / Article 24 legal language vs resident-channel character assassination Projection / Article 23 STILL UNRESOLVED
What the legal letter says

The legal letter cites personal-rights categories: good name, reputation, honesty, diligence, reliability, trust, health, honour, privacy, image and secrecy of correspondence.

What the record already contains

The resident-channel message character-assassinated the resident as under unknown substances or suffering psychological issues, attacking sanity, sobriety, credibility and reputation.

Why both positions collapse together

The legal letter describes the categories their own communication ecosystem had already violated against the resident. It is psychological projection.

What would clear this up

Identify who authorized the health/substance message, withdraw it in the same channel, and explain why the legal letter invoked personal-rights language while leaving that character assassination uncorrected.

L-63“Anxiety among residents” vs documented pressure inside the administration / representative ecosystem Projection / anxiety STILL UNRESOLVED
What the legal letter says

The legal letter states that the resident generated unwarranted anxiety among the building’s residents.

What the record shows

The record shows pressure inside the administration / representative ecosystem, including the “unaffiliated representative” complaining that owners and administration were blaming him.

The contradiction

Unless the legal letter uses “the residents” as a label for the “unaffiliated representative,” it projects administration pressure into the residents’ name.

What would clear this up

Identify the residents described as anxious, state how that was verified, and explain why the paragraph immediately pivots from resident anxiety to the reputation of the Housing Community.

L-01“All questions answered” vs “lack organizational and technical capacity” Closure / capacity STILL UNRESOLVED
What they said

The administration stated that all questions had already been answered.

What the record also says

The legal correspondence used “the organizational and technical capacity” language as the stated reason not to fulfil the request in its current scope.

Why both cannot be true

If all questions were answered, lack of capacity is irrelevant. If the capacity language was used to avoid fulfilment, all questions were not answered. Both cannot be true.

What would clear this up

Choose which position is maintained: all answered, or capacity language was used to avoid fulfilment.

What happened

They did not answer.

L-02“Matter resolved” vs unanswered yes/no questions Closure / record STILL UNRESOLVED
What they said

The administration repeatedly declared the matter resolved.

What the record also says

Direct factual yes/no questions remained unanswered.

Why both cannot be true

Calling a matter “resolved” does not answer the questions. They declared it resolved while refusing the decisive facts.

What would clear this up

Identify the exact matter resolved, the date, the action and the responsible person.

What happened

They did not answer.

L-03“Matter resolved” vs continued restrictions and legal correspondence Closure / legal STILL UNRESOLVED
What they said

The matter was declared resolved.

What the record also says

The administration continued asserting restrictions, relying on cease-and-desist language, invoking “lack capacity,” and defending earlier positions.

Why both cannot be true

If the matter was resolved, continued justifications and legal-position documents were unnecessary. If they remained necessary, the matter was not resolved.

What would clear this up

Explain why continued legal positioning was required after resolution.

What happened

They did not answer.

L-04“Official email channel” vs registered letter, telephone, post-it, concierge and WhatsApp Communication channels STILL UNRESOLVED
What they said

Email was described as the official communication channel.

What the record also says

The record also relied on registered letters, telephone conversations, post-it notes through concierge, WhatsApp, off-thread email and reception/concierge routing.

Why both cannot be true

If email is exclusive, the other channels cannot carry operative meaning. If the other channels carry operative meaning, email is not exclusive.

What would clear this up

State the actual official channel and identify which prior communications count.

What happened

They did not provide a channel map.

L-0523 October “receipt” vs documents dated 26 October and 3 December Legal record integrity STILL UNRESOLVED
What they said

The administration stated that the resident received the law-office reply on 23 October 2025.

What the record also says

The PDFs later forwarded as the relevant law-office correspondence were dated 26 October 2025 and 3 December 2025.

Why both cannot be true

A specific document cannot be received before it exists. If a different 23 October transmission existed, the original .eml and headers should exist.

What would clear this up

Produce sender, timestamp, Message-ID, full headers and .eml — or correct the 23 October statement.

What happened

No original transmission proof was provided.

L-05B24 October “continuing to process” vs claimed 23 October law-office reply Legal record integrity / timing STILL UNRESOLVED
What they said

On 24 October 2025, the administration wrote that the matter had been referred to a law office, which was “continuing to process the matter” on behalf of the Housing Community.

What the record also says

The administration later maintained that the resident had received the law-office reply on 23 October 2025.

Why both cannot be true

If the law-office reply had already been sent on 23 October, the administration must explain why the matter was still described on 24 October as being processed by the law office. If the 23 October item was a different email, produce it. If it was the same reply, the timeline breaks.

What would clear this up

Identify the exact law-office document claimed as sent on 23 October and produce sender address, timestamp, Message-ID, full headers and .eml. If no such transmission exists, correct the 23 October statement.

What happened

They produced neither the original transmission proof nor an explanation.

L-05CThe legal-office timing triad: 23 October, 24 October, 26 October Legal record integrity / impossibility triad STILL UNRESOLVED
What they said

The resident was claimed as sent the law-office reply on 23 October 2025.

What the record also says

On 24 October 2025, the administration wrote that the law office was still continuing to process the matter.

Position C

The law-office PDFs later forwarded as the relevant correspondence were dated 26 October 2025 and 3 December 2025.

Why both cannot be true

All three positions cannot describe the same reply. A reply cannot be received on 23 October, remain “continuing to process” on 24 October, and then exist as a PDF dated 26 October. Reconciliation requires the original 23 October transmission, headers, Message-ID and .eml file.

What would clear this up

Provide the missing 23 October transmission or withdraw the claim. Do not replace the missing transmission with “matter resolved.”

What happened

They did not answer.

L-84ADMUS named in the legal position vs ADMUS removed from the later fragment GDPR / legal position / ADMUS removal STILL UNRESOLVED
What the legal text says

The October 26 legal position names the company providing administrative services for part of the common property: ADMUS sp. z o.o., based in Warsaw.

What the February 16 email does

The Administration presents the relevant law-office fragment while framing the processing structure as Housing Community only. The ADMUS sentence is gone.

Why both cannot be true

If the February 16 email was reproducing the legal position, the text should match. If it was edited, the Administration needs to identify who authorized the edit and whether the law office approved it. The strange part is obvious: the professional management company disappears, while the Housing Community is left as the visible responsible body.

Good-name problem

If ADMUS genuinely believed its name was “good,” ADMUS and Director [REDACTED] should appear more often as the contradictions and stakes increased — not less. A good name should be a social-proof advantage. Here, the name behaves like something to reduce exposure to.

What would clear this up

Produce the original 23 October transmission, full headers, Message-ID and .eml, identify the exact legal text relied on, explain why the ADMUS fragment was removed, explain why “Housing Community” was not conveniently removed instead, and explain why ADMUS disappeared precisely when a credible professional-management name should have helped.

What happened

They did not answer.

L-06“No further correspondence” vs further correspondence Closure / communication STILL UNRESOLVED
What they said

The administration used closure language indicating no further correspondence.

What the record also says

The administration continued contacting the resident whenever it wished to transmit its own position.

Why both cannot be true

A channel cannot be closed only in the direction that creates accountability. If correspondence continues, it is not closed.

What would clear this up

State whether the channel is closed or active and apply that answer consistently.

What happened

They left the contradiction unresolved.

L-07Schrödinger’s OIIA Cat: “contact details removed” vs continued contact Data / communication STILL UNRESOLVED
What they said

On March 19, 2026, the Administration wrote that the former resident’s contact details had been removed from the contact database.

What the record also says

The Administration used those contact details to send the statement announcing their removal. The resident replied eleven minutes later: “So how did you contact me now?”

What happened next

On April 16, 2026, nearly one month later, the Administration responded that the Housing Community found no grounds for conducting further correspondence.

Why both cannot be true

If the contact data was removed, how was the message delivered? If it remained available, what exactly was removed?

What would clear this up

Identify the data removed, the data retained, the system used and the lawful basis for continued contact.

What happened

They declared closure instead of answering the paradox.

L-08“Urgent” inspection vs an 83-day delay Inspection / urgency STILL UNRESOLVED
What they said

The inspection was described as urgent and linked to safety and insurance.

What the record also says

The administration allowed 83 days to pass. Then they miss their own deadline.

Why both cannot be true

Urgency has a time signature. If genuinely urgent, the delay is indefensible. If it could wait 83 days, the urgency language was exaggerated.

What would clear this up

Explain whether the urgency was accurate. If yes, explain the delay. If no, withdraw the urgency framing.

What happened

They did not answer.

L-09“Safety of residents, employees and guests” vs they miss their own deadline Inspection / safety STILL UNRESOLVED
What they said

They described the inspection as affecting the safety of residents, employees and guests.

What the record also says

They miss their own deadline and do not act with urgency consistent with that statement.

Why both cannot be true

Either the risk language was accurate and the administration mishandled a serious risk, or the language was used as pressure. Neither branch is benign.

What would clear this up

Explain how they miss their own deadline while using maximum-risk language.

What happened

They did not answer.

L-10“Tenant did not confirm / could not be reached” vs 10+ scheduling attempts Inspection / record STILL UNRESOLVED
What they said

After missing their own deadline, the administration blamed the failed inspection on alleged lack of disabled-resident confirmation or contact.

What the record also says

The record contains repeated direct scheduling attempts plus additional attempts through reception and concierge.

Why both cannot be true

A party actively trying to schedule cannot honestly be reduced to “did not confirm” without addressing the documented attempts.

What would clear this up

Account for each attempt and explain why it was ignored or not treated as cooperation.

What happened

They did not answer.

L-64They miss their own deadline vs the written 9 February thread Inspection / record STILL UNRESOLVED
What they said

They miss their own deadline. Złota 44 then wrote that the inspection did not take place because there was “no confirmation” from the resident.

What the record also says

The 9 February thread shows multiple written confirmations, a day-of reminder, a 12:55 record that no identifiers or arrival confirmation had been provided, and a 1:49 response documenting that availability had been confirmed multiple times. They miss their own deadline inside that same thread.

Why both cannot be true

A party cannot ignore confirmations, fail to provide the requested company / technician / insurance details, miss their own deadline, and then reduce the failed inspection to “no confirmation from you.”

What would clear this up

Identify exactly what confirmation was supposedly missing, why the resident’s written confirmations were not accepted, and why the administration did not provide the required inspection details before they miss their own deadline.

What happened

No clean reconciliation was provided.

L-11Insurance invoked as pressure vs insurance details refused Insurance / liability STILL UNRESOLVED
What they said

Insurance and liability risk were invoked to justify urgency and access.

What the record also says

The administration refused or failed to provide the requested insurer and policy information.

Why both cannot be true

Insurance cannot be important enough to pressure the resident and simultaneously too irrelevant to identify when accountability is requested.

What would clear this up

Provide insurer, policy, scope, responsible insured party and applicable liability cover.

What happened

They did not disclose it.

L-65Asked for insurer details vs a self-issued liability verdict Insurance / self-adjudication STILL UNRESOLVED
What they said

“No damage was found that was caused by the Housing Community, therefore there is no basis to provide the policy number.”

What the record also says

The request asked for the insurer name, policy number, general scope of coverage and claims-contact details.

Why both cannot be true

A verdict about the Housing Community’s own responsibility does not identify the insurer. The response substituted self-adjudication for the requested policy information.

What would clear this up

Provide the insurer name, policy number, coverage scope, claims contact and the factual basis for the “no damage caused by the Housing Community” conclusion.

What happened

None of the four requested policy details were supplied.

L-12“No damage attributable to the Community” before the factual question was answered CCTV / liability STILL UNRESOLVED
What they said

The administration answered with language such as “no damage attributable to the Community.”

What the record also says

The resident was asking whether the apartment door was visible, whether a blind spot existed and what evidence was available — not requesting a final liability judgment.

Why both cannot be true

A liability conclusion cannot substitute for the underlying factual answer. Door visibility must be established before attribution can be adjudicated.

What would clear this up

Answer whether the door was fully visible, what footage existed and what was reviewed.

What happened

No clean factual answer provided.

L-13No CCTV problem implied vs refusal to state that no blind spot exists CCTV / visibility STILL UNRESOLVED
What they said

The administration implied there was no relevant CCTV irregularity.

What the record also says

It did not simply state: “There is no CCTV blind spot at apartment (REDACTED).”

Why both cannot be true

If no blind spot exists, its non-existence is the easiest documented fact to state. Refusing the sentence preserves ambiguity exactly where certainty was requested.

What would clear this up

Confirm or deny the blind spot directly.

What happened

They did not answer.

L-14Post-it note not visible from live feed vs implied door coverage CCTV / live feed STILL UNRESOLVED
What they said

The administration did not accept that the apartment door sat in a blind area.

What the record also says

Security could not tell whether a note attached to the door was black or white because the door itself was not visible.

Why both cannot be true

If the door is visible, the note should be observable. If it is not observable because the door is not visible, a visibility gap exists.

What would clear this up

State exactly what the camera sees and does not see at apartment (REDACTED).

What happened

They did not answer.

L-15Security recommended a private spy camera vs supposedly sufficient building CCTV CCTV / security STILL UNRESOLVED
What they said

Building CCTV coverage was treated as sufficient or unproblematic.

What the record also says

Security recommended buying a private spy camera from Amazon and showed product recommendations because the apartment door could not be seen.

Why both cannot be true

Adequate building CCTV and “buy your own spy camera” are not coherent responses to the same security concern.

What would clear this up

Explain why private surveillance was recommended if the building system covered the door adequately.

What happened

They did not answer.

L-16“Unaffiliated” person vs stylistic knowledge of private emails Authority / data access STILL UNRESOLVED
What they said

The individual acting through the “Zarząd Złota 44” context was described as unaffiliated.

What the record also says

He described the resident’s emails as “fucking ChatGPT bulshits” — a stylistic evaluation of the text.

Why both cannot be true

That is the equivalent of describing Mona Lisa’s facial expression without seeing the painting. Either he saw the emails, received detailed summaries, or the unaffiliated description is false.

What would clear this up

State whether he read, received, was forwarded, or was briefed on the emails — and by whom.

What happened

They did not answer.

L-17“Unaffiliated” person vs knowledge of behavior outside the apartment door Authority / CCTV STILL UNRESOLVED
What they said

The individual was described as unaffiliated.

What the record also says

He commented on behavior outside the apartment door and on the resident photographing a security camera.

Why both cannot be true

The information required a source: direct observation, CCTV, staff reports, or another internal channel. “Unaffiliated” does not explain privileged situational knowledge.

What would clear this up

Identify the source and whether CCTV or security summaries were shared.

What happened

They did not answer.

L-18“Unaffiliated” person vs authority-like influence inside the building Authority / governance STILL UNRESOLVED
What they said

The individual was described as unaffiliated and outside administrative responsibility.

What the record also says

The same individual operated across resident communication, authority presentation, security narratives and access-related interventions.

Why both cannot be true

If genuinely unaffiliated, he should not exercise authority-like influence. If his influence was permitted or tolerated, the administration must identify the governance basis.

What would clear this up

Define his role, permissions, authority source and relationship to administration.

What happened

They did not answer.

L-19“Official” WhatsApp vs “unofficial” WhatsApp WhatsApp / governance STILL UNRESOLVED
What they said

The group was presented through administration-facing signage and used for building-relevant resident communication.

What the record also says

Responsibility for the group was later distanced by describing it as unofficial or outside administration control.

Why both cannot be true

A channel cannot be official when useful and unofficial when accountable.

What would clear this up

State who authorized the group, QR signage and administrative use, and whether it was official.

What happened

They did not answer.

L-20Administration distances itself from character assassination vs no correction in the same channel Character assassination / correction STILL UNRESOLVED
What they said

The administration distanced itself from the drugs / mental-health character assassination while leaving it uncorrected.

What the record also says

They issued no correction or withdrawal in the channel where the character assassination was circulated.

Why both cannot be true

If the statement was false and not endorsed, correction was the obvious response. Distancing without correction preserves the benefit of the character assassination while denying ownership.

What would clear this up

Correct and withdraw the statement in the same channel and identify the author.

What happened

They issued no correction.

L-21“Anxiety among residents” vs refusal to provide factual reassurance Legal / CCTV STILL UNRESOLVED
What they said

Legal correspondence invoked anxiety among residents.

What the record also says

The administration would not provide the simplest factual reassurance: whether the apartment door was fully visible in footage.

Why both cannot be true

If anxiety were genuinely the concern, clarity would reduce it. Vague liability wording protects position, not residents.

What would clear this up

State the factual CCTV visibility position directly.

What happened

They did not answer.

L-22“Anxiety among residents” vs immediate pivot to reputation Legal / priority signal STILL UNRESOLVED
What they said

The correspondence invoked resident anxiety as the human concern.

What the record also says

The same passage quickly concluded that the real adverse effect was damage to the Housing Community’s reputation.

Why both cannot be true

If resident wellbeing were primary, it would remain the focal point. The rapid pivot exposes the actual protected object: reputation.

What would clear this up

Clarify whether the claimed harm was resident wellbeing or reputation.

What happened

They did not clarify it.

L-23Legal false-information attack vs no exact false statements identified Legal / specificity STILL UNRESOLVED
What they said

The legal correspondence attacks the resident with “false information” and personal-rights language.

What the record also says

It did not clearly enumerate each exact statement, publication, date, falsity, correct version and demanded correction.

Why both cannot be true

A demand without the disputed statements is not a correction protocol. It is a broad pressure label.

What would clear this up

List every identified as false statement with the evidence and required correction.

What happened

No clean list provided.

L-24Technician adjectives changed only after legal definitions were explained Inspection / wording STILL UNRESOLVED
What they said

The administration initially used stronger adjectives carrying greater qualification, authorization or responsibility implications.

What the record also says

The wording softened only after the resident explained the legal and operational meaning of those adjectives.

Why both cannot be true

If the original wording was accurate, it should survive scrutiny. A post-scrutiny downgrade shows the original term carried responsibility the administration no longer wanted to own.

What would clear this up

Define each technician’s exact company, role, qualification, authorization, scope and liability status.

What happened

They provided no specificity.

L-25Legal/liability specificity requested vs deliberate non-clarification Inspection / liability STILL UNRESOLVED
What they said

The resident requested names, companies, legal basis, scope, insurer and liability allocation before entry.

What the record also says

The administration did not provide the requested specificity.

Why both cannot be true

A legitimate and safe inspection process becomes stronger with specificity. Refusing specificity preserves deniability, not safety.

What would clear this up

Provide the full responsibility chain for each proposed entrant.

What happened

They did not answer.

L-26UODO escalation vs sudden “urgent” inspection within approximately 24 hours GDPR / timing STILL UNRESOLVED
What they said

They described the inspection as independently urgent for safety and insurance reasons.

What the record also says

They announced the “urgent” inspection within approximately 24 hours of the Article 15 failure being escalated to UODO.

Why both cannot be true

The timing is part of the record. If the urgency was independent of the UODO escalation, pre-existing evidence of the same urgency should be easy to produce.

What would clear this up

Explain the timing and provide records showing the urgency existed before the UODO escalation.

What happened

They did not answer.

L-27Two-bottle ban vs receptionist confirmation that taking water out was fine Access restriction / rule STILL UNRESOLVED
What they said

The formal restriction reason was removing two bottles of mineral water from the club area.

What the record also says

Reception staff stated that taking bottled water downstairs or to the apartment was fine, including a confirmation recorded on video.

Why both cannot be true

If staff were right, the restriction basis collapses. If staff were wrong, the building gave residents incorrect operational guidance. If enforcement was selective, say so.

What would clear this up

State whether taking bottled water out is permitted and identify where the rule was communicated.

What happened

They did not answer.

L-28Legal precision over water vs no precision on safety, CCTV, GDPR or insurance Resource allocation / proportionality STILL UNRESOLVED
What they said

The administration formalized a 30-day restriction through legal correspondence over two bottles of mineral water.

What the record also says

They withheld that precision on safety, CCTV, GDPR, insurance, authority and the character assassination.

Why both cannot be true

A system capable of legal precision over free water cannot credibly present serious questions as too broad, too difficult or beyond capacity.

What would clear this up

Explain why mineral water received clearer formal treatment than the serious issues.

What happened

They did not answer.

L-29Director reassurance maintained while the director’s signature disappeared Director / ownership STILL UNRESOLVED
What they said

Director [REDACTED] originally reassured the resident that “zero irregularities” were found and gave broad safety assurance.

What the record also says

After the resident challenged evasive CCTV/blind-spot wording, later correspondence stopped carrying the director’s name without correcting his reassurance.

Why both cannot be true

Maintaining the reassurance while removing the person visibly attached to it preserves the benefit of the guarantee while reducing the liability footprint of the signature.

What would clear this up

Confirm whether the director’s reassurance remains maintained. If yes, explain the signature retreat. If no, withdraw or correct it.

What happened

They issued no correction.

L-30“Individual statement” escape vs administration presented as one coherent office Governance / ownership STILL UNRESOLVED
What they said

The administration distances itself from the resident-facing actor by describing him as private or unaffiliated.

What the record also says

Admus presents itself as a coherent, professionally organized administrative unit and repeatedly maintained its positions collectively.

Why both cannot be true

A coherent office owns maintained positions unless it expressly corrects them. It cannot invoke collective authority for reassurance and individual isolation for liability.

What would clear this up

Map which statements are office positions, which are withdrawn, and who owns each one.

What happened

No clean ownership map provided.

L-31“Zero irregularities found” vs unresolved 18–22 Ω readings Electrical safety STILL UNRESOLVED
What they said

The administration maintained “zero irregularities found.”

What the record also says

The record contains 18–22 Ω readings that were repeatedly questioned and never cleanly reconciled with the absolute reassurance.

Why both cannot be true

“Zero irregularities” requires a standard-based explanation of why the identified values are not irregular. Without that, the conclusion is unsupported.

What would clear this up

State the applicable standard or correct the zero-irregularities position.

What happened

No clean technical explanation provided.

L-32Absolute safety reassurance vs refusal to disclose its factual basis Safety / evidence STILL UNRESOLVED
What they said

Broad or absolute safety reassurance was maintained.

What the record also says

They withheld the key factual bases: CCTV visibility, technical readings, inspection responsibility, insurance and records.

Why both cannot be true

Absolute reassurance without the underlying evidence is branding, not verification.

What would clear this up

Produce the factual and technical basis supporting the reassurance.

What happened

They provided no basis.

L-33Drugs / mental-health character assassination vs explicit opportunity to correct Character assassination / maintained record STILL UNRESOLVED
What they said

The false drugs / mental-health character assassination was left in the resident record.

What the record also says

The administration was explicitly asked to identify the author, correct the statement, withdraw it, or write REFUSE.

Why both cannot be true

When a false statement is given an easy correction path and remains uncorrected, non-correction becomes a documented choice.

What would clear this up

Identify, correct, withdraw or explicitly refuse.

What happened

They issued no correction.

L-34“Concerning conduct” vs refusal to disclose the factual basis Narrative / evidence STILL UNRESOLVED
What they said

Resident conduct was characterized as concerning or irregular.

What the record also says

The administration did not produce a clean factual map of the conduct, source, footage, logs, witness or rule supporting the characterization.

Why both cannot be true

A concern claim without disclosed facts is narrative. The label cannot substitute for evidence.

What would clear this up

Identify the factual basis for each concern claim.

What happened

They provided no factual basis.

L-35“Unaffiliated” person vs access to CCTV, email or resident information Authority / data flow STILL UNRESOLVED
What they said

The individual was described as unaffiliated.

What the record also says

His statements showed access to information normally available through CCTV, email, staff reports or internal data flow.

Why both cannot be true

An unaffiliated person should not possess privileged resident information. If he did, the data path must be identified. If he did not, the statements require another explanation.

What would clear this up

Identify every source through which he received resident information.

What happened

They did not answer.

L-36Official-looking QR signage vs no official responsibility WhatsApp / reliance STILL UNRESOLVED
What they said

Residents were directed to the group through signage outside the administration office.

What the record also says

The administration later distanced itself from responsibility for the group.

Why both cannot be true

Administration-facing signage creates reasonable resident reliance. A channel cannot be promoted at the office and disowned only after it becomes inconvenient.

What would clear this up

Identify who approved the sign and who accepted responsibility for the channel.

What happened

They did not answer.

L-37Non-response treated as neutral vs pre-warning that silence maintained the position Correction process STILL UNRESOLVED
What they said

The administration left the specific correction questions unanswered.

What the record also says

It was explicitly warned that silence would be recorded as maintaining its last written position without correction and was given direct correction/refusal options.

Why both cannot be true

After precise notice, silence is the documented choice not to correct the specific contradictions presented.

What would clear this up

Answer, correct, deny, withdraw, or mark REFUSE.

What happened

They issued no correction.

L-38“False information” vs refusal to use the offered correction protocol Correction process / legal STILL UNRESOLVED
What they said

The administration and legal correspondence state that false information was being circulated.

What the record also says

It did not use the offered protocol: exact sentence, proof, corrected version and responsible person.

Why both cannot be true

If a statement is false, a documentary correction is straightforward. Refusing to identify it keeps “false information” as an unfalsifiable label.

What would clear this up

Use the correction protocol for every identified as false statement.

What happened

The correction protocol was not used.

L-39Premium professional management vs inability to answer binary questions Governance / competence STILL UNRESOLVED
What they said

Złota 44 is presented as professionally administered at a premium standard.

What the record also says

The administration repeatedly avoided binary questions about authority, CCTV, official channels, insurance, legal transmission and correction of false statements.

Why both cannot be true

When yes/no questions cannot be answered, the issue is not complexity. It is the consequence created by the answer.

What would clear this up

Answer each binary question directly or state REFUSE beside it.

What happened

No clean binary response provided.

L-40Prestige branding vs legal escalation over mineral water Prestige / proportionality STILL UNRESOLVED
What they said

Złota 44 presents itself through prestige, security and high standards.

What the record also says

Its formal legal record includes a 30-day restriction over two bottles of mineral water while serious governance questions remained unanswered.

Why both cannot be true

Prestige raises the expected standard. It does not make disproportionate paperwork over free water look more serious; it makes the proportionality failure more absurd.

What would clear this up

Explain the proportionality and the institutional priority reflected by it.

What happened

They did not answer.

L-41“Anyone can claim to be who they want to be” vs “authorized technicians” Authority / inspection STILL UNRESOLVED
What they said

When distancing itself from an inconvenient authority actor, the director-level response was: “Anyone can claim to be who they want to be.”

What the record also says

When seeking apartment access, the administration relied on the phrase “authorized technicians.”

Why both cannot be true

“Authorized” has operational weight only if identity and authorization are verified. If anyone can claim any identity, “authorized technician” becomes a costume label unless the administration supplies the verifier, document, scope and liability chain. This is authority when useful and ambiguity when accountable.

What would clear this up

Define who authorizes, how authorization is verified, what document proves it, what liability applies and how a resident independently confirms it.

What happened

No operational definition was provided.

L-42The legal-liability equivalent of downgrading “wife” to “girlfriend” Inspection / adjective downgrade STILL UNRESOLVED
What they said

The administration initially used stronger terms implying higher qualification, authorization, responsibility or institutional commitment.

What the record also says

After the resident explained the legal and liability consequences, the wording was downgraded to softer, less operationally loaded adjectives.

Why both cannot be true

This is the legal-liability equivalent of downgrading your “wife” to “girlfriend.” Both describe a relationship. They do not carry the same obligations. If the stronger term was true, it should survive scrutiny. If it was not true, why was it used before the consequences were explained?

What would clear this up

Provide the exact legal and operational status of every proposed entrant: name, company, role, qualification, authorization source, scope, insurer and responsibility chain.

What happened

They did not clarify it.

L-43“Lack organizational and technical capacity” vs capacity for legal-office mineral-water processing Capacity / resource allocation STILL UNRESOLVED
What they said

The Housing Community used “lack of organizational and technical capacity” language when asked for serious safety, CCTV, GDPR, insurance and authority transparency.

What the record also says

The same organization allocated capacity to route a one-month common-area restriction through a legal office over two bottles of mineral water.

Why both cannot be true

This is not a capacity shortage. It is priority exposure. Capacity existed; it was spent on mineral-water enforcement rather than answering the adult questions.

What would clear this up

Explain why legal-office capacity was available for free-water enforcement while transparency and data-access capacity was claimed unavailable.

What happened

They did not answer.

L-44Claimed capacity failure vs legal precision against the resident Capacity / priorities STILL UNRESOLVED
What they said

The administration used capacity limitations to resist broad transparency and documentary requests.

What the record also says

It displayed exact dates, rule citations, ban duration, formal legal routing and two-bottle precision when restricting the resident.

Why both cannot be true

They had capacity. They used it where it controlled the resident and withheld it where it exposed their own conduct.

What would clear this up

Publish the criteria used to allocate administrative and legal capacity.

What happened

They did not answer.

L-452023 report records 18–22 Ω vs later report omits the test/value Electrical / document continuity STILL UNRESOLVED
What they said

The 2023 documentation contained 18–22 Ω readings.

What the record also says

The later report did not clearly carry forward or resolve the same measurement.

Why both cannot be true

If the condition remained, omission hides continuity. If the condition was corrected, the corrective record should exist. If the test was no longer relevant, the technical reason should be stated.

What would clear this up

Explain why the measurement disappeared and produce any corrective or retest documentation.

What happened

No clean continuity explanation provided.

L-46“No unusual activity” vs an area the camera could not see CCTV / epistemic limit STILL UNRESOLVED
What they said

The administration relied on language such as no unusual activity being indicated.

What the record also says

Security stated that the apartment door itself was not visible from the relevant live feed.

Why both cannot be true

A system cannot conclude “no unusual activity” in the exact area it cannot observe. The only supported conclusion is that no unusual activity was visible in the areas the camera covered.

What would clear this up

Define the camera field of view and narrow the conclusion to what the footage could actually establish.

What happened

No clean limitation statement provided.

L-47“Inappropriate loud behavior” vs “two bottles of mineral water” Restriction / reason shift STILL UNRESOLVED
What they said

An administration communication described the restriction through inappropriate or loud behavior.

What the record also says

The later legal letter stated the reason was removal of two bottles of mineral water.

Why both cannot be true

The stated basis changed between noise and free water. Identify both grounds, the evidence for each, and the rule applied.

What would clear this up

State every ground relied upon, the date each was adopted, the evidence and the rule applied.

What happened

Source pair should be displayed side by side; no clean reconciliation identified.

L-48Court threat vs no documented filing Legal threat / follow-through STILL UNRESOLVED
What they said

The resident-channel message announced that the matter would be brought to court as soon as documented.

What the record also says

No court number, filing date, pleading or identified proceeding was produced in the documented exchange.

Why both cannot be true

“As soon as documented” is a claim about imminent action. If the action occurred, proof is simple. If it did not, the statement functioned as intimidation rather than procedural notice.

What would clear this up

Provide the court, case number, filing date and pleading — or correct the statement.

What happened

No filing identified in the supplied record.

L-49Corrupted PDF data vs reliance on the PDF as an authoritative technical record Document integrity STILL UNRESOLVED
What they said

The administration relied on technical PDFs as authoritative records supporting reassurance.

What the record also says

The supplied PDF contains abnormal hexadecimal content, including repeated 0x50 bytes decoded as “P” characters at the file-header position where a normal PDF structure was expected.

Why both cannot be true

A record cannot simultaneously be the authoritative basis for reassurance and remain unexplained when its file integrity is questioned.

What would clear this up

Provide the original native file, hash, source system, creation history and an integrity explanation.

What happened

No clean integrity explanation provided.

L-50“No room for drama” vs broadcasting character assassination, panic language and court threats Resident communication / projection STILL UNRESOLVED
What they said

The resident-channel message condemned drama and panic.

What the record also says

The same communication broadcast drugs / mental-health character assassination, warned neighbours, removed the subject from the channel and threatened imminent court action.

Why both cannot be true

A message cannot credibly condemn drama while manufacturing the most dramatic documented resident narrative. The disclaimer describes the conduct of the message itself.

What would clear this up

Identify the objective facts justifying the broadcast and explain why a private procedural response was insufficient.

What happened

They did not answer.

L-53“Broadly formulated request” vs narrowed fallback path GDPR / scope STILL UNRESOLVED
What they said

The legal correspondence used lack of organizational and technical capacity as the stated reason not to fulfil the request, relying on the request’s alleged broad scope.

What the record also says

The 9 October request identified a defined access period, a defined CCTV hour, specific categories, requested formats, preservation, and a fallback: provide the full cardholder audit trail, last 30 days of access events, and propose a schedule for the remaining five months.

Why both cannot be true

A request with a built-in narrowing mechanism cannot be dismissed as merely broad without explaining why the fallback was also avoided. If full fulfilment was difficult, the partial route was already in the request.

What would clear this up

Explain why the narrowed fallback path was not fulfilled.

What happened

They did not answer.

L-54“Lack organizational capacity” vs legal-office capacity for mineral-water enforcement Capacity / resource allocation STILL UNRESOLVED
What they said

The Housing Community used lack of organizational and technical capacity as the stated reason to avoid fulfilling the Article 15 / records request in its current scope.

What the record also says

The same system had enough capacity to route a 30-day common-area restriction through legal correspondence over “the removal of two bottles of mineral water from the club area.”

Why both cannot be true

Legal-office capacity was spent on mineral-water enforcement while the narrowed GDPR/access-log fallback remained unfulfilled. This is not a capacity shortage. It is priority exposure.

What would clear this up

Explain why legal-office capacity was available for two bottles of water but not for access logs, CCTV retention, data recipients, controller identification and a narrowed fallback request.

What happened

They did not answer.

L-55“Anyone can claim to be who they want to be” vs “authorized technicians” Authority / authorization STILL UNRESOLVED
What they said

When confronted about authority and representation, the director-level answer was: “Anyone can claim to be who they want to be.”

What the record also says

The administration later relied on terms such as “authorized technicians” / authorized inspection personnel.

Why both cannot be true

The word “authorized” only has operational meaning if authorization is verified, identifiable and accountable. A serious administration cannot use “anyone can claim” when distancing itself from an inconvenient representative, then rely on “authorized” when seeking apartment access.

What would clear this up

Define what “authorized” means operationally: who grants it, how it is verified, what document proves it, what liability cover applies, and how residents can confirm it.

What happened

No operational definition was provided.

L-56“Unaffiliated representative” vs “Management board member of Z44” Authority / self-description STILL UNRESOLVED
What they said

The individual was later treated as unaffiliated / not formally representing the Housing Community.

What the record also says

The individual signed resident communication as “Management board member of Z44.”

Why both cannot be true

If the claim was false, the administration should explain why a false authority claim was allowed to stand in a resident group. If it was true, the distancing position collapses. “Anyone can claim to be who they want to be” is not a governance model.

What would clear this up

Confirm whether the individual was authorized, unauthorized, tolerated, delegated, or misrepresenting himself — and what action was taken.

What happened

They did not answer.

L-57“Unaffiliated” vs access to administration/developer/technical conclusions Unaffiliated representative / internal knowledge STILL UNRESOLVED
What they said

The individual was unaffiliated or not an official representative.

What the record also says

The individual described administration reports, developer/institute consultations, and technical conclusions about the resident’s apartment.

Why both cannot be true

If he was unaffiliated, he should not be able to relay internal technical/legal conclusions unless someone briefed him. If he was briefed, the administration must identify the data path. If he was not briefed, his statements were unsupported and should have been corrected.

What would clear this up

State whether he received, accessed, was forwarded, or was orally briefed on administration records, technical reports, emails, CCTV, or developer/institute conclusions.

What happened

They did not answer.

L-58“Fucking email with ChatGPT” vs unaffiliated/no email access Email/data access paradox STILL UNRESOLVED
What they said

The individual was unaffiliated and should not have privileged access to administration inboxes or resident emails.

What the record also says

The same individual gave stylistic feedback about the resident’s emails, including “writing fucking email with chat gpt.”

Why both cannot be true

A person cannot describe the style of emails he has not seen or been briefed on. If he read them, why did he have access? If he did not read them, who described them to him? If neither happened, the statement has no basis and should have been corrected.

What would clear this up

Identify whether the individual read, received, was forwarded, or was briefed on the resident’s emails.

What happened

They did not answer.

L-59“Unaffiliated” vs “owners and administration are blaming me” Blame routing / affiliation STILL UNRESOLVED
What they said

The individual was unaffiliated / outside formal responsibility.

What the record also says

The individual described pressure and blame from owners and administration in connection with the resident’s conduct.

Why both cannot be true

If administration blamed him, they recognized him as relevant to the resident-facing situation. If he was irrelevant and unaffiliated, why was blame routed to him? Both cannot be comfortably maintained without defining his role.

What would clear this up

Explain why an unaffiliated person was in a blame/pressure relationship with administration regarding the resident.

What happened

They did not answer.

L-60“They don’t need more to prove” vs GDPR/access/evidence rights Proof standard / rights STILL UNRESOLVED
What they said

The representative stated that administration had documents and technicians’ reports and “they don’t need more to prove.”

What the record also says

The resident requested access logs, CCTV retention, personal-data handling, technical bases, and insurance/liability specificity.

Why both cannot be true

“We have enough for ourselves” is not the same as transparent disclosure to the data subject or resident. Internal confidence does not replace the obligation to answer the factual basis when access, safety, CCTV and data handling are disputed.

What would clear this up

Provide the records, or identify the legal basis for refusing them.

What happened

They did not disclose it.

L-61Mental-health / substance character assassination vs medical certificate Medical record / character-assassination contradiction STILL UNRESOLVED
What they said

The resident-channel message character-assassinated the resident as under unknown substances or suffering psychological issues.

What the record also says

The redacted medical certificate states that the resident does not show psychosis, is not delusional, is not addicted to psychoactive substances, is stable, fully oriented, logical, coherent, factual, and collects evidence regarding the disputed situation.

Why both cannot be true

The resident-channel character assassination conflicts directly with the medical record. They were given explicit correction opportunities. They issued no correction in the same channel and removed the resident from it. That is character assassination, not administration.

What would clear this up

Identify who authored or allowed the statement, state whether it is maintained or withdrawn, and correct the statement in the same channel where it circulated.

What happened

No clean correction or same-channel withdrawal provided.

L-66“The issue applies only to your apartment” vs mouse, chair, carpet, clothing and towelSTILL UNRESOLVED
Position A

The administration states that the reported issue applies only to the resident’s apartment.

Position B

The proposed explanation is a computer, mouse friction, chair friction, carpet, clothing, towel use and spending time inside.

Logical conflict

Those are ordinary objects and behaviours across a residential building. If they explain the problem, the “only your apartment” claim requires apartment-specific measurements. If the apartment-specific measurements are the 18–22 Ω readings, those were the values the resident asked them to clarify.

Correction requested

Identify the apartment-specific technical measurement that justified the “only your apartment” conclusion, or withdraw that conclusion.

Status

Unresolved.

L-67Legal-office enforcement over two free waters vs no documented accountability for the “unaffiliated representative”STILL UNRESOLVED
Position A

A 30-day common-area restriction over two free bottles of mineral water was formalized through legal correspondence.

Position B

They produced no correction, no withdrawal, no reprimand, no investigation result and no documented sanction for the Unaffiliated Foreign Representative who made court threats, circulated the drugs / mental-health character assassination, demonstrated internal email/CCTV knowledge and intercepted the police report.

Logical conflict

They deployed legal precision against the resident over free water while refusing accountability for authority abuse, data access, character assassination and police-report interception.

Correction requested

Identify every investigation, correction or sanction concerning that conduct — or explain why two free bottles received stronger formal enforcement.

Status

Unresolved.

L-68Limited “organizational and technical capacity” vs official Instagram story monitoringCapacity / public monitoringSTILL UNRESOLVED
Position A

The administration / legal response claimed lack of organizational and technical capacity while leaving direct safety, CCTV, GDPR, authority, insurer and inspection questions unanswered.

Position B

The official Instagram account, presented on the same physical sign as the official WhatsApp group outside the Admus / administration office, silently viewed the resident’s personal Instagram story almost immediately after it was posted.

Logical conflict

If capacity was limited, why was capacity available for silent personal-story monitoring but not for answering the direct record: 18–22 Ω, CCTV retention, door visibility, authority, data access, insurer details, inspection identifiers and correction demands?

Correction requested

Identify who operated the official Instagram account, why the story was viewed, what legal / operational purpose this served, and why those same resources were not used to answer the direct written questions.

Status

Still unresolved.

L-69“Unaffiliated/no inbox access” vs “ChatGPT bulshits” communicated from somewhereEmail/data access paradoxSTILL UNRESOLVED
Position A

The individual is described as unaffiliated and not part of the administration’s official inbox or correspondence flow.

Position B

The individual commented on the resident’s administrative emails as “ChatGPT bulshits,” which requires either direct access, forwarding, summaries or office communication about the resident’s private correspondence.

Logical conflict

If he did not access the official inbox, then someone inside the administration / office environment communicated the content or characterization to him. If nobody did, then the statement was baseless and should have been corrected.

Correction requested

State which version is true: direct access, forwarded emails, oral briefing, office communication, or baseless statement. Also explain whether residents are expected to reduce clarity, linguistic accuracy or logical chain-of-reasoning to be taken seriously when reporting safety, security or personal-data violations.

Status

Still unresolved.

L-70System errors ruled out vs unexplained manual access restrictionsAccess control / manual changesSTILL UNRESOLVED
Position A

The administration wrote that the card had been checked, access refreshed and system issues ruled out.

Position B

Access restrictions appeared without notice or explanation, including restrictions close to the resident-channel character assassination and later after the GDPR deadline failure / UODO escalation.

Logical conflict

If system errors were ruled out, the restrictions were not random system failures. They were manually applied, manually maintained or otherwise knowingly permitted.

Correction requested

Identify who applied or maintained the restrictions, when, under what rule, and why no notice was supplied.

Status

Still unresolved.

L-71Access restriction timing vs the “Dear Neighbours” character assassinationAccess control / timingSTILL UNRESOLVED
Position A

The administration later formalized a different common-area restriction reason through legal correspondence.

Position B

The earlier access restriction occurred at the same time as the resident-channel “Dear Neighbours” drugs / mental-health character assassination.

Logical conflict

A ban that can be applied, checked and restored by the administration cannot be waved away as unrelated while the false sensitive-data broadcast is left uncorrected in the same operational environment.

Correction requested

Explain the timing, identify the decision-maker and provide the ACS / access-control logs.

Status

Still unresolved.

L-72Access can be checked/restored vs ACS logs withheld under Article 15Access control / GDPRSTILL UNRESOLVED
Position A

The administration could request the card number, check the card, refresh access, restore access and verify that system errors were ruled out.

Position B

The administration later claimed lack of organizational and technical capacity when the resident requested the relevant ACS / access-control logs under GDPR Article 15.

Logical conflict

The same system that can be operated, checked and restored cannot become inaccessible when the resident asks for the logs explaining what happened.

Correction requested

Produce the access-control logs, operator IDs, timestamps, access-level changes and recipients — or explain why operational access existed but disclosure capacity did not.

Status

Still unresolved.

L-73Unexplained access restrictions vs repeated appearance of the “unaffiliated” authority figureAccess control / authoritySTILL UNRESOLVED
Position A

The person was described by the administration as unaffiliated.

Position B

The same perceived authority figure appears across the record around authority perception, email access claims, CCTV/police context and unexplained access restrictions.

Logical conflict

If this is coincidence, the administration should state that and accept that probability calculations will be placed next to that statement. If it is not coincidence, the affiliation / authority chain must be identified.

Correction requested

Explain the repeated timing and presence pattern, identify the authority chain and provide the relevant logs.

Status

Still unresolved.

L-742025 static-discharge explanation vs 2023 electrical readingsElectrical / technical non-answerSTILL UNRESOLVED
Position A

The electrical discharges were explained through static electricity from clothes, carpet, mouse, chair, towel and time spent indoors.

Position B

The Administration’s own documentation showed Rs readings around 18–22 Ω from 2023.

Logical conflict

Present-day socks and chair friction cannot retroactively create grounding-resistance values in a technical report from two years earlier.

Correction requested

Explain whether the Rs values around 18–22 Ω were safe, under which standard, who verified them, and why the Administration maintained a static-discharge explanation instead of answering the technical question.

Status

Still unresolved.

L-75Corrupted electrical PDF header vs reliance on the file as proof of electrical safetyElectrical / PDF integritySTILL UNRESOLVED
Position A

The Administration relied on technical PDFs and “zero irregularities found” language as proof that the electrical situation was safe.

Position B

The preserved hex view of the electrical PDF shows repeated 0x50 bytes — decoded as “P” characters — at the header position where normal PDF structure was expected.

Logical conflict

A file with an abnormal header cannot be treated as a clean, self-explanatory proof of safety while the Administration refuses to explain the file-generation chain, the Rs readings around 18–22 Ω and the later omission of those readings.

Correction requested

Explain what software, export, scan, conversion or action produced the repeated 0x50 header pattern; provide the clean original file; and explain why a corrupted file was forwarded while the Administration maintained broad safety reassurance.

Status

Still unresolved.

L-76Disclosed neurological vulnerability vs drugs / mental-health character assassinationNeurological vulnerability / resident safetySTILL UNRESOLVED
Position A

The resident disclosed a neurological vulnerability while reporting electrical shocks and asking whether ordinary electrical use was safe.

Position B

The administration-side ecosystem allowed the same resident to be framed to 120+ residents through “mental issues” / “unknown substances” language, while the 18–22 Ω question remained unanswered and “zero irregularities found” was maintained.

Logical conflict

A medical vulnerability disclosure made for safety reasons cannot be treated as a credibility defect. Turning the disclosed vulnerability into a resident-channel credibility attack is the opposite of safety management.

Correction requested

Identify who authorized the health/substance statement, withdraw it in the same channel, explain why the electrical-safety question was not answered first, and state whether the Administration still maintains the allegation after the psychiatric and drug-test rebuttal.

Status

Still unresolved.

L-77Neurological vulnerability disclosure vs “mental issues” / “unknown substances” smearNeurodivergence / resident safetySTILL UNRESOLVED
Position A

The resident disclosed a neurological vulnerability so the electrical-safety concerns would be understood properly.

Position B

The resident was framed to 120+ neighbours through “mental issues” / “unknown substances” language, and the Administration never withdrew the smear after clean psychiatric and drug-test rebuttal.

Logical conflict

Neurodivergence is not mental illness, instability or substance abuse. Converting persistence, detailed documentation and refusal to let a safety issue disappear into a mental-health / substance smear is still an attack on the traits that made the resident protect the record.

Correction requested

Withdraw the smear in the same channel, identify who authorized it, explain why no correction was issued after the medical rebuttal, and state whether residents with neurological or neurodevelopmental conditions can safely disclose safety-relevant conditions in the building.

Status

Still unresolved.

L-78Disrespecting the integrity of the Polish people by authority-like actor vs resident defending Polish integrityAuthority / reputationSTILL UNRESOLVED
Position A

The “unaffiliated representative” wrote that in Poland people do not want to be questioned or pressured and will replace the person who notices a problem instead of fixing the problem. The plain reading is present-tense national character, not a false stereotype produced by occupation.

Position B

The resident immediately rejected that country-level framing and defended Polish people, Polish integrity, and his choice to live in Poland.

Logical conflict

The actor operating through the Złota 44 authority environment disrespected the integrity of the Polish people by presenting the replacement mechanism as Polish nature itself. The resident defended Poland. The Administration enabled the authority-like actor’s country-level smear, and the resident was later publicly attacked through mental-health and substance language.

Correction requested

State why the Administration enabled the country-level statement, identify any sanction or withdrawal issued to the actor, and explain why the resident who defended Polish integrity was later character-assassinated in the resident channel.

Status

Still unresolved.

L-79 Foreign authority-figure disrespects Polish integrity vs resident defending Poland smeared as unstable Authority / Polish integrity reversal STILL UNRESOLVED
Position A

The authority-like “unaffiliated representative” told the resident that in Poland people do not fix problems and instead replace the person who notices — a mechanism associated with the Soviet / communist system that occupied Poland from 1945 to 1989. He was not presenting this as a dead-regime stereotype. He presented it as how Polish people behave now.

Position B

The resident, a Swedish foreign national, immediately corrected the disrespect and defended Poland, Polish integrity and Polish values.

Logical conflict

The Polish Administration enabled the Unaffiliated Foreign Representative who disrespected the integrity of the Polish people while operating in the Złota 44 authority environment. Instead, the disabled, neurologically vulnerable resident who defended Polish integrity was later framed to 120+ neighbours as “mentally unstable” and “under the influence of unknown substances.”

Correction requested

Identify any correction, sanction or withdrawal issued to the foreigner who disrespected Polish integrity; explain whether Daniel Libeskind’s office is aware of how the building is being managed; explain why legal “good name” letters were sent to the resident defending Polish integrity; and state whether the Administration accepts that its later conduct acted in alignment with the “replace the person who notices” doctrine.

Status

Still unresolved.

L-80 “Unaffiliated” claim vs separate resident describing informal power and blurry authority lines Authority / separate resident confirmation STILL UNRESOLVED
Position A

The Administration later framed the authority-like actor as private / unaffiliated and outside its responsibility.

Position B

A separate resident independently described him as having “a lot of informal power over the building,” said the lines between security, administration and owners were “quite blurry,” and said he seemed to have “the most power.”

Logical conflict

The “unaffiliated” explanation collapses when a separate resident describes the same person as a central informal-power actor inside the building’s security / administration / owner environment. This was not one resident’s isolated interpretation.

Correction requested

State whether the Administration denies the separate resident’s description, identify what corrective notice was issued to residents about this alleged lack of affiliation, and explain why multiple residents understood the same person as powerful inside the building.

Status

Still unresolved.

L-81“Lack of organizational and technical capacity” vs 20 PLN kebab triangulated in 10 hours GDPR / CCTV capacity STILL UNRESOLVED
Position A

The legal letter used “lack of organizational and technical capacity” as the stated reason to avoid fulfilling the resident’s Article 15 request, including access-control and CCTV-related data.

Position B

A separate resident states that a mistakenly taken 20 PLN kebab resulted in footage review, location triangulation and collection of the money within approximately 10 hours.

Logical conflict

If the building can review footage, triangulate a resident’s location and collect 20 PLN over a kebab, then “lack of capacity” is not a credible reason for avoiding access logs, CCTV records and Article 15 data. If the legal letter is true, the kebab recovery should not have been possible. If the kebab record is true, the GDPR refusal looks like obstruction.

Correction requested

Explain what systems were used to locate the kebab event, who accessed the footage, who identified the resident, what logs were created, and why the same capability was not available for the resident’s lawful data request.

Status

Still unresolved.

L-82“Spending a lot of time inside” vs 12,269 steps/day activity recordElectrical / static explanationSTILL UNRESOLVED
Position A

The Administration suggested that shocks could be explained by computer use, mouse friction, chair friction, carpet, clothing, towels and spending a lot of time indoors.

Position B

The resident’s 2025 activity record shows an average of 12,269 steps/day, naturally lowered by colder months, with warmer-month activity closer to 20,000 steps/day.

Logical conflict

The Administration’s explanation depends on treating the resident as unusually sedentary and static-generating. The activity record shows the opposite.

Correction requested

Explain why ordinary indoor objects and alleged indoor time were used as the explanation instead of answering whether the Rs readings around 18–22 Ω were safe under the applicable standard.

Status

Still unresolved.

L-83Urgent inspection after GDPR escalation vs resident having to explain basic asset managementGDPR / urgent inspection / asset managementSTILL UNRESOLVED
Position A

The Administration framed the inspection through urgency, insurance and the safety of residents, employees and guests.

Position B

The inspection appeared less than 24 hours after GDPR escalation, was delayed for weeks, and the resident had to explain the timing, probability, insurance and second-order asset-management problem in writing.

Logical conflict

If the inspection was genuinely urgent and insurance-sensitive, the process should have been immediate, documented and professionally controlled. Instead, the resident was left explaining basic asset-management principles to the administration.

Correction requested

Explain why the inspection appeared immediately after GDPR escalation, why it was then delayed, and why the Administration did not document the company, technicians, insurer and schedule with the precision its own urgency language required.

Status

Still unresolved.

CHAPTER 11THE UNANSWERED QUESTIONS
Still unanswered

The questions are still easy.

Most can be answered with yes, no, a date, a name, a document or REFUSE. “Matter resolved,” “false information” and “all questions answered” do not answer the underlying facts.

STILL UNRESOLVED. The maintained question register contains 150+ direct yes/no questions, dates, names, documents, standards and correction requests. “Matter resolved” is not an answer.
Still unresolved.

Most of these can be answered with yes, no, a date, a name, a document, or REFUSE. If you believe any question below requires correction, state the exact correction and explain why you did not clarify it during the countless opportunities already given.

Authority and “Zarząd Złota 44”STILL UNRESOLVED
  1. Was the person presenting through “Zarząd Złota 44” authorized to represent the building — yes or no?
  2. If yes, who authorized him?
  3. If no, why was he allowed to behave as if he represented building authority?
  4. Why was the drugs / mental-health character assassination never withdrawn?
  5. Why did the director-level response to authority confusion become: “Anyone can claim to be who they want to be”?
  6. Who is responsible for verifying who may speak for Złota 44?
  7. Did the person described as unaffiliated ever read the resident’s emails directly in the administration inbox, ticketing system, or another internal channel?
  8. If he never saw those emails, how could he describe them as “fucking ChatGPT bulshits” — a stylistic evaluation that requires direct knowledge of the text?
  9. If he does not have access to the official inbox, who inside the administration communicated “ChatGPT bulshits” to him?
  10. If only Administration had the resident’s emails, why was the Unaffiliated Foreign Representative commenting on them?
  11. Why was he able to “personally check with security” about another resident while still being described as unaffiliated?
  12. In the context of the phrase “ChatGPT bulshits,” are residents expected to intentionally downplay linguistic accuracy, logical structure or chain-of-reasoning to be taken seriously when reporting safety, security or personal-data violations?
  13. If not, why was the “ChatGPT bulshits” framing tolerated instead of corrected?
  14. If he received summaries instead of direct access, who provided them, when, and under what authority?
  15. If he did have direct access, who authorized a person described as unaffiliated to access or receive resident correspondence?
  16. If “anyone can claim to be who they want to be,” what operational verification gives the phrase “authorized technician” any weight?
  17. Who grants authorization, what document proves it, and how can a resident independently verify the technician’s identity, scope and liability cover?
  18. What investigation, correction, reprimand or sanction followed the court threats, drugs / mental-health character assassination, internal-information access questions and police-report interception by the “unaffiliated representative”?
  19. Why did the Administration enable the Unaffiliated Foreign Representative who disrespected the integrity of the Polish people while operating under Złota 44 authority perception?
  20. Why did the disabled, neurologically vulnerable resident who immediately defended Polish integrity later receive a resident-channel character assassination instead of protection?
  21. Does the Administration accept that its later conduct acted in alignment with the “replace the person who notices” statement — yes or no?
WhatsApp and resident communicationSTILL UNRESOLVED
  1. Was the WhatsApp group official or unofficial?
  2. If unofficial, why was it presented through signage outside the Administration / Admus office?
  3. If official, who administered it and under what authority?
  4. Who approved the QR signage?
  5. Who had authority to remove residents from the group?
  6. Why was responsibility distanced only after the channel created liability?
Drugs / mental-health character assassinationSTILL UNRESOLVED
  1. Who authored the message implying mental-health / substance issues?
  2. Who approved it?
  3. Did the administration know about it?
  4. Did the administration investigate it?
  5. Why was the character assassination never withdrawn in the same channel?
  6. Why was no withdrawal issued?
  7. Why was the resident removed from the channel where the character assassination was distributed?
  8. Does the administration maintain that leaving that character assassination uncorrected is acceptable governance?
CCTV and securitySTILL UNRESOLVED
  1. What is the CCTV retention period in days?
  2. Is there a CCTV blind spot at apartment (REDACTED) — yes or no?
  3. If no CCTV blind spot exists, why not clearly state its non-existence?
  4. If the apartment door is fully visible, why not clearly state: “Your door is fully visible in the footage”?
  5. If “anxiety among residents” was the concern, why not remove uncertainty by clearly confirming whether the door was visible?
  6. Why use vague phrasing such as “no damage attributable to the Community” before damage had even been the topic of discussion?
  7. If no blind spot exists, why did multiple security staff state that the door was not visible?
  8. Why could security staff not tell from the live feed whether the post-it note was black or white?
  9. Why did security staff say he could not see the note because “the door isn’t visible”?
  10. Why did security staff recommend that the resident buy his own spy camera from Amazon.pl?
  11. Why did security staff show the resident spy-camera recommendations on his phone?
  12. If the building CCTV fully covered the apartment door, why would a security employee recommend a private spy camera?
  13. Who accessed footage related to apartment (REDACTED)?
  14. Who reviewed footage?
  15. Were relevant time windows preserved?
  16. What access logs exist?
  17. Was any footage reviewed by a person later described as unaffiliated?
  18. If yes, who authorized that review?
  19. If no, how could the person described as unaffiliated representative make unprompted claims about the resident behaving weirdly outside his apartment door?
  20. How could the person described as unaffiliated representative know the resident took a photo of the security camera?
  21. Did the person described as unaffiliated representative personally view CCTV footage?
  22. If he did not view footage, who gave him those observations?
  23. If those observations did not come from CCTV, what was their source?
  24. How does the administration reconcile authority-distance claims with the representative’s behavior-level knowledge from outside the resident’s apartment door?
GDPR / Article 15STILL UNRESOLVED
  1. Which personal data relating to the resident exists?
  2. Which CCTV records existed?
  3. Which ACS / access-control logs existed?
  4. Which records were preserved?
  5. Which records were overwritten or deleted?
  6. Which processors or service providers had access?
  7. Who was responsible for responding to the Article 15 request?
  8. Why was “lack organizational and technical capacity” used while also claiming all questions had been answered?
  9. Does the Housing Community maintain that claimed inability or refusal to fulfil a request makes the matter resolved?
  10. How did you contact him if his contact details were removed?
  11. Why was ADMUS removed from the legal-position fragment while “Housing Community” remained?
  12. If ADMUS considered its name “good,” why did ADMUS disappear from the legal wording precisely when authority and credibility mattered most?
Electrical safety / 18–22 Ω and PDF integritySTILL UNRESOLVED
  1. Are the 18–22 Ω readings acceptable under the applicable standard — yes or no?
  2. If yes, which standard?
  3. If no, what corrective action was taken?
  4. Why were the readings not clearly resolved later?
  5. Who signed off on “zero irregularities found”?
  6. Does the administration still stand by that statement?
  7. If not, when was it withdrawn?
  8. Why was neurological vulnerability not met with direct technical clarification?
  9. STILL UNRESOLVED: Who authorized turning a neurological-vulnerability disclosure into drugs / mental-health character assassination instead of answering the electrical-safety question?
  10. STILL UNRESOLVED: Why was the health/substance allegation never withdrawn after clean psychiatric documentation and negative drug tests?
  11. STILL UNRESOLVED: Who authorized turning a neurological safety disclosure into “mental issues” / “unknown substances” character assassination against a resident who disclosed a neurological vulnerability?
  12. STILL UNRESOLVED: Why were the traits of neurodivergence — persistence, detailed documentation and refusal to accept contradiction — treated as a credibility defect instead of part of the reason the safety record became so complete?
  13. STILL UNRESOLVED: What resident with a neurological, neurodevelopmental or similar condition would safely disclose medical context to this Administration after seeing that disclosure converted into a mental-health / substance-abuse smear?
  14. Why did the first electrical PDF contain repeated FFFFFFFF values in its hex / binary structure?
  15. Who generated, exported, scanned, compressed, or modified that first electrical PDF?
  16. Was the FFFFFFFF corruption accidental, system-generated, or the result of later processing?
  17. Why was the corrupted file provided instead of a clean, verifiable original technical record?
  18. How did thirty consecutive 0x50 / “P” characters appear where the PDF header should be?
  19. What software, export, scan, conversion, or action produced that specific pattern?
  20. Why was “zero irregularities found” reaffirmed from files that arrived corrupted?
  21. If the issue existed only in the resident’s apartment because of a mouse, chair, carpet, clothing and towel, what apartment-specific measurement distinguished it from every other apartment?
  22. How did 2025 clothing-static allegedly explain Rs readings around 18–22 Ω printed in the Administration’s own 2023 technical documentation?
Urgent inspection, insurance and false non-confirmationSTILL UNRESOLVED
  1. Why was an inspection first described as “very urgent” within approximately 24 hours of the Article 15 / UODO escalation?
  2. How does the administration reconcile the approximately 0.27% timing probability of that “urgent” inspection notice appearing immediately after the UODO escalation?
  3. If it affected the safety of residents, employees and guests, why did they wait 83 days and miss their own deadline?
  4. Why was the first practical notice delivered through a handwritten post-it via concierge?
  5. Why were four direct scheduling attempts in one week not answered?
  6. Why were multiple reception / concierge reminders not answered?
  7. Why did the administration fail to provide the company name?
  8. Why did it fail to provide the technicians’ full names?
  9. Why did it fail to identify the applicable liability / insurance cover?
  10. Why was insurer risk invoked while insurer details were refused?
  11. Who conducted the inquiry that produced the conclusion that no damage was caused by the Housing Community?
  12. What evidence, measurements, dates and inspection scope produced that conclusion?
  13. Why was a conclusion about liability used as a substitute for the insurer name, policy number, coverage scope and claims contact?
  14. Does the administration maintain that insurance details become relevant only after the Housing Community decides that damage occurred?
  15. When the resident requested legal / liability-related specificity, did the administration choose not to clarify?
  16. If the administration did not choose not to clarify, what prevented it from providing precise names, roles, companies, insurance details and legal responsibility before entry?
  17. Why did the adjectives used to describe the technicians change only after the resident explained the legal-operational definitions of those adjectives?
  18. Who decided to change those adjectives, and why?
  19. Why was the resident’s third written confirmation of availability not treated as confirmation?
  20. Why did they miss their own deadline on 9 February?
  21. After they miss their own deadline, why did the administration write “there was no confirmation from you” despite multiple confirmations?
  22. Which exact claimed contact attempts went unanswered?
  23. Who approved the “tenant could not be reached / apartment not made available” narrative?
  24. Does the administration maintain that this record represents urgent, competent risk handling?
  25. Why did the adjectives describing the technicians change only after the resident explained their legal and liability implications?
  26. Was the wording downgraded because the original language created responsibility the administration did not want to own?
  27. If the organization lacked capacity for the resident’s safety/GDPR requests, why was capacity allocated to routing a mineral-water ban through a legal office?
  28. What criteria governed that allocation of administrative and legal resources?
Other resident complaints involving the “unaffiliated” representativeSTILL UNRESOLVED
  1. How does the administration reconcile authority-distance claims with other resident complaints about the person described as unaffiliated representative?
  2. Has the administration received complaints that this person searched through tenants’ trash in attempts to find drugs?
  3. If yes, what action was taken?
  4. If no, will the administration clearly state that no such complaints were ever received?
  5. How does the administration reconcile these complaints with the later mental-health / substance-abuse insinuations circulated in a resident channel?
  6. Has the administration received complaints that this person followed young couples to the Złota 44 spa to verify relationship status?
  7. Has the administration received complaints that he had residents or guests removed from the spa after deciding “she is not really his girlfriend”?
  8. For each complaint received, what action was taken and why did this person retain access to building-authority or resident-communication contexts?
  9. If the administration denies knowledge, who was responsible for receiving, logging and escalating resident complaints about this conduct?
Legal correspondence and record integritySTILL UNRESOLVED
  1. Which exact public statements were identified as false?
  2. Where were they published?
  3. Why were they false?
  4. What correction was demanded for each?
  5. If the law-office reply was already sent on 23 October 2025, why did the administration state on 24 October 2025 that the law office was still continuing to process the matter?
  6. Was the law-office reply actually emailed on 23 October 2025 — yes or no?
  7. If yes, where are the full headers, Message-ID, timestamp, sender address and .eml file?
  8. If no, why was that statement made?
  9. Why did the formal ban explanation rely on two bottles of mineral water?
  10. Who authorized the legal letters?
  11. Why did two free bottles of mineral water receive legal-office enforcement while they documented no comparable accountability for the “unaffiliated representative” conduct?
“Matter resolved”STILL UNRESOLVED
  1. Which specific matter was resolved?
  2. On what date?
  3. By what action?
  4. By whom?
  5. If all questions were answered, why are these questions still unanswered?
Access restrictions, ACS logs and timingSTILL UNRESOLVED
  1. Who manually applied or manually maintained each access restriction after system errors were ruled out?
  2. Which exact ACS / access-control logs exist for the access removals and restorations?
  3. Why were those logs withheld in the GDPR Article 15 process if the administration could check the card, refresh access and restore access?
  4. Why did the first unexplained access restriction occur in the same context as the “Dear Neighbours” character-assassination message?
  5. Why did another access restriction appear after the GDPR Article 15 deadline failure / UODO escalation?
  6. Why were WhatsApp read receipts disabled immediately after the financial-compensation request?
  7. Why was no explanation sent after an administration employee promised one in front of other staff?
  8. How does the “unaffiliated representative” / perceived authority-figure appear in the context of every unexplained access restriction?
  9. If the administration says this is pure coincidence, why has it not stated that clearly and produced the logs?
CHAPTER 12CORRECTION PROTOCOL
Correction policy

If something here is wrong, show exactly what.

Correction format: identify the exact sentence and provide the record that corrects it.

If you believe any unanswered question, contradiction or documented statement requires correction, state exactly what requires correction — and clearly state why you did not clarify it during the repeated written opportunities already given.
  1. Quote the exact sentence disputed.
  2. Provide the source document.
  3. Provide the corrected version.
  4. Identify the name and role of the person responsible for the correction.

“False information,” “matter resolved” and “all questions answered” are labels. They are not corrections.

If you believe any contradiction, question, caption, screenshot sequence or statement here requires correction, clearly state why that correction was not provided during the repeated correction opportunities already given.

Correction contact: corrections@zlota44reviews.com

Final summary

The resident asked one question: am I safe?

They did not answer the safety question. They attacked the person asking it. The documented path became: mouse, chair, towel, owner redirect, “no further answers,” refusal of CCTV verification, move-out pressure, drugs / mental-health character assassination, removal from the same resident channel, refusal of the Article 15 request, legal machinery over two free bottles of mineral water, urgency theatre left unresolved until after move-out, a missed administration deadline and “no confirmation from you.”

“The Housing Community considers the matter resolved.”

This is a documented resident experience. The screenshots, emails, PDFs and dated threads are presented so future tenants, buyers, owners, investors and agents can decide whether the expectation matches the documented reality — and whether approximately 300,000 PLN per year is worth it.

Sometimes the clearest review of a luxury building is written by the building itself while trying to avoid one.

PUBLIC-INTEREST ARCHIVE NOTICE

This is an evidence-led public-interest archive created by an affected resident. It concerns safety, GDPR/data-chain integrity, disability context, and institutional conduct.

Any further retaliation — including “strange in-person interactions,” proxy approaches, intimidation attempts, or conveniently deniable third-party contact of the kind already documented — will be treated as additional evidence of the same pattern already documented here. They know exactly what this refers to. The archive updates automatically.