architecture-convergencelisted

# Architecture Convergence Turn a substantial architecture change into independently verifiable convergence slices. The same terminal applies whether the implementation spans one repository or many. Optimize for verified throughput: disjoint slices may advance in parallel when doing so has positive net value, but no slice advances on narrative status or stale proof. ## Resource guide - Read `references/architecture-convergence-patterns.md` before choosing slice boundaries, states, parity gates, concurrency, or cutover policy. - Use `scripts/validate_migration_ledger.py` only when the convergence adopts the portable ledger shape in the reference. From this repository's root, run `python3 -m unittest -v skills/architecture-convergence/scripts/test_validate_migration_ledger.py` after changing the validator. A simple single-repository refactor does not need a ledger merely to use this Skill. Reuse the repository's existing proportional verification entrypoint when ledger validity is material; do not add a dedicated CI workflow merely because the portable validator exists. Prefer an existing repo-native schema and validator when one already owns this fact. - Load the target repositories' local architecture, delivery, and safety rules. This portfolio skill does not replace them. ## Workflow 1. Define the source and target boundaries. Name the repos, runtimes, customer-visible invariants, persistence surfaces, delivery paths, and evidence that would prove a completed cutover. 2