Add Privacy Engineer - Engineering#728
Closed
Hotragn wants to merge 1 commit into
Closed
Conversation
msitarzewski
added a commit
that referenced
this pull request
Jul 22, 2026
Lands two gated contributor agents via consolidated branch: - Privacy Engineer (engineering) — the technical counterpart to the policy-focused Data Privacy Officer: PII discovery/classification, data minimization, consent enforcement, DSAR/deletion pipelines, tokenization, retention automation. (#728) - Aging Parent Care Companion (specialized) — HIPAA-aligned family caregiver decision-support: appointment/medication coordination, care-team comms, and caregiver wellbeing. Novel consumer-caregiver domain. (#727) README roster rows added for both; Hermes generated count 263 -> 265. All guards green (divisions/tools/runbooks/hermes-plugin/lint). Closes #728 Closes #727 Co-authored-by: Hotragn <Hotragn@users.noreply.github.com> Co-authored-by: iampaulmata <iampaulmata@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Owner
|
Merged! 🎉 Landed in #738 (consolidated with another agent to avoid a README-merge conflict). Your Privacy Engineer is live — it passed the full gate cleanly (lint 0/0, originality 0.0%) and I love the framing as the technical counterpart to the policy-focused Data Privacy Officer. Thanks for the contribution, @Hotragn! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a Privacy Engineer agent to the engineering division. The roster has a Data Privacy Officer in
specialized/— but that's a policy/DPO role (GDPR programs, PIAs, consent as policy, breach response, regulatory engagement). No agent covers the engineer who implements privacy in code. This agent is the technical counterpart: PII discovery and classification across all stores (including logs, caches, indexes, third parties), data minimization enforced at code review, consent/purpose limitation enforced at the write path (not just recorded), automated DSAR and right-to-be-forgotten pipelines that fan out across distributed systems with verification and audit records, pseudonymization/tokenization vs true anonymization (with re-identification-risk testing), and automated retention. Verified 0.0% originality against the Data Privacy Officer and the roster.Agent Information (if adding/modifying an agent)
Checklist
name,description,colorValidation:
scripts/lint-agents.shpasses with 0 errors / 0 warnings;scripts/check-agent-originality.shreports 0.0% similarity against the roster (checked specifically against the existing Data Privacy Officer).