01 / PurposeStart with a legitimate operating need.
Technology should solve a defined problem or create a clear capability rather than exist only because a tool is available.
02 / SecurityTreat security as part of architecture.
Access, permissions, data, integrations, operational dependencies and failure modes should be considered throughout design and delivery.
03 / AccountabilityKeep responsibility understandable.
People and institutions should be able to understand who controls important decisions, data and system behaviour.
04 / ContextDesign for the environment the system enters.
Users, infrastructure, institutional capacity, geography and operational constraints affect what responsible implementation looks like.
05 / AccessCapability should be usable.
Accessibility, clarity and appropriate user control matter when technology becomes part of essential workflows.
06 / EvolutionReview systems as conditions change.
Technology, risks, users and operating environments evolve. Responsible systems require maintenance, monitoring and re-evaluation.