stateset-sdk 1.26.0

Rust SDK facade for StateSet iCommerce with feature-gated re-exports
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76

# stateset-sdk

[![crates.io](https://img.shields.io/crates/v/stateset-sdk.svg)](https://crates.io/crates/stateset-sdk)
[![docs.rs](https://docs.rs/stateset-sdk/badge.svg)](https://docs.rs/stateset-sdk)

**Start here.** The Rust facade for StateSet iCommerce — one dependency, one prelude,
feature-gated access to the commerce engine plus optional sync, crypto, policy, and
macro surfaces.

If you're writing Rust against StateSet, add this crate rather than picking sibling
crates by hand; it pins compatible versions of the whole set for you.

```toml
[dependencies]
stateset-sdk = { version = "1.26.0", features = ["full"] }
```

Or: `cargo add stateset-sdk --features full`

## Usage

```rust,no_run
use stateset_sdk::prelude::*;

# fn main() -> Result<()> {
let commerce = Commerce::new("store.db")?;

let customer = commerce.customers().create(CreateCustomer {
    email: "alice@example.com".into(),
    first_name: "Alice".into(),
    last_name: "Smith".into(),
    ..Default::default()
})?;
# let _ = customer;
# Ok(())
# }
```

## Feature Flags

| Feature | Description | Default |
|---------|-------------|---------|
| `core` | Primitives + Core + DB + Embedded + Observability | Yes |
| `crypto` | VES v1.0 cryptographic operations | No |
| `policy` | Declarative policy engine | No |
| `macros` | Proc macros (`StateSetId`, `GenerateDto`, `JsonSchema`) | No |
| `sync` | Outbox-driven sync engine and sequencer transport | No |
| `full` | Everything above | No |

## Sync Runtime

With `sync` enabled, `SyncRuntime` and `SyncRuntimeConfig` bundle the sync engine,
sequencer HTTP transport, and runtime auth into a single surface: config loading,
sync operations, JSON-ready snapshots, kernel receipt queries, and
confirmation/dead-letter inspection. `SyncRuntimeConfig` loads from a file, a JSON
string, or the environment via `from_file`, `from_json_str`, and `from_env`.

## What's Underneath

| Crate | Role |
|-------|------|
| [`stateset-embedded`](https://crates.io/crates/stateset-embedded) | The engine — commerce operations over SQLite or PostgreSQL |
| [`stateset-core`](https://crates.io/crates/stateset-core) | Domain models, repository traits, validation, errors |
| [`stateset-primitives`](https://crates.io/crates/stateset-primitives) | Typed IDs, `Money`, `CurrencyCode`, `Sku` |
| [`stateset-db`](https://crates.io/crates/stateset-db) | SQLite and PostgreSQL implementations |
| [`stateset-observability`](https://crates.io/crates/stateset-observability) | Metrics and tracing bootstrap |
| [`stateset-crypto`](https://crates.io/crates/stateset-crypto) | Canonical JSON, signing, hybrid PQ crypto |
| [`stateset-policy`](https://crates.io/crates/stateset-policy) | Declarative rule engine |
| [`stateset-sync`](https://crates.io/crates/stateset-sync) | Event-sourced outbox and sync engine |

Serving HTTP instead of embedding? See
[`stateset-http`](https://crates.io/crates/stateset-http).

## License

MIT OR Apache-2.0