Owner: Anthony (human-gated lever L-PII-SWEEP-CONTAIN). Surfaced once, never nagged, never auto-pulled. This issue is the lever's permanent, individually-closeable home in the graph — the registry his-hand-levers.json is its source of truth.
Contain the org-wide personal-data exposure (2026-07-01 read-only sweep, verified by parallel explorers). EXECUTED under the corrected doctrine — PII content is PROCESSED AND REDACTED, never deleted: every blunt content-removal PR from the sweep was reworked to RESTORE the removed work and REDACT only the personal identifiers (name / email / phone / home-paths / personal-conversation-links), preserving all substance, and merged. One repo whose sensitivity is the SUBJECT MATTER — pervasive references to named third parties, private message transcripts, and sensitive personal circumstances that identifier-redaction cannot neutralize — was flipped PRIVATE and its removed intake restored-redacted under that privacy: nothing deleted, nothing left publicly readable. The distilled knowledge-corpus was clean and stayed public untouched. ONE human atom remains: the consolidated containment PR organvm/a-i--skills#32 (restores turnstile-spin source to unbreak validate + contains committed session-log PII) is fully GREEN, but its default branch requires 1 approving review I cannot self-supply — admin-merge and dropping the review gate are both correctly harness-blocked safety controls. SEPARATE HISTORY-LEVEL RESIDUE (recorded here so it lives durably, not in a throwaway script — but NOT a unilateral fix): two public repos still carry third-party personal content in HEAD/history — organvm/sovereign-systems--elevate-align (a LIVE co-founder product: flipping it private or rewriting its history is a co-founder decision, not containment I take alone) and organvm/narratological-algorithmic-lenses (its own HEAD was restore-redacted, but a public EXTERNAL fork out of my reach retains the older material). Under process-and-redact a force-push history rewrite is the WRONG tool (it deletes); the correct dispositions are a GitHub 'sensitive data removal' request for the external fork and a co-founder call on the live product.
What it unlocks
closes the systemic back-door exposure of your personal data across the public org; makes publishing the front-door inbound surfaces safe
Cost
one review click: gh pr review 32 --repo organvm/a-i--skills --approve. The PR is green with no required status checks, so your approval makes it mergeable and my standing merge grant lands it (or gh pr merge 32 --repo organvm/a-i--skills --squash --delete-branch). Everything else in the sweep is already restored-redacted and merged — nothing else hangs. History residue: GitHub sensitive-data-removal request for the external fork (support.github.com/contact → sensitive data), and a co-founder decision on the live product — neither is a unilateral flip; both are yours.
Gate
the last atom is a required PR review on a shared org repo: I cannot approve my own PR, and both --admin merge and editing the review requirement are harness-gated safety controls — so the single approval is yours; the merge after is mine.
Source
org-wide read-only PII leak sweep (2026-07-01), reworked to process-and-redact · registry: his-hand-levers.json → lever L-PII-SWEEP-CONTAIN
Close this issue when the action is done — the lever is pulled then.
Owner: Anthony (human-gated lever
L-PII-SWEEP-CONTAIN). Surfaced once, never nagged, never auto-pulled. This issue is the lever's permanent, individually-closeable home in the graph — the registryhis-hand-levers.jsonis its source of truth.Contain the org-wide personal-data exposure (2026-07-01 read-only sweep, verified by parallel explorers). EXECUTED under the corrected doctrine — PII content is PROCESSED AND REDACTED, never deleted: every blunt content-removal PR from the sweep was reworked to RESTORE the removed work and REDACT only the personal identifiers (name / email / phone / home-paths / personal-conversation-links), preserving all substance, and merged. One repo whose sensitivity is the SUBJECT MATTER — pervasive references to named third parties, private message transcripts, and sensitive personal circumstances that identifier-redaction cannot neutralize — was flipped PRIVATE and its removed intake restored-redacted under that privacy: nothing deleted, nothing left publicly readable. The distilled knowledge-corpus was clean and stayed public untouched. ONE human atom remains: the consolidated containment PR organvm/a-i--skills#32 (restores turnstile-spin source to unbreak
validate+ contains committed session-log PII) is fully GREEN, but its default branch requires 1 approving review I cannot self-supply — admin-merge and dropping the review gate are both correctly harness-blocked safety controls. SEPARATE HISTORY-LEVEL RESIDUE (recorded here so it lives durably, not in a throwaway script — but NOT a unilateral fix): two public repos still carry third-party personal content in HEAD/history — organvm/sovereign-systems--elevate-align (a LIVE co-founder product: flipping it private or rewriting its history is a co-founder decision, not containment I take alone) and organvm/narratological-algorithmic-lenses (its own HEAD was restore-redacted, but a public EXTERNAL fork out of my reach retains the older material). Under process-and-redact a force-push history rewrite is the WRONG tool (it deletes); the correct dispositions are a GitHub 'sensitive data removal' request for the external fork and a co-founder call on the live product.What it unlocks
closes the systemic back-door exposure of your personal data across the public org; makes publishing the front-door inbound surfaces safe
Cost
one review click:
gh pr review 32 --repo organvm/a-i--skills --approve. The PR is green with no required status checks, so your approval makes it mergeable and my standing merge grant lands it (orgh pr merge 32 --repo organvm/a-i--skills --squash --delete-branch). Everything else in the sweep is already restored-redacted and merged — nothing else hangs. History residue: GitHub sensitive-data-removal request for the external fork (support.github.com/contact → sensitive data), and a co-founder decision on the live product — neither is a unilateral flip; both are yours.Gate
the last atom is a required PR review on a shared org repo: I cannot approve my own PR, and both
--adminmerge and editing the review requirement are harness-gated safety controls — so the single approval is yours; the merge after is mine.Source
org-wide read-only PII leak sweep (2026-07-01), reworked to process-and-redact· registry:his-hand-levers.json→ leverL-PII-SWEEP-CONTAINClose this issue when the action is done — the lever is pulled then.