upgrade-to-team-os

To convert a personal Claude Code OS into a shared team workspace, run an automated upgrade that copies your skills and docs into a team-ready structure while removing owner identifiers and neutralizing first-person voice. It auto-detects architecture maturity and applies privacy sanitization.

PII sanitization works by applying programmatic gates that scan for and remove identifiers, neutralize first-person pronouns, and gate sensitive content before sharing a knowledge base. The upgrade blocks completion if any PII or pronoun leakage is detected.

Yes, you can run an idempotent migration on an already canonical Claude Code repo. The upgrade auto-detects existing architecture maturity and performs additive-only scaffolding, augmenting missing skills without overwriting your personal OS.

Yes, the team OS migration supports non-English folder structures by inferring locale mapping during the auto-detection scan. It safely scaffolds and sanitizes directories regardless of the detected language locale.

If post-transform PII validation fails during the team OS upgrade, the process blocks the success declaration. It runs programmatic gates for PII and pronoun leakage to ensure no unsafe content is declared complete before you resolve the issues.

No, your personal operating system is not overwritten when upgrading to a team OS. The upgrade uses additive-only, idempotent behavior to scaffold missing canonical structures and skills into a separate output path.