Reference
Normative, lookup-oriented documentation for exd — the manifest format, the SDK surfaces, the HTTP server API, the CLI, and the telemetry contract. This is the material you reach for to answer "what is the exact shape of X", not a guided walkthrough; for that, start with the tutorials.
New here? Read core concepts first — every other page assumes that vocabulary — then jump to the section you need.
Sections
| Section | What's in it |
|---|---|
| Core concepts | Definitional vocabulary — flag, variant, rule, segment, environment, tenant, flag namespace, evaluation context, evaluation result. |
| Manifest | The on-disk TOML file tree that describes a flag namespace: directory layout, the namespace.toml / flags/ / segments/ files, predicates, buckets, the resolution algorithm, the diagnostic vocabulary, packaging. Normative — every lint diagnostic and evaluation behavior is anchored here. |
| SDKs | Per-language client surface — Rust, TypeScript, Python, Java, Go. All FFI into the same validator core, so lint and eval behave identically on every runtime. |
| Server API | HTTP reference for exd-server, broken out by route family: tenants, namespaces, manifest, evaluation, events. |
| CLI | The exd, exd-server, and exd-server-admin binaries — one page per subcommand, plus shared conventions. |
| Telemetry | The evaluation-record wire contract, the sink contract, the provenance envelope, the warehouse table contract, and the exd telemetry query catalog. |
| Access control | The tenant / flag-namespace permission model. |
| Tokens | Token types, scopes, and the token-management API. |