-
-
Notifications
You must be signed in to change notification settings - Fork 0
[campaign] TypeScript → AffineScript estate migration (UMBRELLA) #239
Copy link
Copy link
Open
Labels
documentationDocs, prose, diagrams, READMEs, ADRsDocs, prose, diagrams, READMEs, ADRsgovernancePolicy, rulesets, standards, compliance, and their enforcementPolicy, rulesets, standards, compliance, and their enforcementmeta:campaignCoordinated multi-repo push with a defined end stateCoordinated multi-repo push with a defined end statemeta:recurringRecurs on a schedule or by trigger; never finally closedRecurs on a schedule or by trigger; never finally closedmeta:umbrellaParent issue aggregating child issuesParent issue aggregating child issuesmigrationPorting between languages or toolchains (e.g. -> AffineScript)Porting between languages or toolchains (e.g. -> AffineScript)priority:p3Low - nice to haveLow - nice to havescope:estateAffects many or all repos across the estateAffects many or all repos across the estate
Description
Activity
Metadata
Metadata
Assignees
Labels
documentationDocs, prose, diagrams, READMEs, ADRsDocs, prose, diagrams, READMEs, ADRsgovernancePolicy, rulesets, standards, compliance, and their enforcementPolicy, rulesets, standards, compliance, and their enforcementmeta:campaignCoordinated multi-repo push with a defined end stateCoordinated multi-repo push with a defined end statemeta:recurringRecurs on a schedule or by trigger; never finally closedRecurs on a schedule or by trigger; never finally closedmeta:umbrellaParent issue aggregating child issuesParent issue aggregating child issuesmigrationPorting between languages or toolchains (e.g. -> AffineScript)Porting between languages or toolchains (e.g. -> AffineScript)priority:p3Low - nice to haveLow - nice to havescope:estateAffects many or all repos across the estateAffects many or all repos across the estate
Campaign overview
Estate-wide migration of TypeScript to AffineScript, parallel to the completed V→Zig sweep (2026-05-28) but at very different scale.
State: IN-FLIGHT. Multi-session campaign, ~50-80 PRs across ~38 repos.
Scope safety: only
hyperpolymath/repos that are non-fork (owner-only + shared-with-son). Upstream forks (rescript, servers, repos-monorepo, linguist) are carve-outs.4-layer architecture
LAYER 1 - POLICY & ENFORCEMENT COMPLETE
LAYER 2 - STDLIB BINDING CAPACITY EXPANDING
LAYER 3 - PHYSICAL FILE PORTS (~285 files / 38 repos)
LAYER 4 - PARALLEL DEPENDENCY: AS bindings top-50 roadmap
Step issues
Dependency graph
step 1 LANDED -> step 2 LANDED -> step 3 (~ done) -> step 4-A (#326) + step 4-B (#327) -> step 4-C (#243) -> step 4-D -> step 5
step 6 (host bindings, parallel) -> step 7 (plugin repos)
Cross-references
Scale summary