What DJ Patil's Five-C Ethical Checklist Taught Our Governance Agent
The former US Chief Data Scientist didn't publish principles — he published a checklist. That distinction turns out to matter enormously when you are building an agent that has to make governance calls at 3am.
By The Data Workers Team
DJ Patil co-coined the term 'data scientist' at LinkedIn in 2008, served as the first US Chief Data Scientist under the Obama administration, and co-authored the O'Reilly report 'Ethics and Data Science' with Hilary Mason and Mike Loukides. What makes his work useful to engineers is that he keeps asking the same uncomfortable question: once you have agreed on a principle, what do you actually do on Tuesday morning?
The Core Insight: Oaths Give Cover, Checklists Connect
In 'Of Oaths and Checklists,' Patil and his co-authors make a crisp distinction that is easy to miss. Oaths are 'one-shots. You take the oath once (if at all), and that's it.' More troublingly: 'oaths can actually give cover to people and organizations who are doing unethical work.' Checklists work differently: 'unlike oaths, checklists connect principle to practice.'
The Five Cs
- •Consent: Was the data collected with authorization for this specific use?
- •Clarity: Can a non-technical stakeholder read the data contract or policy and understand what is happening?
- •Consistency: Is the same ethical standard applied uniformly across populations and pipelines?
- •Control: Do the affected parties have real agency — rights to deletion, correction, and a path for dissent?
- •Consequences: What is the documented answer to 'How could this go wrong?'
How a Method Becomes a Skill
The dw-governance agent already handles policy checks, RBAC enforcement, data contract evaluation, PII scanning, and audit log generation. What the Five-C Ethical Checklist skill adds is a sequenced gate protocol that runs those tools in order and requires each gate to produce a documented answer before the next opens.
The skill calls check_policy for the consent and consistency gates, evaluate_data_contract for the clarity gate, request_governance_review for the consequences gate, and generate_audit_report plus export_audit_log to produce the permanent record. The skill will halt and return a governance hold if any gate fails.
One of More Than 400
The Five-C Ethical Checklist skill is one of more than 400 method-named skills across the 19 agents in the Data Workers swarm.
A note on this post: This is independent commentary and homage. It distills publicly available writing and talks by DJ Patil to illustrate a working method, and every quote is drawn from and verified against the primary sources linked above. The skill it describes is named for the method, not the person, and contains no marketing claims attributed to them. Data Workers is not affiliated with, sponsored by, or endorsed by DJ Patil. If you are DJ Patil and would like anything adjusted or removed, email hello@dataworkers.io and we will respond promptly.
Related Posts
What Ralph Kimball's Dimensional Modeling Taught Our Pipelines Agent
Ralph Kimball's four-step dimensional design process is one of the most durable ideas in data engineering — here is what it taught our pipelines agent.
What Jay Kreps's Log-Centric Architecture Taught Our Streaming Agent
Jay Kreps's core insight is deceptively simple: an append-only, totally-ordered log is not just a message bus — it is the single source of truth that eliminates N² integration pipelines and makes reprocessing routine. We studied his published writing and built a reusable streaming skill around the method.
What W. Edwards Deming's Plan-Do-Study-Act Taught Our Data Quality Agent
W. Edwards Deming spent a career arguing that quality comes from improving the process, not inspecting for defects. His Plan-Do-Study-Act cycle is the most rigorous improvement loop in the field. Here is how we encoded it into our data quality agent.