tc39-atlas
Interactive explorer that uses Jev to tag TC39 proposals by adoption path, cognitive overhead, web-compat risk and intent archetype.
Overview
TC39 Proposal Atlas is a web application that enriches the live corpus of ECMAScript (TC39) proposals with a semantic taxonomy produced by Jev. Standard proposal records only carry stage, name, description and authors, so the app asks Jev typed questions about each proposal and displays the results in a split-screen explorer with a stage-coded colour palette.
Each proposal is classified on five core dimensions: adoption path (polyfillable in userland, transpilable at build time, or requiring engine changes) as a Choice, cognitive overhead and web-compatibility risk as 1 to 5 Scores, primary motivation as a Choice, and several architectural signals as yes/no questions, such as whether it mutates prototypes or adds new syntax. It also assigns one of seven foundational intent archetypes. A scheduled GitHub workflow reruns the enrichment for new or updated proposals using a repository secret. It is aimed at JavaScript developers and standards watchers who want a structured view of the proposal pipeline.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Choice | What adoption path does this proposal need? | userland_polyfillable · build_transpilable · native_engine_required |
| Score | How much cognitive overhead does this feature impose on developers? (1-5) | — |
| Choice | What is the primary motivation? | dev_ergonomics · performance_optimization · correctness_safety · ecosystem_interop |
| Yes / no | Does this introduce new grammar or syntax? | — |
How it works
- Fetch the TC39 proposal corpus.
- Send each proposal to Jev with the dimension questions.
- Store the typed answers and probabilities as enrichment data.
- Render the explorer; a CI job re-enriches changed proposals.
Strengths
- Adds structured, comparable dimensions to every proposal.
- Automated refresh via GitHub Actions.
Caveats
- Jev's judgments on proposals are not validated against expert labels in the README.
- No licence stated.
- Needs a TypeSafe key for enrichment.
Getting started
npm install, then npm run enrich:api with TYPESAFE_API_KEY set.At a glance
- Type
- Project
- Status
- prototype
- Language
- TypeScript
- Runtime
- web app + GitHub Actions
- Has code
- yes
Use cases and integrations
How curated lists describe it
Interactive semantic explorer and taxonomy for TC39 proposals. Applies TypeSafe AI System One (Jev) to classify ECMAScript proposals across adoption pathways, cognitive overhead, web-compatibility risk, and foundational intent archetypes.
logicrw/awesome-jev-projects
Frequently asked questions
What does Jev decide for each proposal?
Adoption path, motivation, cognitive overhead, web-compat risk, several yes/no architectural signals and an intent archetype.
How is the data kept current?
A GitHub workflow runs the enrichment for newly submitted or updated proposals.
Are the labels authoritative?
No, they are model judgments, not TC39 committee classifications.
Related projects
Browser-based systematic-review extraction tool where Jev points at the lines that answer each question and code copies verbatim quotes.
ProjectbetaJavaScriptDaily pipeline that reads Spain's official gazette with Jev, scoring relevance, tagging categories and picking a summary paragraph.
AppprototypeTypeScriptMines timestamped driving scenes from vehicle logs by asking Jev lateral and longitudinal manoeuvre questions per moment.
ProjectbetaPythonRecord linkage for researchers: write the match rule in plain English and Jev judges each candidate pair with a probability.
ProjectbetaPythonWindows office workbench with search, OCR and batch renaming, where Jev optionally helps pick extracted contract fields.
ProjectbetaRustClassifies 1,000 arXiv AI papers into 24 topics with one Jev Choice each and checks agreement against an LLM judge.
ProjectprototypePython