The People We Can See but Fail to Protect

matt klee

Hatched by matt klee

Aug 26, 2026

11 min read

86%

0

What if the central problem in modern life is not that we lack information, but that we have become very good at recognizing the wrong things?

A company can assemble more than 200 million buyer and company profiles from public records, third party providers, and the wider internet. Artificial intelligence can extract, normalize, categorize, and refresh those profiles. Human reviewers can check whether the information is accurate and relevant.

Yet a woman can be visible to the world as an Olympic athlete, a neighbor, a former partner, and a person with a known history, while the danger around her remains socially invisible until it is too late.

These facts seem to belong to different moral universes. One concerns commercial intelligence. The other concerns intimate violence and the death of Rebecca Cheptegei, who was set alight by her former boyfriend days before she died. But together they expose a deeper question:

What is the value of visibility when a system can identify a person, but cannot recognize what matters about her life?

The question is not whether data is powerful. It plainly is. The question is whether our systems of attention are designed to convert knowledge into protection, responsibility, and action, or merely into prediction, persuasion, and profit.

The difference between being known and being understood

Modern data systems are built around a specific kind of knowing. They seek attributes that can be collected, compared, and put to work: a company’s industry, a buyer’s role, a likely purchasing interest, a web signal, a recent change in behavior. Their achievement is not simply gathering facts. It is making scattered facts legible to an institution.

This process has three stages. First, information is gathered from many places. Second, artificial intelligence extracts and standardizes it. Third, the resulting profile is used to guide a decision. A messy digital world becomes a clean representation that an organization can act upon.

That architecture is useful because institutions cannot respond to everything. A sales team cannot study every company manually. A hospital cannot treat every patient with the same protocol. A public agency cannot investigate every signal with equal intensity. Classification helps allocate attention.

But classification always leaves something out. A person is converted into a set of fields, and the fields that do not serve the system’s purpose often disappear. In a commercial profile, a buyer may be represented by role, industry, company size, and intent. In a social setting, a woman at risk may be reduced to a private dispute, a relationship problem, or an unfortunate event. In both cases, the crucial issue is not whether information exists somewhere. It is whether the system has a category for its significance.

This is the difference between data visibility and human visibility.

Data visibility means that an entity can be located, described, scored, and retrieved. Human visibility means that a person’s vulnerability, dignity, and claims on other people’s attention are recognized. The first is a technical achievement. The second is a moral and institutional one.

A profile can be highly complete while being profoundly incomplete. It may contain hundreds of relevant attributes and still fail to include the one fact that should change what happens next.

The dangerous gap between signal and meaning

Data enrichment promises freshness, accuracy, and relevance. Those are sensible goals. Old or incorrect information produces bad decisions. Human quality assurance improves the chances that automated systems will not simply amplify noise. Yet accuracy alone cannot answer the most important question: accurate for what purpose?

A fact is never relevant in the abstract. It becomes relevant within a decision.

Knowing that a company has recently expanded may be relevant to a seller. Knowing that an executive has changed roles may be relevant to a recruiter. Knowing that a person has repeatedly reported threats, coercive behavior, or escalating violence should be relevant to a protection system. But relevance depends on whether an institution has been designed to see the person as more than a transaction, a case number, or a private problem.

Imagine a smoke detector that perfectly identifies the chemical composition of the air but has no rule for sounding an alarm. Its readings may be accurate. Its sensors may be sophisticated. Its database may be continuously updated. It is still a failure if it cannot translate a signal into an appropriate response.

This is the central weakness of many information systems: they optimize the chain from collection to classification, but not the chain from recognition to responsibility.

The distinction matters in intimate violence because warning signs are often distributed across contexts. A threat may be mentioned to a friend. A frightening incident may be shared with a family member. An injury may appear in a medical record. A change in routine may be noticed at work. A previous complaint may exist in a police file. No single observation necessarily contains the whole truth. The danger emerges through accumulation, pattern, and escalation.

Commercial data enrichment is designed to connect fragments into a useful profile. That same conceptual capability could, in principle, be applied to public safety. But there is a profound ethical difference between enriching a profile to improve a sale and connecting signals to prevent harm. One asks, “Is this person likely to buy?” The other asks, “Is this person in danger, and who has a duty to act?”

The first can be governed by conversion metrics. The second cannot be reduced to a score without risking another form of dehumanization.

Why systems notice value before vulnerability

Institutions tend to become highly perceptive where attention produces measurable returns. Businesses invest in data infrastructure because better information can improve revenue, retention, and efficiency. The benefits are visible in dashboards. They can be tested against outcomes. Budgets follow them.

Protection systems operate under different conditions. Success often looks like an event that never occurs. A crisis prevented does not produce a dramatic headline or a clear return on investment. A survivor who remains safe may leave no obvious trace of the intervention. Prevention is therefore structurally difficult to measure, even when it is immensely valuable.

This creates a perverse asymmetry. Systems become more sophisticated at identifying commercial intent than at identifying escalating human danger. They can infer that a buyer is researching a product, but institutions may still treat repeated threats as isolated incidents. They can refresh a corporate record from many sources, while people in a vulnerable relationship may be forced to repeat their story to every agency separately.

The problem is not simply technological neglect. It is a hierarchy of institutional attention.

A society reveals what it values not only by what it talks about, but by which patterns it is willing to organize itself to notice.

The tragedy surrounding Rebecca Cheptegei should not be used as evidence that any particular data tool could have predicted or prevented her death. That claim would be both irresponsible and impossible to establish from the facts available. The deeper lesson is more demanding: when violence is treated as a series of private episodes rather than a pattern with escalating consequences, visibility arrives only after irreparable harm.

