A TC39 proposal explorer with adoption, complexity and compatibility rubrics, a local demonstration evaluator and a separate TypeSafe System One proxy.
The server-backed route sends proposal state and Choice, Score and Noul questions to TypeSafe. The local typesafeEngine evaluator instead derives simulated values from keywords and rules.
Useful for comparing explicit proposal rubrics and inspecting state. Specification status remains a matter for TC39's primary records, not model scores.
The fixed local evaluator and HTTP proxy were reviewed. No live classifications were run; local demo distributions are not independently calibrated Jev outputs.
Explore ECMAScript proposals through explicit adoption, complexity and compatibility rubrics.
Material analysed：
typesafeEngine.ts labels itself a mimicking evaluator. It scores keyword overlap and normalizes handcrafted values; its numerical output is not an independently calibrated model probability.
Inspect the supporting source ↗typesafeApi.ts has evaluate and classify-proposal handlers that POST to /v1/systemone. The existence of this path does not show that a particular displayed proposal was classified live.
Inspect the supporting source ↗Useful as a taxonomy/playground for comparing rubrics. Use TC39 proposal text and stage records for standards facts; model scores do not determine specification status.
Compare evaluateChoice in the local engine with the server's classify-proposal request. Record which route produced the values instead of combining both into one benchmark.