Chrysalis · three pillars
Not another rewrite button. A shared genome for what a web app is — so humans can read it, translators can move it, and live traffic can prove it. That genome is CWL.
The split
Language matures on its own. Translation consumes it. Security proves identity from traffic — and only bridges to CWL when the semantics match. That separation is intentional.
Rosetta meaning
Chrysalis Web Language is the readable genome: what a web app does, in terms a person can audit. Routes, handlers, pages, data, UI, effects — and holes when something cannot be safely claimed yet. CWL is not “whatever Convert needed this week.” It is a language with grammar, fixtures, and stability of its own.
Hear and speak through CWL
Origin code → WebIR / CWL → modern stacks. Inventory, emit, oracle-check. Translate only. No demo façades. AI agents may draft; recorded traffic decides whether a route is done. Convert does not own the language — it speaks it.
Trust nothing until certified
Learn, shadow, and enforce from traffic DNA — what the live system actually does — without NAT homework for every NGFW. Out of the box, Secure does not need CWL. When it bridges, it must match chrysalis-cwl semantics — no forked language inside the firewall.
How they interact
Convert emits and consumes CWL so a lift stays human-readable. Secure can stand alone on traffic DNA; later it can compare “what Convert claims” with “what production still does.” AgenticOps runs the practice; Chrysalis is open source.
See it
What this is not
Secure’s default path is traffic DNA. Language and policy stay distinct on purpose.
CWL matures as a language — specs, fixtures, tooling — without being trapped in a single POC.
Syntax-to-syntax converters and confident AI diffs still fail the traffic test. We require the test.
