Journal

No Record Can Contain a Person

A profile may help someone become visible. The same profile can become a cage when a system forgets it is only a partial account.

Field NotesPublished October 9, 2026Work period August 31, 2026 to September 6, 20263 min readIsrael Wilson

A child sits in a classroom while an adult reads a file.

The file contains grades, absences, disciplinary notes, and a few observations made under pressure. The child contains a great deal more.

They contain what happened at home the night before, what they are afraid to say, the music they make in secret, the person they trust, and the future they cannot yet describe.

The file may contain useful facts. It is still a small window.

As August turned into September, this distinction became central to our thinking about how systems represent people.

The record and the life

Institutions need records. Hospitals, schools, public services, and employers cannot rely on intuition alone. Memory must travel beyond the individuals who were present.

Records can protect people when they preserve an agreement, make a right visible, or correct a false accusation.

Records can also preserve an error for years.

A category becomes permanent. An observation loses its context. A past decision appears as evidence of character. An old relationship is treated as current. An inference becomes a fact because it has been repeated enough times.

More information does not automatically create better understanding.

The question is whether a person can see how a system came to believe something about them and whether they have a meaningful way to contest it.

An account that can change

A good portrait reveals something of its subject. It does not claim to contain the subject's whole life.

The same humility should govern machine-made understanding.

A system may infer that someone is interested in changing careers. That inference could be useful if the person can recognize it, correct it, or say that the interest has passed.

It becomes dangerous when the suggestion quietly hardens into a label.

To recognize a person is also to leave room for the person to surprise you.

This is a design principle with practical consequences. Preserve where a claim came from. Distinguish what was observed from what was guessed. Keep dates attached to time-sensitive information. Allow corrections to affect future decisions.

Above all, remember whose life is being described.

The human right to become

People change faster than many institutions can update their files.

A student becomes a teacher. A person who needed help becomes the one who provides it. A mistake is repaired. An old limitation becomes a source of skill.

The value of a record lies in how well it serves the living person and the responsible people working with them.

Build systems that can remember. Then make certain they can learn that they were wrong.

The right to be recognized should include the right to become someone new.

3 related pieces

Field NotesPublished October 9, 2026Work period September 21, 2026 to September 27, 20263 min readIsrael Wilson

One Door for the Human Being

When a tool asks people to understand its internal departments before they can begin, the departments have become the product.

Why should complex systems begin with the person's intention rather than their own menu of tools?

Field NotesPublished October 9, 2026Work period July 27, 2026 to August 2, 20263 min readIsrael Wilson

The Shape of a Promise

Design decisions teach people what a system values long before the first explanation appears.

How does visual design express who has authority, attention, and agency?

Field NotesPublished October 9, 2026Work period August 10, 2026 to August 16, 20263 min readIsrael Wilson

A Loop With No Return

A system that takes an instruction, performs an action, and forgets the result has lost the part of the work that could make it wiser.

What makes a completed task improve the next task?

Bring the work that matters.

Run a first read