libLogit

libLogit v1 Beta Overview

v1 Beta is the release where libLogit becomes a contract-first SDK. Alpha proves that the model works; Beta makes that model stable enough for users and binding authors to depend on.

Beta Promise

A developer should be able to:

1. Install or import the libLogit SDK for their language.
2. Create a LOGIT object in application startup.
3. Set an output directory or local file path.
4. Set a minimum log level.
5. Optionally set remote-path output, formatting, metadata, retention, and failure behavior.
6. Call that LOGIT anywhere logs are needed.
7. Inspect retained local logs through standard SQL tooling or a libLogit viewer.

The syntax should feel native to each language, but the meaning of the object must remain stable.

What Beta Is Not

Beta is not a promise that every language in existence ships immediately. It is also not a promise that every binding has byte-for-byte identical syntax.

Beta is the point where the shared LOGIT contract, config schema, conformance fixtures, package expectations, and documentation are mature enough that new bindings can be added methodically.

Audiences

Audience	What Beta gives them
Application developers	A predictable logger object they can configure once and call throughout a project.
Desktop developers	Local logs that can rotate, retain, and be inspected without running a server.
Multi-language teams	A shared mental model across services, tools, and runtimes.
Binding authors	A contract and playbook for implementing libLogit in another language.
Maintainers	Release gates that distinguish supported bindings from experiments.

Beta Support Terms

Term	Meaning
Supported binding	A binding with install docs, package metadata, shared fixture coverage, examples, and CI/release evidence.
Incubating binding	A binding being actively shaped against the contract but not yet counted as Beta-ready.
Future binding	A planned or community-requested language with an intake record but no release commitment.

Roadmap Shape

Beta work is organized around the multiphase burndown:

• Documentation foundation.
• LOGIT contract stabilization.
• Config/schema stabilization.
• Cross-language conformance.
• Package and install maturity.
• Local output and rotation parity.
• Remote output and transport strategy.
• SQL/viewer workflow.
• OS and hardware validation.
• Language expansion.
• CI and release gates.
• Developer experience polish.
• Beta exit and public release.

The detailed task list is maintained in the v1 Beta multiphase burndown.

Read The Beta Docs In This Order

1. Getting started for the shortest path to the LOGIT mental model.
2. Starter project guides for the shortest real setup path in each MVP language.
3. Developer instructions for configuration, sinks, rotation, SQL storage, and troubleshooting.
4. SQL inspection and viewer workflow for the retained-log side of the product story.
5. Install and package status for the real state of each binding.
6. SDK architecture for the contract, schema, sink, and conformance layers.
7. Language matrix for readiness by binding.
8. Known limitations for the current gaps.
9. Binding playbook if you want to add or harden a language.

Beta Control Documents

These pages define how the project will actually reach Beta:

• Beta roadmap for the public phase-by-phase delivery path.
• Beta readiness rubric for how percentages and support claims should be interpreted.
• LOGIT contract matrix for the public field-by-field contract status.
• Config schema audit for how the current schemas align with the contract and where Beta freeze work remains.
• LOGIT lifecycle and compatibility rules for construction, emit, flush, close, and unsupported-field expectations.
• Binding compatibility matrix for the binding-by-binding reality of lifecycle and advanced-feature support.
• Error taxonomy and unsupported-field policy for configuration failure categories and unsupported-field behavior.
• Beta schema version strategy for how the current v0.2 schema should freeze into a Beta-supported contract.
• Beta burndown for the detailed task ledger.