The KWAM Language · kwam.dev/v0.2
One auditable file co-specifies discovery, fault-domain replication, an SLA guard, authorized deploy, RBAC, and metrics. The compiler checks the durability nines against the replication and failure math, and rejects a guard that claims more than the math backs.
KWAM is declarative on purpose, so every program is total, auditable, and safe to lower.
A KWAM program describes what resilience you want, the fault domains to spread across, the durability to hold, who may deploy, what to watch, and the runtime makes it so. There are no loops, no user-defined functions, and no imperative verbs. That restraint is the point: it keeps the interpreter total and every program reviewable line by line.
Discovery, replication, the SLA guard, authorized deploy, RBAC/capabilities, and metrics live in one file — not scattered across YAML, scripts, and dashboards.
The strongest claim the compiler will let you assert is N-nines durability + zero silently-corrupted bits (SHA-256 detection) + a bounded per-bit restore MTTR — never "zero loss."
Every block schema is closed; an unknown key is a parse error, not a silent drop. All validation errors are fatal and fail closed.
A guard states the SLA; the compiler checks it against the replicate math.
apiVersion "kwam.dev/v0.2"
replicate code_and_data {
factor 3
anti_affinity [rack, pdu, spine, az] # fault-domain independence
}
guard sla {
durability 6nines # checked vs the replicate/MTTR/MTBF math — 11nines would be REJECTED
mttr_restore 90s # per-bit, INDEPENDENT single-node loss
integrity sha256 # zero silently-corrupted bits
}Each block lowers to one typed policy object. Full reference →
Bootstraps the governed control plane: identity, transport, ports, seeds, the trust anchor, and the kill-switch endpoints.
The in-memory per-node micro-service image: a content-addressed image cid, sandbox tier, health signals, hot-swap safepoint.
SWIM-style gossip membership + nearest-neighbor mesh, with an optional narrow tiny-LLM negotiator that only re-ranks candidates.
Replica factor + anti_affinity over fault domains; the placer keeps replicas in distinct domains.
The SLA: durability in nines, the per-bit mttr_restore, mandatory integrity sha256, and audited MTBF inputs.
RBAC: principals, capabilities, the trust anchor, the sandbox floor, and scoped, non-default discovery.
An authorized rollout, gated on an externally-minted, signed consent reference: waves, bake, rollback.
Binds an observable (durability, restore p99, silent-corruption count) to a target + window; feeds the guard's error budget.
Selects the hardware/interconnect model (h100, tpu, trainium) and its latency + health hooks.
The small glue: import / use bring in signed, content-addressed modules; let binds reusable values; expressions are literals, references, lists/maps, interpolation ${expr}, and a guarded ternary. Nothing more.
KWAM applies the same discipline to its own claims that it applies to durability.
KWAM is our intellectual property, grounded in Swiss law.
KWAM — its source code, the KWAM language, the JHMM reconstruction orchestrator, the deterministic codec runtime, and all associated AI components — is a proprietary computer program and the sole and exclusive intellectual property of KWAM.CH. As a computer program it is a protected work under the Swiss Federal Act on Copyright and Related Rights (Copyright Act, CopA), and the exclusive rights of use vest in KWAM as employer; it is further protected as a trade secret under the Swiss Federal Act Against Unfair Competition (UCA). KWAM is offered by private licence only. All rights reserved.
CopA (SR 231.1) Art. 2 para. 3 & Art. 17 · UCA (SR 241) Art. 6 · Governed by the laws of Switzerland · Place of jurisdiction: Zürich