docs: define sensitivity and protection method

[asteier2026]

Changes include:

• Documentation for how sensitivity and protection method are assigned.

[greptile-apps]

Greptile Summary

This PR adds a new "Key concepts" section to docs/concepts/rewrite.md that formally defines Sensitivity (with a table of high/medium/low levels and their leakage weights) and Protection method (with a table of all five methods: replace, generalize, suppress_inference, remove, leave_as_is). It addresses previous review feedback requesting concrete level definitions and a table format for protection methods.

• Sensitivity table introduces the three discrete levels and their exact leakage weights (1.0 / 0.6 / 0.3), making the downstream leakage mass formula in the Configuration section self-consistent.
• Protection method table replaces what was previously a run-on sentence with scannable rows that align with the enum values used in the codebase.

Confidence Score: 5/5

Documentation-only change; no code paths are modified.

The change touches only a Markdown documentation file, adding two reference tables that are consistent with the leakage weights and enum values already present elsewhere in the document and codebase. There is no runtime risk.

No files require special attention.

Important Files Changed

Filename	Overview
docs/concepts/rewrite.md	Adds a 'Key concepts' section with a Sensitivity table (high/medium/low levels with leakage weights) and a Protection method table (replace, generalize, suppress_inference, remove, leave_as_is) — documentation-only change with minor prose awkwardness.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Entity detected] --> B[Assign Sensitivity]
    B --> C{Sensitivity level}
    C -->|high - weight 1.0| D["Direct identifiers\n(names, IDs, contacts)"]
    C -->|medium - weight 0.6| E["Quasi-identifiers\n(location, occupation, age)"]
    C -->|low - weight 0.3| F["Generic attributes\n(widely shared traits)"]
    D & E & F --> G[Assign Protection Method]
    G --> H{Method chosen}
    H --> I[replace\nSynthetic alternative]
    H --> J[generalize\nBroader category]
    H --> K[suppress_inference\nRewrite surrounding text]
    H --> L[remove\nDelete entirely]
    H --> M[leave_as_is\nNo change needed]
    I & J & K & L --> N[Leakage scoring]
    M --> O{strict_entity_protection?}
    O -->|True| P[Override → active protection]
    O -->|False| N
    P --> N

Loading

_{Reviews (6): Last reviewed commit: "Update docs/concepts/rewrite.md" | Re-trigger Greptile}

[lipikaramaswamy]

looks good, provides more clarity on the total risk management approach we describe in the devnote.