Which architectural decisions carry ethical consequences, and what is the architect's professional responsibility?

The decisions that carry ethical weight

1. What data is collected and retained. Collecting everything because storage is cheap creates exposure for users who did not ask for it and cannot see it. Data minimisation at collection is an architectural decision with an ethical dimension, and it is nearly impossible to retrofit — reducing collection later does not remove what was already gathered.

2. Purpose limitation. Whether data collected for one purpose can be used for another. Enforced by architecture — purpose tags evaluated at the point of use — or not enforced at all.

3. Optimisation targets. A recommendation system optimises what it is told to optimise. Engagement, watch time and click-through are proxies, and optimising a proxy hard produces outcomes nobody intended. The architect's contribution is making the objective explicit and its second-order effects measurable, so the choice is deliberate rather than emergent.

4. Deletion and portability. Whether a user can actually leave, and whether deletion is real across replicas, backups, derived datasets and trained models. Architecture determines whether this is possible; a policy alone does not.

5. Accessibility, which is a structural property of how interfaces are built rather than a feature added later.

6. Transparency. Whether an automated decision can be explained, which requires retaining the inputs and the model version at decision time — an architectural choice made long before anyone asks.

The professional responsibility

To surface the consequence, ensure the decision is made deliberately by someone accountable, and record it.

The architect is usually not the decision-maker on product direction, and that is not an exemption. The obligation is to make the consequence visible — "this design retains individual location history for two years and here is what that means" — so the decision is informed rather than accidental.

A decision made by omission is still a decision, and the architect is frequently the only person positioned to notice it is being made.

The practical mechanisms

• Privacy and data-handling questions in the design review, at the same standard as security questions.
• Data minimisation and purpose binding as default architecture, so the ethical outcome is the low-effort path.
• Measurable second-order effects for optimisation systems, so unintended consequences are detectable rather than theoretical.
• Recording the decision and who accepted it, which is what makes accountability real.