Justification across a project
Carry project reasoning into collaborative work.
Edit on GitHubYou examined why a case belongs throughout a project. Broad principles start useful conversations. They become practical only when people identify what is relevant, weigh competing concerns, specify a meaning for the project, revise it when challenged, and take actions that generate reviewable evidence.
The prison safety example showed that fairness can refer to several different harms and outcomes. A proposed heart digital twin introduced the need to reflect across a project's lifecycle. In your recruitment case, the same reasoning helps you distinguish a narrow data-audit claim from the wider fairness goal.
You Can Now
By the end of this module, you will be able to:
Explain why an assurance case should develop across a project rather than only before deployment.
Distinguish an ethical principle from a specific action and its justification.
Identify, weigh and specify principles with stakeholder input.
Turn a specified concern into a claim, an action and evidence that can be reviewed.
Continue to Drinking TEA with Others. You will decide who needs access to the working case, how to invite challenge, and what a public snapshot can responsibly communicate.