pull down to refresh
But, in my experience, LLMs do not always comply. Is that your language's responsibility to solve or mine?
My take:
[HUMAN LANG] --> [Lexer + MINI LLM] --> JSON + Prompt -> [BIG LLM] --> OUTPUT + Prompt --> [Verification LLM]
That is I think you need 3 stages: (a) Lexer + Mini LLM that transpiles HUMAN lang into structured JSON and also outputs a static prompt describing how to interpret this JSON. Both of which are then fed (b) into big LLM, (c) Output code (plus instruction prompt) is then fed back to another smallish LLM to verify that OUTPUT matches the "MUST" "SHOULD" "NEVER" directives.
[Mini LLM] = Something like gemma3-270m finetuned as a lexer / json compiler
[BIG LLM] = Claude 4 or whatever
[Verification LLM] = Could be something like Qwen3.
reply
Json takes too many tokens, and will not compile to json. however, i have thought about it.
reply
{
"react_dev": {
"model": "gpt-4",
"temperature": 0.2
},
"todo_rules": {
"NEVER": [
"use_class_components",
"mutate_state_directly"
],
"MUST": [
"use_hooks",
"include_add_todo",
"include_delete_todo",
"include_toggle_complete"
],
"SHOULD": [
"use_local_storage",
"handle_empty_input"
],
"AVOID": [
"inline_functions",
"magic_numbers"
]
},
"generates working component": {
"INPUT": "Create a React todo list",
"EXPECT": "contains useState and retu"
}
}
reply
Is there an actual language implementation?
I am going to write a basic lexer in rust. eventually a formatter too. the repo is empty for now because i am still working on it. the cool thing is that it does not need a lexer, but it would be nice. it is going to have a lot of cool stuff coming soon, like a package manager.
Very cool idea in general.
Ty let me know how it works for you.
Is that your language's responsibility to solve or mine?
the entire goal is that the language will solve it. still figuring it out but the idea is that this would integrate directly into an LLM so it is actual code, not just a prompt. i also want to add
ADDRESS_HALLUCINATION or something similar eventually.also, i was going to name it huumn but that github @ was taken... by you! lol.
reply
reply
stop abusing mongolia TLD haha
new project idea: create a country called Human and apply for
.hmn or .human TLD -- when human/AI distinction becomes more important, that TLD may become quite valuable.reply
I read a tweet where some savvy guy bought
walmart.ai, intel.ai, etc shortly after ChatGPT launched and raked in the mongolian beef if you know what I mean..human domains would be nice. I bet you could really gouge.I like domains a lot. I can't wait to make use of https://outer.space
reply
Nice starfield animation, brings back memories of Win 95
reply
I suspect we're looking at a case of this #1077714
reply
i do not care if this takes off or not, it was a side project i use personally and i thought i would share
reply
MUST, I would expect the output to really adhere to that constraint. But, in my experience, LLMs do not always comply. Is that your language's responsibility to solve or mine?