# Kweb DB Core
`kweb-db-core` is a storage-only Rust library for a provenance-backed knowledge
web in SQLite. It has no HTTP server, binary target, frontend assets, prompt
policy, or user/root-role model. The Rust crate path is `kweb_db_core`.
This package continues the storage API previously packaged as `kweb` under a
name that makes its database-core role explicit.
The directory is self-contained. By default it enables the `bundled-sqlite`
feature, preserving a build that does not depend on a system SQLite installation:
```sh
cargo test
```
Embedding applications that manage SQLite themselves can opt out of bundling:
```toml
[dependencies]
kweb-db-core = { version = "0.2.3", default-features = false }
```
For an ordinary bundled build, applications can use:
```toml
[dependencies]
kweb-db-core = "=0.2.3"
```
The exact requirement is appropriate for an application that wants dependency
updates to be explicit. Library authors can use a normal compatible requirement
such as `kweb-db-core = "0.2"` when that better matches their release policy.
All of this crate's own dependency requirements are normal Cargo-compatible
ranges rather than exact transitive-version pins.
Applications open a database path with `Kmap::open`, create immutable
provenance, and reuse the returned provenance ID in node creates and updates.
Every create or update also requires a fresh random 16-byte `IdempotencyId`,
which the caller must reuse for retries. Nodes expose ordered fixed and recent
connection ID arrays; their caller owns all graph semantics and multi-node
orchestration.
The application default is `kweb.sqlite3` with a sibling
`kweb-provenance-artifacts/` directory. Large provenance payloads and attached
media live there while SQLite retains their immutable metadata and links. The
library reads externally stored provenance data transparently.
See [Specification.md](Specification.md) for the complete public contract,
compatibility guarantees, and deliberate limitations.