libLogit

Language Matrix

This page keeps the Beta conversation honest. It separates what exists now from what still needs hardening.

Support Vocabulary

Label	Meaning
Alpha baseline	The binding exists and proves the core LOGIT model locally.
Beta baseline	The binding has install docs, package verification, shared fixtures, and public limitations.
Beta complete	The binding passes the full supported-Beta gate for its ecosystem.

Current MVP Languages

These are the v1 Alpha MVP languages named for the project:

• Python
• C++
• C
• C#
• Java
• JavaScript
• Go
• Kotlin

Binding Snapshot

Binding	Current state	Core direct logging	Config loading	Shared fixtures	Package story	Notable gaps
Python	Reference binding	Yes	Yes	Yes	Strongest	Cross-binding parity still incomplete for advanced features.
C++	Native alpha binding	Yes	Yes	Yes	CMake install/export	CTest discovery has an environment-specific Windows generator issue to resolve.
C	Native alpha binding	Yes	Yes	Yes	CMake install/export	Public install/consumer docs still need more polish.
C#	Managed alpha binding	Yes	Yes	Yes	NuGet metadata/artifact proof	Published package and full consumer install gate still pending.
Java	JVM alpha binding	Yes	Yes	Yes	Maven metadata/artifact proof	Published coordinates and broader consumer validation still pending.
JavaScript	Node alpha binding	Yes	Yes	Yes	npm metadata plus installed-tarball smoke	Public package publication and broader TypeScript story remain open.
Go	Go alpha binding	Yes	Yes	Yes	Module/docs plus starter guide	Tagged public release discipline remains open.
Kotlin	JVM facade	Yes	Yes through Java	Wrapper-level coverage	Companion package verification	Full Kotlin-first package and conformance identity still need work.

Contract Fields To Keep Portable

Every binding should be converging on these user-facing fields:

• name
• localPath
• path
• outputDirectory
• pathMode
• remotePath
• databasePath
• level
• enabled
• sinks
• format
• metadata
• rotation
• retention

Bindings do not need identical spelling for every internal implementation detail, but the public intent must stay recognizable.

Beta Promotion Requirements Per Binding

A binding should not be called Beta-ready until it has:

1. a stable package identity
2. a normal install command
3. a blank LOGIT example
4. a structure-fed LOGIT example
5. a config-loaded example
6. shared fixture coverage
7. documented limitations
8. release verification evidence
9. an owner or maintainer expectation

Likely Next Language Waves

Near-Beta Candidates

• TypeScript
• Swift
• Rust

Valuable But Later

• Ruby
• PHP
• Scala
• Dart
• Delphi/Object Pascal
• additional .NET and JVM languages

The authoritative intake order remains docs/project/beta-language-intake.md.