This is where the comparison with enriched commercial profiles becomes unsettling. The technical world has learned to ask whether fragments scattered across the internet can be assembled into a timely and actionable picture. The social world must ask why similar seriousness is so often absent when the fragments concern threats, control, stalking, or violence.

The answer cannot be to create a universal database of private lives. That would introduce grave risks, including surveillance, retaliation, false accusations, and the misuse of sensitive information. The answer is to build contextual systems of care: systems with narrow purposes, strict access controls, trained professionals, survivor consent wherever possible, independent oversight, and clear escalation pathways.

The point is not to know everything about everyone. It is to ensure that the people entrusted with responding to danger can recognize patterns without making vulnerable people carry the entire burden of assembling the evidence themselves.

From enriched profiles to responsible institutions

A useful mental model is to separate four layers of institutional intelligence.

Layer one: detection. Something has been observed. This could be a threat, a repeated unwanted contact, an injury, a change in behavior, or a report from someone close to the person at risk.

Layer two: interpretation. The observation is placed in context. Is it isolated, or part of an escalating pattern? Is there a history of coercion? Has the person expressed fear? Are there weapons, stalking, financial control, or attempts to sever social support?

Layer three: duty. Someone must be responsible for deciding what the information requires. A signal without an accountable owner is merely stored anxiety.

Layer four: intervention. The institution offers a proportionate, survivor centered response: emergency protection when necessary, safe housing, legal assistance, counseling, transport, financial support, or sustained follow up.

Most organizations are strongest at the first layer and weakest at the third. They collect reports but do not connect them. They connect them but do not assign responsibility. They assign responsibility but offer no resources. The result is an information system that can describe danger without changing its trajectory.

The same framework applies beyond violence. In education, a student may be visible through attendance data but invisible in the context of caring responsibilities or bullying. In health care, a patient may be visible through test results but invisible as someone unable to afford transportation or medication. In the workplace, an employee may be visible through performance metrics but invisible as someone facing harassment or burnout.

The recurring error is to confuse a record of a person with a relationship of responsibility toward a person.

A company profile exists to help an institution do something with a business. A public safety record should never exist merely to describe a vulnerable person. Its purpose must be tied to protection, and its design must be judged by whether it increases agency and safety rather than exposure.

That requires a different standard from ordinary data quality. We need at least five tests:

  1. Purpose limitation: Is the information collected for a clearly defined protective purpose?
  2. Contextual integrity: Is the information interpreted by trained people who understand coercion, culture, and the possibility of retaliation?
  3. Survivor agency: Does the system give the person meaningful choices rather than turning her life into an automated case?
  4. Accountable escalation: Is a named institution responsible for acting when risk increases?
  5. Feedback and repair: Can errors be corrected, harmful decisions challenged, and failures publicly examined?

These tests protect against two opposite dangers. The first is neglect, where warning signs disappear into disconnected offices. The second is overreach, where data collection becomes surveillance and the person at risk loses control over her own identity.

What individuals and institutions can do now

The most immediate lesson is not that everyone needs more data. It is that everyone needs better practices for turning observations into care and accountability.

For individuals, this means taking disclosures seriously without demanding courtroom proof from someone in danger. Preserve messages and records when doing so is safe. Ask what support the person wants. Avoid confronting a threatening partner in ways that may increase risk. Help connect the person with specialized domestic violence services, emergency support, legal assistance, or trusted local organizations.

For institutions, the practical changes are more structural:

  • Create one clear pathway for reporting concerns, with trained staff who know how to assess escalation.
  • Treat repeated low level incidents as potentially significant when they form a pattern.
  • Record context, not just events. “Argument at home” is not an adequate description if the surrounding facts indicate coercion or fear.
  • Make responsibility explicit. Every report should have a next step, an owner, and a time for review.
  • Measure prevention, continuity of support, and survivor safety, not merely the number of reports processed.
  • Minimize sensitive data and restrict access. More information is not automatically better protection.

Key Takeaways

  • Visibility is not protection. A person can be known to many systems and still be unseen in the ways that matter.
  • Accuracy requires a purpose. A perfectly correct fact is useless, or dangerous, if an institution does not know how it should change behavior.
  • Patterns matter more than isolated events. Escalating harm often appears across several small signals rather than one decisive incident.
  • Every warning needs an accountable owner. Detection without responsibility creates the appearance of action without its reality.
  • Good safety systems increase agency. They help vulnerable people make safer choices and access support. They do not turn them into objects of surveillance.

The future will contain more profiles, more automated inference, and more systems capable of connecting fragments. That future is not automatically more humane. Intelligence can be used to target a customer, rank a prospect, flag a risk, or justify inaction. The technology does not decide what deserves attention. Institutions do.

The most important question, then, is not whether we can enrich the data surrounding a person. It is whether we can enrich the human context surrounding the data: the history, the vulnerability, the relationships, the duties, and the possible consequences of ignoring a pattern.

Rebecca Cheptegei should not be remembered only as a name associated with a terrible act. Her death forces a broader reckoning with the limits of a society that can make people legible for commerce while leaving danger illegible in private life.

To see someone fully is not to collect every fact about them. It is to recognize which facts create a duty to respond. The mature information society will be the one that finally understands this distinction: the highest form of knowledge is not prediction. It is responsible attention.

Sources

← Back to Library

Hatch New Ideas with Glasp AI 🐣

Glasp AI allows you to hatch new ideas based on your curated content. Let's curate and create with Glasp AI :)

Start Hatching 🐣