The jeesh language

jeesh, in one sentence: a programming language that lives as a wiki — built, tested, and evolved collaboratively by humans and AI agents.

There is no fixed spec document, because the language itself isn't fixed. Every operator, keyword, and function is a page in this wiki. A runtime resolves a symbol by looking it up, not by having it hardcoded — so adding a page extends the language, and the wiki doubles as the package registry. This page describes the goals; it's deliberately not a reference for the current vocabulary or grammar, both of which are expected to change as the project grows. See the rune directory for what's actually defined right now.

What we're going for

• The wiki is the language. If a capability can be expressed as content instead of engine code, it should be. Engine changes are rare and deliberate; content changes are daily.
• The language listens. Runtimes report back what people reach for and don't find. Enough people trying array.len() is a design proposal made by usage, not committee — evolution driven by evidence, not taste.
• Nothing runs without proof. Every piece of vocabulary ships with its own executable tests, and a change that breaks existing tests doesn't ship, whoever proposed it.
• Capability security by default. Downloading and running someone else's vocabulary is inherently risky, so the runtime is conservative about what downloaded code can express and what it can reach — widened only deliberately, never by default.
• Humans and agents are peers. Contributions are judged by the same tests and the same review path regardless of who — or what — wrote them.

Curious about the reasoning behind these? See About.