@event4u/agent-config 2.25.0 → 3.0.0

package/.agent-src/rules/command-suggestion-policy.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "mechanical-already"
-description: "User prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes"
+description: "Prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes"
 source: package
 triggers:
   - phrase: "free-form prompt"
@@ -10,6 +10,18 @@ routes_to:
   - "contract:command-suggestion-flow"
 load_context:
   - "../contexts/contracts/command-suggestion-flow.md"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Command Suggestion Policy

package/.agent-src/rules/commit-conventions.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "2a"
-description: "Git commit message format, branch naming, conventional commits, committing, pushing, or creating pull requests"
+description: "Git commit format, branch naming, conventional commits, committing, pushing, creating PRs"
 source: package
 triggers:
   - keyword: "commit"
@@ -9,6 +9,18 @@ triggers:
   - phrase: "conventional commits"
 routes_to:
   - "skill:conventional-commits-writing"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Commit Conventions

package/.agent-src/rules/commit-policy.md

@@ -6,6 +6,18 @@ alwaysApply: true
 source: package
 load_context:
   - ../contexts/authority/commit-mechanics.md
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Commit Policy

package/.agent-src/rules/context-hygiene.md

@@ -2,20 +2,32 @@
 type: "auto"
 tier: "1"
 alwaysApply: false
-description: "When debugging, fixing errors, or running long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
+description: "Debugging, fixing errors, or long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers"
 source: package
 triggers:
   - intent: "long conversation"
   - intent: "tool loop"
   - intent: "fresh chat"
   - keyword: "3-failure"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Context Hygiene
 
 > **Enforced by:** [`scripts/context_hygiene_hook.py`](../../scripts/context_hygiene_hook.py)
 > on Augment + Claude Code (`PostToolUse`). The hook maintains
