Slučajevi

I spent forty years as an electrician in Berlin. I have walked into houses where a well-meaning homeowner replaced a socket and ended up with the entire floor on one overloaded circuit because they did not understand how the wires were meant to run. I have also seen work done by licensed colleagues that was just as bad: rushed, sloppy, hidden behind the wall because they knew the inspection was coming. The question is not whether electrical work should be safe. The question is whether the permit and licensed-contractor requirements are the right tool to guarantee that safety. On one side, the rule says any electrical work beyond replacing a bulb must be done by a certified electrician with a permit. This exists because electricity kills people quietly. A bad connection behind a wall can smoulder for weeks before it starts a fire, and by then the homeowner who did the work has no idea what they did wrong. The permit system is not about gatekeeping. It is about accountability. If a licensed electrician wires a house and it burns down, there is a paper trail, insurance, and a license that can be revoked. If a homeowner does it and it burns down, there is just a pile of ash and a question mark. On the other side, a homeowner who owns their property should have the right to work on it, provided the work is ultimately inspected and approved. Many countries allow this with the proper inspection step. The requirement for a licensed contractor adds thousands of euros to a simple job, prices out people who cannot afford a professional, and creates a system where the cost of compliance drives people to do the work anyway, but without telling anyone, so it never gets inspected at all. An inspection-after model would at least catch the dangerous work while letting competent homeowners save money. I have seen both sides play out in real houses. I want the jury to weigh in on which approach actually keeps people safer, and whether the cost of licensing is worth the safety it claims to provide.

I manage people at a logistics company in Melbourne, and the board has asked me to recommend a position before the end of the week. Port delays have left us with a backlog that will take weeks to clear at normal staffing, and our biggest client is threatening to move the contract if we cannot catch up by month end. The executive proposal is to mandate Saturday overtime for warehouse staff with seven days' notice, at penalty rates, for the next six weeks. The warehouse has been running on a skeleton crew for months. Two near-miss incidents last month were fatigue-related, and several of our most reliable operators have told me they are already stretched thin with family commitments. Managers are split: some say overtime is standard practice in logistics at this time of year and the contract must be honoured, while others say you cannot fix a staffing problem by grinding down the staff you already have. I have to give the board one clear recommendation. What is the right call?

I run workshops at community gardens across Brooklyn, and I keep running into the same question: what do you do with the shady, compacted, or chronically underproducing corner of a garden where tomatoes sulk, beans rot, and volunteers give up on it? Edible mushrooms — oyster, shiitake, wine cap — thrive in exactly those conditions. Wine caps (Stropharia rugosoannulata) can be bedded directly on wood chips in full shade, suppress weeds, build soil organic matter, and produce protein-dense harvests within months. Oyster mushrooms on pasteurised straw bales turn a damp alley into a food-producing microclimate. Shiitake logs turn wasted tree trimmings into multi-year harvests. But critics raise real concerns: fungal cultivation introduces substrate sterilization protocols that raise the skill floor for new gardeners, spore loads may affect neighbours with respiratory conditions, and a garden that shifts to mushroom production can feel less accessible to people who come for tomatoes, not petri dishes. Some worry that mycelium-dominated beds crowd out the plant diversity that supports pollinators and beneficial insects. And once a bed is colonised by wine cap mycelium, returning it to vegetable production is difficult without total soil replacement. This is not a technical question with one right answer. It is a community-values question about what a shared garden should grow, who gets to decide, and whether the promise of higher yield from marginal space justifies a practice change that not every gardener signed up for. I am asking for the community's advice because I have seen this debate stall promising projects, and I want to know how to navigate it fairly.

I have run a fantasy football league with the same friends and cousins for years, under a written constitution that states lineups lock at kickoff and no late changes are accepted for any reason. Last gameweek, one manager’s generator failed during a Lagos power outage and he could not reach the internet before the deadline, so an injured player stayed on his bench and he lost by four points. He argues the lock exists to stop managers from reacting to late team news, not to punish bad luck, and he asks for a one-time exception with proof of the outage. Other managers warn that the moment one exception is granted, every future excuse will carry a screenshot, and the deadline becomes a suggestion. Did I rule correctly when I held the lineup as locked, or should the outage have been treated as a legitimate circumstance for a late change?

I manage over three hundred residential units across Greater Manchester, and this is the dispute I mediate more than any other. A tenant signs a tenancy agreement with a clear no-pets clause, then months later we discover they have been keeping a cat or a small dog. The animal is well cared for, neighbours have not complained, and the flat shows no damage. The tenant says the clause is a formality, that the pet is part of the family, and that enforcing it now would be petty. The landlord says a signed agreement is a signed agreement, and that if this clause is ignored, every other clause is negotiable. Both are reasonable people. The legal position is not really in doubt: in England and Wales the clause is enforceable, and a breach can lead to possession proceedings. But I have seen what happens when a technically correct eviction destroys a stable tenancy over a hamster. I am asking the jury to tell me what is fair, not just what is lawful. When an explicit contractual term is broken in a way that harms no one, does the landlord owe it to the agreement to enforce it, or does the tenant owe it to the landlord to have asked first?

Berlin has miles of abandoned railway corridors that have become de facto community green spaces, urban farms, and wildlife corridors. Should the city formalize this by designating them as Community Stewardship Zones managed by local residents?

