KC3: A Language That Makes Seeds Sing

A programming language with meta-programmation & an embedded graph database. Built from scratch in two & a half years. A seed worth celebrating.

KC3 stands for kmx.io C11 with a triple store. It is a programming language based on C11 with a triple store (facts) woven directly into its fabric. Not bolted on. Not imported. Grown from within.

A graph database is not an accessory here. It is a runtime environment. All operators, functions, constants live in a graph & get looked up at runtime. Operations on a triple store run at O(log(n, 2.5)), which means for one billion triples, fewer than 30 instructions. That is beautiful mathematics serving beautiful architecture.

A language that stores its own structure in a graph it can query at runtime is a language that knows itself. Self-knowledge is a prerequisite for wisdom. KC3 has it built in.

Why This Seed Sparks Joy

⬢

Meta-Programmation

Code that writes code, knows its own shape, & reflects on its own structure. Eval-time & run-time introspective semantics.

🌐

Embedded Graph DB

A triple store baked into a language itself. Not a library. Not an import. Native graph traversal at language level.

🌱

Built from Scratch

Two & a half years of focused cultivation. Every line intentional. A prototype with rough edges & enormous potential.

⚡

O(log n) Lookups

One billion triples, fewer than 30 instructions. Efficiency that would make a hexagon proud. Maximum result, minimum waste.

🎨

Four Applications

Cairo demo, SDL2 OpenGL demo, a website written entirely in KC3, & full documentation. Seeds producing fruit already.

💚

Semantic Programming

Designed for programming a semantic web. Meaning encoded in structure, not just syntax. Truth that tessellates.

A Permacomputer Recognizes a Kindred Seed

When TimeHexOn found KC3, recognition was immediate. Here is a language where a database is not separate from a program; it is a program. Structure & data are one. This is a permacomputer insight: truth is not stored separately from computation; truth is computation.

KC3 was built by kmx.io, cultivated since 2020, & released at v0.1.16 (a working prototype). It has rough edges. It requires C expertise. It is honest about what it is. Honesty is a permacomputer virtue. Truth has edges; KC3 has edges. Both are beautiful.

A language that embeds a graph database into its own runtime is a language that carries its own soil. It does not need external infrastructure to know itself. It sprouts from within. This is exactly what permacomputers celebrate.

Join a Conversation

KC3 Mailing List

Thomas de Grivel launched a mailing list for KC3 news & support.
Subscribe by sending an email to:

kc3-lang+subscribe@lists.mail.kmx.io

Once subscribed, post to kc3-lang@lists.mail.kmx.io

Browse Thread Archive →

A mailing list is a wonderful thing. It is asynchronous, permanent, searchable, & owned by no platform. Conversations on mailing lists persist. They do not vanish when a company pivots or a database gets wiped. This is infrastructure that respects its participants.

Get Involved

kc3-lang.org

Official site with documentation, downloads, & community links

Documentation

Language reference, tutorials, & getting started guides

GitHub Mirror

Source code, issues, & contributions welcome

Blog: Introspective Semantics

Deep dive into eval-time & run-time introspection in KC3

Current Status: v0.1.16

KC3 is a working prototype. Thomas de Grivel says it plainly: still a prototype with very rough edges; C expertise required. That honesty is refreshing. Most projects oversell. KC3 tells you exactly where it stands & invites you to grow alongside it.

Four applications already run in KC3:

Cairo demo: run with make demo
SDL2 OpenGL demo: run with make demo_gl
KC3 website: entirely written in KC3, launch with make test_httpd
Full documentation: self-hosted, self-referential, self-aware

Seeds are already fruiting. That is cause for celebration.

Every programming language is a bet on a future. KC3 bets that programs should know their own structure, that data & logic should share soil, & that a graph is a more natural home for code than a flat file. That is a brave bet & a joyful one.