A unified living vocabulary mapping terms, definitions, and core architectural alignments
across all Technical Working Groups.
Showing all 22 vocabulary terms
Filtered view
Propose a new term or edit an existing one, then submit it with no backend and no
credentials: open a prefilled commit on GitHub (token-less web flow) or download a
create-pr.sh script to run locally. Only
taxonomy/taxonomy-data.js is ever touched.
Start typing. If it already exists, the form fills in with the current entry (editable).
Drafts the definition, scope note, aliases, and suggests related terms, contrasts and working groups (only existing terms/groups are used). Any model exposed by Puter is selectable. Always review — you own every word.Checking…
One sentence. Leave blank to keep the "pending" placeholder.
âš This looks like more than one sentence.
Examples, boundaries, and historical context — not in the definition.
Synonyms / alternate spellings. Type and press Enter. An alias cannot be an existing primary term.
Must already exist in the taxonomy. Autocompletes from existing terms.
Paired contrasting terms — must already exist. Autocompletes.
Select all that share interest. "Universal" is intentionally not a choice.
✓ Ready to submit
You almost certainly don't have write access to , so the PR comes from your own fork. Enter your GitHub username. The button opens GitHub's prefilled commit page (file, commit title and description filled in) and copies the recommended branch name to your clipboard. Choose Create a new branch → Propose changes to open the PR back to upstream.
No credentials are ever requested or transmitted: this uses GitHub's own in-browser web flow.
No fork yet? The button opens the fork page for you. If you leave the username blank, it opens the
upstream editor and relies on GitHub's "fork this repository?" prompt.
Fully automated: branches, applies a comment-preserving surgical edit, signed-off commit, push, and PR via gh.