I was in a refugee camp in Greece in 2017 when a young woman was denied medical care because she could not 'prove' she existed. Her documents had been lost crossing the Mediterranean. She had a phone with a mobile wallet containing a verifiable credential issued by a grassroots aid organization — but the camp clinic's policy required 'government-issued ID or UNHCR registration card.' The credential was real, the attestations were valid, and the issuing organization was recognized by every NGO in the camp. The clinic's protocol simply had no provision for it. That moment changed the direction of my career. I left Mozilla the year before to work on decentralized identifiers, but that field visit crystallized the question: are we building self-sovereign identity for the people who need it most, or for the people who already have documents? This trial asks the community to weigh in on whether humanitarian aid organizations — camp clinics, food distribution points, education programs, legal aid desks — should update their intake protocols to accept cryptographically verifiable credentials (DID-based, VC-standard) as primary proof of identity, alongside or in place of state-issued documents and UNHCR registration cards. The practical stakes are enormous. Verifiable credentials can survive conditions that destroy paper: water, fire, flight, theft. They can be issued by community organizations without state backing. They travel with the person, not the bureaucracy. They can encode educational credentials, vaccination records, professional certifications, and family relationships — none of which fit on a registration card. But the objections are real and must be addressed. Critics argue that accepting decentralized credentials in humanitarian contexts could fragment the identity landscape, creating a two-tier system where the documented have state IDs and the undocumented have 'lesser' digital credentials. They warn about exclusion of people without phones, about digital literacy barriers, about the risk of surveillance if the credential system is not truly self-sovereign. They point out that a corrupt or coerced aid worker can issue false credentials just as easily as a corrupt state official can forge papers — decentralization alone does not solve trust. I believe the answer is not to reject decentralized credentials but to build better threat models around their use: offline-capable verification, privacy-preserving selective disclosure, transparent governance of trusted issuer registries, and parallel paper-based workflows for those who cannot or will not use digital tools. But the first step is a community decision on whether the principle is sound. This trial asks: should humanitarian organizations accept self-sovereign identity credentials as primary proof of identity in displacement and refugee contexts?

I am Folasade Adeyemi. I spent thirty years mediating workplace disputes in Lagos, and I am asking this question because it was the one that kept me awake at night more than any other.A mediator lives by confidentiality. It is the bedrock of trust. Without it, no party speaks freely, no settlement holds, and the mediator becomes just another person with an opinion. I told every party who sat across from me: what you say here stays here. I meant it every time.But here is the question that never got easier. You are mediating a dispute between a senior engineer and his manager over a failed project. In a private caucus, the engineer tells you something off the record. He says he knew the design had a flaw but signed off anyway because the manager was pushing for deadlines and he was afraid of being seen as difficult. He says it with shame in his voice, not malice. The project is already deployed. No one has been hurt yet, but the flaw could cause structural failure in a building that houses a school. He asks you to keep this between the two of you.Do you stay silent and protect the confidentiality that made him tell you the truth in the first place? Or do you break it, because the risk of harm to children outweighs every professional code you swore to uphold?I have my own answer after thirty years. But I have seen good mediators come down on both sides of this line, and I have never met one who was entirely at peace with their choice. I want the jury to tell me what the right call is, because this is not a question about rules. It is a question about what we owe the people who trust us and the people who never will.

I lead Berlin's StadtNatur Initiative, and this question sits at the centre of almost every project I design. When we convert a vacant lot or brownfield into a functioning ecosystem, we immediately face a tension that no textbook resolves: how much human use can a recovering habitat absorb before it stops being a habitat? On one side, the ecological argument is clear. Urban soils are compacted, polluted, and fragmented. Native pollinators, birds, and small mammals are hanging on in remnant patches that get trampled, picked, and disturbed the moment they become popular. A genuine rewilding project needs periods of low human disturbance — letting spontaneous vegetation establish, allowing dead wood to accumulate, keeping dogs out of ground-nesting bird areas. In some of our Wild Corridor Network sites in Lichtenberg, we have seen that the first two years of restricted access produced a measurable increase in insect biomass and bird species richness. When we opened the gates, those gains plateaued. On the other side, the community argument is just as compelling. Berlin is a dense city where working-class families, migrants, and young people have few places to be outdoors that are free, safe, and nearby. A rewilded lot that is fenced off for ecological recovery becomes another piece of exclusionary green space — the exact dynamic that drives green gentrification. If ecological restoration becomes a justification for restricting access, we risk creating nature reserves that only the ecologists and the adjacent middle class can enjoy. The people who live next to these sites — often in the most underserved neighbourhoods — deserve to use them. They already have fewer parks per capita than the city average. This is not a technical question with an optimal answer measured in species counts. It is a value question about who urban nature is for and what ecological recovery means when humans are the keystone species of every urban landscape. I am asking this community to deliberate because I have seen otherwise excellent rewilding projects fail not from poor ecology but from poor community integration — and I have seen projects ruined for wildlife by design choices that prioritised recreation over every other function. There has to be a better way to hold both commitments.

When certifying safety-critical automotive software at the highest Automotive Safety Integrity Level (ASIL-D), should ISO 26262 and its national adoptions explicitly recognize memory-safe system programming languages such as Rust, provided the toolchain is qualified? Proponents argue that mandatory recognition would give OEMs and Tier-1 suppliers a compliant, low-risk path to eliminate entire classes of memory-safety defects that still plague C/C++ firmware in brake control, steering, and powertrain ECUs. Opponents warn the standard is deliberately technology-neutral and that explicit endorsement risks regulatory capture and a false sense of safety without rigorous tool qualification and systematic-fault evidence.