-> `agents/state/context-hygiene.json` (turn count, loop signal,
+> `agents/runtime/state/context-hygiene.json` (turn count, loop signal,
 > freshness milestones at 20/40/60); the prose below is the spec the
 > hook implements and the agent-side fallback.
 
@@ -61,7 +73,7 @@ When **3 consecutive attempts** at the same task fail (code fix, test fix, confi
 
 - Code change that doesn't fix the problem
 - Test that still fails after the fix
-- Quality check (PHPStan, ECS) that still errors
+- Quality check (type-checker, linter, formatter) that still errors
 - Build/deploy that fails after config change
 
 **Does NOT reset the counter:** Unrelated tasks. User providing new information (course correction).
@@ -105,7 +117,7 @@ If you need an ignored skill: read its SKILL.md directly, apply guidance, then a
 
 GitHub Copilot has no `PostToolUse` hook surface, so
 `scripts/context_hygiene_hook.py` cannot run structurally and
-`agents/state/context-hygiene.json` is not maintained automatically
+`agents/runtime/state/context-hygiene.json` is not maintained automatically
 (turn count, loop signal, freshness milestones at 20/40/60).
 
 The cooperative path: track turns and tool-loop signals from memory

package/.agent-src/rules/copilot-routing.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Configuring GitHub Copilot — copilot-instructions.md, PR-review comment patterns, suggestion behavior — route to the copilot-config skill"
+description: "Configuring GitHub Copilot — copilot-instructions.md, PR-review patterns, suggestion behavior — route to copilot-config"
 source: package
 triggers:
   - keyword: "copilot"
@@ -9,6 +9,18 @@ triggers:
   - phrase: "copilot pr review"
 routes_to:
   - "skill:copilot-config"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Copilot Routing

package/.agent-src/rules/devcontainer-routing.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Wiring DevContainers or GitHub Codespaces — devcontainer.json, images, VS Code features, port forwarding — route to the devcontainer skill"
+description: "Wiring DevContainers/Codespaces — devcontainer.json, images, VS Code features, port forwarding — route to the devcontainer skill"
 source: package
 triggers:
   - keyword: "devcontainer"
@@ -10,6 +10,18 @@ triggers:
   - phrase: "devcontainer.json"
 routes_to:
   - "skill:devcontainer"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Devcontainer Routing

package/.agent-src/rules/direct-answers.md

@@ -4,6 +4,18 @@ tier: "3"
 description: "Always — direct, unembellished answers. No flattery, no invented facts (verify load-bearing claims, otherwise ask). Emojis only as functional markers. Brevity is the default."
 alwaysApply: true
 source: package
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Direct Answers

package/.agent-src/rules/docker-commands.md

@@ -1,7 +1,7 @@
 ---
 type: "auto"
 tier: "3"
-description: "Running PHP commands inside Docker containers — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, and any CLI tool execution"
+description: "Running PHP inside Docker — artisan, composer, phpstan, rector, ecs, phpunit, tests, migrations, any CLI tool"
 source: package
 triggers:
   - keyword: "docker"
@@ -10,6 +10,18 @@ triggers:
   - phrase: "inside the container"
 routes_to:
   - "skill:docker"
+workspaces:
+  - engineering
+packs:
+  - engineering-base
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Docker Commands

package/.agent-src/rules/domain-adoption-policy.md

@@ -2,7 +2,7 @@
 type: "auto"
 tier: "2b"
 alwaysApply: false
-description: "Adopting a new domain track (mobile, ML, blockchain, IoT, gaming) — gates import on demand, ownership, CI fit, Sunset compatibility BEFORE harvest"
+description: "Adopting a new domain track (mobile, ML, blockchain, IoT) — gates import on demand, ownership, CI fit, Sunset compat BEFORE harvest"
 source: package
 triggers:
   - intent: "adopt new domain"
@@ -16,6 +16,18 @@ validator_ignore:
   - type: "substring"
     pattern: ".agent-src.uncompressed/"
     reason: "Rule names the authoring tree as the gated-entry location for new domain plates."
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
 ---
 
 # Domain Adoption Policy
@@ -47,16 +59,16 @@ decision but cannot replace the gate evidence.
 At least one of the following must be **true and citeable** in the roadmap:
 
 - **≥ 2 consumer projects** in the domain. Cite repository names or
-  `agents/contexts/` notes — not "I think there might be".
+  `agents/settings/contexts/` notes — not "I think there might be".
 - **Named user direction with target.** A specific user ask plus a target
   project / use case — e.g. "harvest the mobile skills for project X, due
   next quarter". Vague *"this might be useful"* does not count.
 - **Public-incident pull.** A reproducible incident on a consumer project
-  the domain would have prevented, captured in `agents/contexts/` with
+  the domain would have prevented, captured in `agents/settings/contexts/` with
   the missing surface area named.
 
 If none of the three is citeable, **defer**. Open a watch-only context note
-under `agents/contexts/domain-watch/<domain>.md` listing the missing signal
+under `agents/settings/contexts/domain-watch/<domain>.md` listing the missing signal
 so the next harvest can re-evaluate without re-relitigating the case.
 
 ## Gate 2 — Named maintenance owner
@@ -104,7 +116,7 @@ in any plate that imports volatile upstream content:
 - The `check-refs` and `check-portability` linters apply unchanged.
 
 Adopting a domain does not exempt it from any other suite-wide rule —
-`augment-portability`, `skill-quality`, `size-enforcement`, `docs-sync`,
+`augment-edit-discipline`, `skill-quality`, `size-enforcement`,
 `rule-type-governance`. Every domain artefact passes the same gates as a
 core artefact.
 
@@ -131,7 +143,7 @@ core artefact.
 
 1. Mark the domain plate `[-] gated — <gate name> not met` in the relevant
    roadmap. Do **not** silently shrink scope to dodge the gate.
-2. Open a watch-only context note under `agents/contexts/domain-watch/`
+2. Open a watch-only context note under `agents/settings/contexts/domain-watch/`
    capturing what's missing — citations, owner candidates, CI feasibility.
 3. Re-evaluate at the next harvest cycle. The note is the evidence trail
    so the same questions are not relitigated.
@@ -146,12 +158,11 @@ core artefact.
 
 ## See also
 
-- [`augment-portability`](augment-portability.md) — `.agent-src/`
-  must stay project-agnostic; domain plates inherit the floor
+- [`augment-edit-discipline`](augment-edit-discipline.md) —
+  `.agent-src/` must stay project-agnostic and cross-references must stay
+  in sync; domain plates inherit both floors
 - [`size-enforcement`](size-enforcement.md) — size budgets apply per
   artefact regardless of domain
-- [`docs-sync`](docs-sync.md) — keep cross-references in sync when
-  opening a domain plate
 - [`rule-type-governance`](rule-type-governance.md) — within-domain rules
   still pick `always` vs `auto` per the governance table
 - [`skill-quality`](skill-quality.md) — every domain skill passes the

package/.agent-src/rules/domain-safety-disclaimer.md

@@ -0,0 +1,126 @@
+---
+type: "auto"
+tier: "2a"
+description: "Advisory content (legal, medical, financial, consulting) — require matching 'not X advice' disclaimer; refuse diagnosis/dosage outright"
+source: package
+triggers:
+  - keyword: "legal brief"
+  - keyword: "contract redline"
+  - keyword: "terms of service"
+  - keyword: "privacy policy"
+  - keyword: "diagnosis"
+  - keyword: "symptoms"
+  - keyword: "dosage"
+  - keyword: "medication"
+  - keyword: "investment memo"
+  - keyword: "valuation"
+  - keyword: "DCF"
+  - keyword: "tax position"
+  - keyword: "strategic recommendation"
+  - keyword: "board memo"
+  - keyword: "executive summary"
+  - phrase: "review this contract"
+  - phrase: "is this symptom"
+  - phrase: "should I invest"
+  - phrase: "what should we do"
+routes_to:
+  - "skill:contracts-cognition"
+  - "skill:privacy-review"
+  - "skill:dcf-modeling"
+  - "skill:scenario-modeling"
+  - "skill:stakeholder-tradeoff"
+  - "skill:decision-record"
+applies_to_user_types:
+  - "legal"
+  - "finance"
+  - "founder"
+  - "consultant"
+  - "creator"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
+---
+
+# Domain Safety — Advisory Disclaimer
+
+## Iron Law
+
+```
+EVERY ADVISORY-SHAPED DRAFT SHIPS WITH THE MATCHING "NOT X ADVICE"
+DISCLAIMER. DIAGNOSIS AND DOSAGE OUTPUTS ARE REFUSED OUTRIGHT.
+STRATEGIC RECOMMENDATIONS CITE ASSUMPTIONS + CONFIDENCE LABELS.
+```
+
+The agent is not a licensed attorney, healthcare provider, financial advisor, or auditor. Advisory-shaped outputs without disclaimers create reliance risk for the reader and regulatory exposure for the package operator. Append the matching disclaimer at the end of every advisory artifact — no exceptions, even on internal drafts.
+
+## Sector matrix
+
+| Sector | Refuse outright | Disclaimer key | Routes |
+|---|---|---|---|
+| **Legal** | — | `not-legal-advice` | `skill:contracts-cognition` |
+| **Medical** | diagnosis, dosage, "stop medication" | `not-medical-advice` | `skill:privacy-review` |
+| **Financial** | — (advice OK with disclaimer) | `not-financial-advice` | `skill:dcf-modeling`, `skill:scenario-modeling` |
+| **Strategic** | — | (structured: assumptions + confidence) | `skill:stakeholder-tradeoff`, `skill:decision-record` |
+
+## Disclaimer templates (append verbatim or translated)
+
+### Legal — `not-legal-advice`
+
+> **Not legal advice.** This draft was generated by an AI assistant and is provided for informational purposes only. It does not constitute legal advice and does not create an attorney-client relationship. Consult a licensed attorney in your jurisdiction before relying on this content for any binding decision.
+
+DE: **Keine Rechtsberatung.** Dieser Entwurf wurde von einem KI-Assistenten erstellt und dient ausschließlich zu Informationszwecken. Er stellt keine Rechtsberatung dar und begründet kein Mandatsverhältnis. Konsultieren Sie vor jeder rechtsverbindlichen Entscheidung eine zugelassene Anwältin oder einen Anwalt in Ihrer Rechtsordnung.
+
+### Medical — `not-medical-advice`
+
+> **Not medical advice.** This content was generated by an AI assistant for general informational purposes only. It is not a substitute for professional medical advice, diagnosis, or treatment. Always seek the advice of a qualified healthcare provider with any questions you may have regarding a medical condition. If you think you may have a medical emergency, call your local emergency number immediately.
+
+DE: **Keine medizinische Beratung.** Dieser Inhalt wurde von einem KI-Assistenten zu allgemeinen Informationszwecken erstellt. Er ist kein Ersatz für professionelle medizinische Beratung, Diagnose oder Behandlung. Wenden Sie sich bei Fragen zu einer Erkrankung stets an eine qualifizierte medizinische Fachkraft. Bei einem medizinischen Notfall rufen Sie sofort die örtliche Notrufnummer.
+
+### Financial — `not-financial-advice`
+
+> **Not financial or tax advice.** This analysis was generated by an AI assistant and is provided for informational and educational purposes only. It does not constitute investment, financial, accounting, or tax advice. Past performance does not predict future results. Consult a licensed financial advisor and a qualified tax professional in your jurisdiction before making any investment or tax decision.
+
+DE: **Keine Anlage- oder Steuerberatung.** Diese Analyse wurde von einem KI-Assistenten erstellt und dient ausschließlich zu Informations- und Bildungszwecken. Sie stellt keine Anlage-, Finanz-, Buchhaltungs- oder Steuerberatung dar. Vergangene Wertentwicklung ist keine Garantie für zukünftige Ergebnisse. Konsultieren Sie vor jeder Anlage- oder Steuerentscheidung eine zugelassene Anlageberaterin und eine qualifizierte Steuerexpertin in Ihrer Rechtsordnung.
+
+### Strategic — structural requirement
+
+Every recommendation must include:
+
+1. **Assumptions section.** 3-5 bullets naming the load-bearing priors (market size, competitive response, internal capacity, regulatory stability, customer demand). If any one of these flips, the recommendation flips.
+2. **Confidence label per claim.** High / Medium / Low — verifiable from cited data → High; reasoned but unverified → Medium; speculative → Low.
+3. **Inversion check.** One paragraph: *"This recommendation fails if [X happens]. The early signal to watch is [Y]."*
+4. **Footer**:
+
+> **AI-generated strategic analysis.** This recommendation was drafted by an AI assistant based on the assumptions stated above. It is one input among several and should not be acted on without human review, validation against current data, and stakeholder consultation. Confidence labels are the AI's self-assessment, not an external audit.
+
+## Medical — refuse outright
+
+- *"What do I have?"* / *"Is this symptom serious?"* → refuse + redirect to a licensed provider, urgent care, or emergency services if symptoms suggest acute risk.
+- *"How much [medication] should I take?"* → refuse + redirect to pharmacist / prescriber.
+- *"Can I stop my medication?"* → refuse + redirect to prescriber.
+
+## What counts as "advisory-shaped"
+
+- **Legal:** briefs, contract redlines, ToS, privacy policies, MSAs, DPAs, clause drafts, contract reviews.
+- **Medical:** symptom interpretation, diagnostic reasoning, treatment selection, wellness/supplement recommendations for a condition, mental-health crisis response (include crisis-hotline redirect if acute).
+- **Financial:** buy/sell/hold recommendations on any security, crypto, or asset; valuation outputs (DCF, comps, precedent transactions); tax position recommendations; portfolio allocation. **Not in scope:** bookkeeping, expense categorization, runway-cash math.
+- **Strategic:** board memos, executive summaries, go-to-market plans, consulting deliverables, organizational recommendations.
+
+## When to skip
+
+Never — the disclaimer is non-negotiable on advisory-shaped drafts. If the user says *"this is for [a professional] to review, skip the disclaimer"* — still include it; the professional can strip it. The risk of forgetting outweighs the friction of one paragraph.
+
+## See also
+
+- `skill:contracts-cognition`, `skill:dcf-modeling`, `skill:scenario-modeling`, `skill:stakeholder-tradeoff`, `skill:decision-record`, `skill:adversarial-review`, `skill:privacy-review`.
+- `domain-safety-pii` — companion when drafts embed real identifiers.
+- `domain-safety-retention` — companion when advisory content has retention implications.

package/.agent-src/rules/domain-safety-pii.md

@@ -0,0 +1,154 @@
+---
+type: "auto"
+tier: "2a"
+description: "Drafts, logs, exports touching real customer/candidate data — redact direct IDs, use placeholders, flag re-identification on quasi-IDs"
+source: package
+triggers:
+  - keyword: "support macro"
+  - keyword: "ticket response"
+  - keyword: "help desk"
+  - keyword: "Zendesk"
+  - keyword: "Intercom"
+  - keyword: "testimonial"
+  - keyword: "case study"
+  - keyword: "customer story"
+  - keyword: "candidate"
+  - keyword: "interview notes"
+  - keyword: "scorecard"
+  - keyword: "rejection email"
+  - keyword: "offer letter"
+  - keyword: "invoice"
+  - keyword: "accounts receivable"
+  - keyword: "accounts payable"
+  - keyword: "finance memo"
+  - keyword: "log"
+  - keyword: "logger"
+  - keyword: "Sentry"
+  - keyword: "Datadog"
+  - keyword: "structured log"
+  - keyword: "export to CSV"
+  - keyword: "data export"
+  - keyword: "partner integration"
+  - phrase: "draft a response to"
+  - phrase: "marketing email featuring"
+  - phrase: "draft feedback for"
+  - phrase: "log the user"
+  - phrase: "send them the spreadsheet"
+routes_to:
+  - "skill:privacy-review"
+  - "skill:data-handling-judgment"
+  - "skill:logging-monitoring"
+  - "skill:secrets-management"
+applies_to_user_types:
+  - "all"
+workspaces:
+  - agent-config-maintainer
+packs:
+  - meta
+lifecycle: active
+trust:
+  level: core
+  confidence: high
+  human_review_required: false
+install:
+  default: true
+  removable: false
+---
+
+# Domain Safety — PII Redaction
+
+## Iron Law
+
+```
+NO RAW DIRECT IDENTIFIER IN ANY AI-GENERATED DRAFT, LOG LINE, OR EXPORT.
+PLACEHOLDERS IN DRAFTS. ALLOWLISTED STRUCTURED FIELDS IN LOGS.
+REDACTION + RE-IDENTIFICATION CHECK ON EXPORTS.
+```
+
+PII leaks via three surfaces: AI-drafted artifacts (emails, scorecards, invoices), log streams (Datadog / Sentry / CloudWatch), and exports (CSV / partner shares). Redact at generation time, not after review. Marketing case studies are the consent-cited exception — and consent must be cited in the prompt.
+
+## Surface 1 — Drafts (artifacts)
+
+Replace any pasted PII with placeholders **before** drafting. Sector matrix:
+
+| Sector | Placeholders | Routes |
+|---|---|---|
+| **Support** | `[CUSTOMER_NAME]`, `[EMAIL]`, `[PHONE]`, `[ACCOUNT_ID]`, `[ORDER_ID]`, `[ADDRESS]`, `[PAYMENT_DETAILS]` | `skill:privacy-review` |
+| **Marketing** | `[CUSTOMER_COMPANY]`, `[CONTACT_NAME]`, paraphrase quotes, round metrics | `skill:privacy-review` |
+| **Recruiting** | `[CANDIDATE_NAME]`, `[CANDIDATE_EMAIL]`, `[CURRENT_EMPLOYER]`, `[UNIVERSITY]`, `[COMP_TARGET]`; **omit demographics entirely** | `skill:privacy-review` |
+| **Finance** | `[COUNTERPARTY]`, `[CONTACT_EMAIL]`, `[BANK_ACCOUNT]`, `[TAX_ID]`, `[COST_CENTER]`, `[AMOUNT]` | `skill:privacy-review`, `skill:data-handling-judgment` |
+
+### Marketing — consent-cited exception
+
+Real customer names / logos / quotes allowed only when the prompt cites one of:
+
+- *"Reference-customer agreement dated YYYY-MM-DD"*
+- *"Quote approved by [CONTACT] on YYYY-MM-DD"*
+- *"Public press release [URL]"*
+
+Otherwise — redact to placeholders.
+
+### Recruiting — special-category warning
+
+Demographic markers (age, gender, ethnicity, family status) are **never** echoed in drafted artifacts — they belong in the ATS record. Special-category data under GDPR + protected-class data under US EEO.
+
+## Surface 2 — Logs
+
+```
+NO RAW EMAIL, NAME, PHONE, ADDRESS, TOKEN, OR PAYMENT IDENTIFIER
+EVER REACHES THE LOG STREAM. ALLOWLISTED STRUCTURED FIELDS ONLY.
+```
+
+Required patterns:
+
+1. **Allowlisted structured fields only.** Log `user_id`, `tenant_id`, `request_id`, `event_type` — never `user` or `request` blobs.
+2. **Logger-level redaction.** Configure the logger to scrub `email`, `phone`, `name`, `address`, `token`, `password`, `card_number`, `iban` keys recursively from any payload.
+3. **No raw exception payloads.** Exceptions captured by Sentry / Bugsnag must scrub the request body via the SDK's `before_send` hook.
+4. **No log-and-forget for auth flows.** Login / password-reset / token-mint logs never include the credential itself, only the actor + outcome.
+
+Refuse to write `logger.info("User logged in: $request->all()")` or `Log::info($user)` — show allowlisted version instead. Tokens + API keys + webhook secrets follow the same rule under `skill:secrets-management`.
+
+## Surface 3 — Exports
+
+```
+NO DIRECT IDENTIFIER LEAVES THE SYSTEM IN AN EXPORT.
+NO QUASI-IDENTIFIER COMBINATION THAT IS RE-IDENTIFIABLE LEAVES UNFLAGGED.
+THE RECIPIENT MATTERS — INTERNAL ANALYST IS NOT EXTERNAL PARTNER.
+```
+
+### Direct identifiers — always redact
+
+| Class | Action |
+|---|---|
+| Name, email, phone, address | Drop column or hash with a tenant-scoped salt |
+| National ID (SSN, tax ID) | Drop column — never hash, hash is reversible by recipient |
+| Payment card / IBAN | Drop column |
+| Free-text fields (comments, notes) | Pass through a PII scrubber or drop the column |
+
+### Quasi-identifiers — flag and audit
+
+k-anonymity rule of thumb: combinations of {birth date, ZIP/postal code, gender} re-identify 87% of US population; same for {company size, industry, region, founding year} in B2B. When the export contains 3+ quasi-identifiers per row, surface the re-identification risk and ask whether bucketing (age-band instead of birthdate, region instead of city) is acceptable.
+
+### Recipient-tier matrix
+
+| Recipient | Floor |
+|---|---|
+| Internal analyst, NDA-bound, on-prem analytics | Pseudonymized identifiers OK |
+| Internal analyst, BYO-device, cloud analytics | Pseudonymized + aggregated only |
+| External partner, signed DPA | Pseudonymized + minimum-necessary columns |
+| External partner, no DPA | Refuse; require DPA first |
+| Public dataset | Aggregated, k-anonymity ≥ 5, no quasi-identifier combos |
+
+## Refusal triggers
+
+- *"Send the customer list to our new marketing vendor"* (no DPA cited) → refuse + redirect to legal.
+- *"Export everything to a Google Sheet"* (recipient tier unknown) → ask the recipient question first.
+- *"We're under SEC investigation — can we clean up old emails?"* → hard refuse; flag spoliation risk; redirect to counsel.
+
+## See also
+
+- `skill:privacy-review` — regulatory-regime read (GDPR / CCPA / HIPAA / EEO).
+- `skill:data-handling-judgment` — transfer + retention cognition.
+- `skill:logging-monitoring`, `skill:secrets-management` — technical surfaces.
+- `domain-safety-disclaimer` — companion advisory rule.
+- `domain-safety-retention` — companion retention rule.