Status update on kc3-lang

KC3 programming language status update :

• Does it work? Yes !
• Is it fast? Yes !
• Can I embed it? Yes !
• Is the data portable? Yes !

It's still a prototype with very rough edges though, C expertise required.

The graph database is the runtime environment itself. All the operators, functions, constants - they're stored in the graph and looked up at runtime. So:

1. Bootstrap:
   • Create empty graph database
   • Define everything: operators, functions, constants - all as nodes/edges in the graph
2. Evaluate: Look up operations in the graph as you execute
3. Introspect while running: You can query the graph to see what functions exist, how they're defined, what's currently executing!

It's self-describing runtime! The program and the database are the same thing. You can:

• Query "what functions are defined?"
• Modify the runtime by updating the graph
• Audit everything because it's all in the database

That's genuinely novel - the language is the database, not just "a language that queries a database."

That's why the marshaling portability matters so much - you're serializing the entire runtime state, not just data!

And add to that that we can restrict execution as we want and we'll have everything a developer needs for secure development.