Ethics Shows Up in Requirements

Ethics in robotics is not a final slide about "using technology responsibly."

It changes what the system is required to do.

Example: camera-equipped robot

A robot uses a camera to navigate.

Engineering questions include:

• Does navigation require storing video?
• Is recording enabled by default?
• Who can access images?
• Can the task be completed with processed features instead of retained footage?
• What areas should the robot never image?
• How long is data kept?

Those are architecture decisions.

Bias and performance boundaries

A perception system can perform differently across environments, objects, body types, lighting, or mobility aids.

If a robot interacts around people, testing must include the population and conditions the robot will actually encounter.

"Average accuracy" can hide serious failures.

Accessibility

A human interface that relies only on color, tiny text, sound, or fast reaction time can exclude users.

Accessibility is not separate from robotics. It affects alarms, controls, status displays, and operator training.

Environmental and maintenance costs

Ethical tradeoffs can include:

• battery lifecycle;
• repairability;
• proprietary lock-in;
• energy use;
• replaceable modules;
• disposal;
• labor impact.

No design is neutral just because the CAD file is technically correct.

Requirement rewrite

Take three vague statements:

• "The robot is safe."
• "The robot respects privacy."
• "The interface is accessible."

Rewrite each into at least two testable requirements.

Example:

The operator interface must communicate critical fault state using text/icon information in addition to color.

The ethical concern has now become something engineers can design and test.

Ethical choices become technical constraints

Imagine a service robot with a camera used for navigation in a school hallway.

The question "Should it record everyone it sees?" is not separate from engineering. The answer changes:

• storage architecture;
• network traffic;
• access control;
• retention policy;
• UI;
• incident risk;
• testing data.

A privacy decision becomes a system design decision.

Rewrite values as requirements

Broad value:

Respect privacy.

Engineering requirement:

The navigation system shall process camera frames for localization without retaining identifiable video after the frame is no longer required for the navigation function.

Now the requirement can be reviewed and tested.

Another value:

A person should be able to override the robot.

Engineering version:

A designated operator shall be able to command the robot into its defined safe-stop state through an interface that remains available during loss of autonomous planning.

The exact wording depends on the system. The method is durable: turn social expectations into inspectable constraints before implementation.

Ethics becomes weakest when it appears only in a final reflection. It becomes useful when it changes architecture.