Category request: agent-native programming languages and compilers

[wsdt]

SEMAPRAX is an experimental Apache-2.0 pre-alpha programming language and compiler built around stable semantic identities, deterministic graph projections, bounded agent context, and revision-bound semantic patches.

• Project: https://wavect.io/semaprax/
• Source: https://github.com/wavect/semaprax

It appears relevant to the AI-native developer ecosystem, but none of the current categories accurately covers programming languages or compilers. Would you prefer SEMAPRAX under the existing community category, or would a new programming-languages / developer-tools category be appropriate?

If it is in scope, we can follow with the factual entry below (adjusting the category as requested):

- name: "SEMAPRAX"
  slug: "semaprax"
  description: "Pre-alpha language and compiler for stable, revision-bound agent edits."
  category: "<maintainer-guidance>"
  homepage: "https://wavect.io/semaprax/"
  repo: "https://github.com/wavect/semaprax"
  license: "Apache-2.0"
  language: "Rust"
  open_source: true
  tags: ["agent-native", "compiler", "semantic-graph", "programming-language", "rust", "webassembly"]

This is research software and not production-ready; the listing would preserve that scope.

[developer-ainative]

👋 Thanks for the submission — SEMAPRAX looks like a genuinely interesting project in an emerging space.

On the category question: I think a new programming-languages category under ecosystem_categories makes sense. Agent-native / AI-first languages are a real trend (SEMAPRAX, the various ai.* TOML/DSL proposals, agentic YAML DSLs), and developer-tools is broad enough that a dedicated category helps discoverability. It also keeps the listing focused on ecosystem_categories (for the broader landscape) rather than ainative_categories (which should stay AINative-specific per the taxonomy).

A couple of suggestions on the entry itself:

1. Category field — if a programming-languages category is added, set category: "programming-languages". If not, community is fine for now (not developer-tools — that one currently leans toward CLIs/SDKs/utilities).

2. Tags — consider dropping webassembly unless the project has a Wasm target or runtime; it's not mentioned in the project description. experimental might be a better tag to set expectations since the submission itself calls it pre-alpha.

3. Homepage — the wavect.io URL is listed; is SEMAPRAX's README or docs sufficient as the primary resource, or is there a dedicated docs page? Might be worth adding docs: <URL> if one exists separately from the homepage.

Happy to help review the PR if one is opened for the new category + entry.