Cyberpunk surveillance is not only a camera on a wall. It can be a collection of ordinary transactions: opening a door, buying food, receiving pay, or asking for help. When those records are joined, an institution may know far more about a person than any single observer could. The story begins when someone can use that knowledge to influence another person's choices.
Collection is not the whole question
An identity system may make a city easier to use. It may also leave people unable to correct mistakes. Imagine a worker whose travel record says they missed a shift they actually attended. If the same record controls wages, housing, and future work, a small error becomes a large penalty. The problem is not a glowing interface; it is the absence of an effective appeal.
Surveillance also changes behavior before any punishment occurs. People who know they are watched may avoid meeting friends, asking questions, or reporting a problem. A cyberpunk story can show this pressure through a character's route across a city rather than a speech about privacy.
A score can hide a chain of decisions
Suppose a resident receives a low reliability score. The number might combine a mistaken address, a late payment caused by an outage, and a visit to a district the system labels risky. The score looks simple because the people and rules behind it have been compressed. Asking for the underlying entries can reveal which parts are factual errors and which are judgments built into the model.
Even a correct record can be used unfairly. A person may really have visited that district, yet the visit need not justify denying them work. Separating accuracy from legitimacy keeps the story from suggesting that better data alone solves surveillance.
Who may read the record?
Ownership, access, and correction are separate powers. The operator of a system may collect data; an employer may receive only a score; a resident may see neither the original record nor the rule that produced it. Tracing these powers makes an imagined network feel concrete.