Sarvalekha.

Public product notes

Foundation, in context.

The common framework for the Sarvalekha ecosystem.

Under development — not releasedProduct overview

Purpose & status.

Sarvalekha Foundation is the common development framework for the Sarvalekha ecosystem. Its independently usable Core brings schema-defined models, generated codecs and selected managed state, cache and embedded storage capabilities together. The renamed 1.0.0 framework remains in development.

Under development — not released. These notes do not supply a supported installation, operational signup or subscription.

Capability scope.

Development implementation

Start with a shared model

Generate models and codecs for C++, C, Java, C#, JavaScript, TypeScript, Go, Rust, Python, Swift and Kotlin. JSON and native binary formats have documented profiles; selected C++ outputs add Protobuf-related formats. Backend and compression support varies.

Development implementation

Add managed application state

The C++ managed runtime supplies typed editing, transactions, immutable reads, linear or branching histories and selected durable journals. Other language outputs have narrower model, platform and recovery boundaries.

Development implementation

Coordinate with explicit boundaries

Selected authority/client mechanisms coordinate accepted edits, retries and merges. Applications supply authentication, trusted sessions, transport, scheduling and conflict resolution; cross-service ACID is outside this scope.

Development implementation

Work with structured document formats

Selected profiles provide XML mappings, XSD operations and ZIP/OPC typed document parts with bounded opaque content. These file-format facilities do not provide a document renderer.

Development implementation

Choose the right storage and reuse profile

Optional C++ storage persists one managed root with an exclusive writer and immutable snapshots. Scalar and page-backed indexes, rebuildable values and data caches retain explicit validity, ownership and resource limits.

Important limitations.

  • Under development, with no published Foundation SDK artifact established by the source rename. Compiler/runtime, schema language and paired editor identities begin at 1.0.0; broad qualification and paired release remain separate.
  • Core can be used independently for data exchange without a product engine, cloud credentials or running service. Applications retain domain logic, user interfaces, authentication, transport and service authority.
  • Native components require C++23. Language and provider profiles have distinct prerequisites and do not establish universal parity.
  • The clean Foundation contract has no legacy adapters, old-data converter or automatic artifact-pin upgrade. Consuming applications require matched dependencies and separate qualification.
  • Eager storage retains complete roots. Page-backed indexes do not establish larger-than-RAM editing or a process-wide memory ceiling; no general SQL, graph, spatial or vector engine is implied.

A shared product foundation.

Foundation Core is independently usable. Optional Database, Platform and Diagnostics modules are planned; each service retains authority over its operations. The renamed 1.0.0 framework remains in development, and each consuming product needs its own integration qualification.