background

Background

The background pages explain the historical and design documents that shaped the current CSV Anonymizer architecture. They are useful when a change touches migration history, detector language coverage, release packaging, or local-first privacy boundaries.

Active contributors: Douwe de Vries

Background map

Page	Source material	Use it for
Rust and Tauri rewrite	docs/rust-rewrite-plan.md, current workspace layout, release workflows	Understanding why the active app is React/Vite plus Tauri plus Rust
Multilingual detection	docs/multilingual-detection-phased-plan.md, docs/multilingual-header-detection-investigation.md	Understanding Unicode-safe header normalization, taxonomy-backed detection, validators, and optional future semantic experiments
Architecture	Current code in frontend/src, src-tauri/src, and crates/csv-anonymizer-core/src	Understanding the current layer boundaries
Security	README.md, src-tauri/src/path_access.rs, crates/csv-anonymizer-core/src/csv_io.rs, Local AI code	Understanding privacy and file-system safety boundaries
Dependency freshness	docs/dependency-audit-followups.md	Understanding current audit state and dependency upgrade backlog

How to read historical docs

Some files under docs preserve past investigations or resolved findings. Treat them as design context unless they explicitly describe current implementation status.

Current behavior should be verified against source paths such as:

• frontend/src/tauri.ts
• src-tauri/src/tauri_command_list.rs
• src-tauri/src/commands
• src-tauri/src/local_ai
• crates/csv-anonymizer-core/src
• .github/workflows
• scripts

The wiki should describe the implemented state first, then call out future experiments only when source docs mark them as optional or not yet part of the default path.