Chrysalis — the verification-backed migration engine
github.com/4GEngineer/chrysalis · MIT intent · early development
Chrysalis is the verification layer AgenticOps brings to every pilot: work is scoped to
one bounded legacy system at a time — typically a PHP-heavy slice (custom
apps, framework stacks, long-lived .php estates). We capture what that slice
actually does, replay it against candidate implementations (new runtime, refactored
module, or translated surface), surface mismatches honestly, and run chimera-style cutover
until behavior earns parity. That loop was distilled from the same shipping discipline that
produced wisptools.io — agents accelerate; humans gate; proof decides.
Not vibe-coded rewrites — proof-grounded translation.
What exists today (facts)
Public proof: the WISP-Management / wisptools.io codebase — multi-tenant operations platform, MIT-licensed, linked below — demonstrates agent-assisted delivery at production scale.
Chrysalis: lives in its own repository (4GEngineer/chrysalis), separate from WISP-Management. The engine is early; engagements run as private alpha pilots — still one legacy system at a time. Capabilities below describe what we’re building toward; production-hardening tracks pilot feedback.
Engine shape (pilots)
- Oracle corpus capture from running PHP slices
- Deterministic replay harness
- Behavioral diff & coverage
- Honest partial translation (“holes”)
- Chimera cutover orchestration
Where it fits
- Legacy PHP (primary proving surface)
- Perl / classic .NET — same verify pattern
- Monolith → service decomposition
- Language & framework migrations
- Risk-bounded refactors at scale
Status
- Source · 4GEngineer/chrysalis
- Private alpha pilots — one system at a time
- MIT license (intent; verify LICENSE in repo)
- Request pilot brief →