anonymisationlisted

# Anonymisation Consulting and PMO content is credible because it draws on real experience. That experience is governed by NDAs and trust relationships. Breaking either costs you future clients, legal standing, and referrals. This skill is the binding rule for extracting **lessons** from real experience without exposing the **parties**. If you cannot satisfy this rule, drop the example and use an industry baseline. > **This skill is organisation-neutral.** The values specific to your organisation — who your core audience is, who owns confidentiality sign-off, which agreements bind you — live in a local overlay (`CALIBRATION.local.md`) kept out of version control, not in this file. Create your own from the template in this directory's README. The four-layer structure and decision procedure below are universal. > > **The examples below are illustrative and fictional.** They demonstrate the *failure modes*, not real engagements, and they name no real party. Keep it that way: when editing this skill, never replace a fictional example with a real case, even as a "bad" one. A document about anonymisation must itself be anonymised. ## The Four Layers Each layer must be checked independently before publishing. ### Layer 1 — Identity (the NDA layer) **Rule:** No reader should be able to deduce the client, vendor, sector + scale combination, or project from the content — alone or combined with other public information. Failure modes: - Direct names (a named client or a named co