KWAM Language: worked examples

fleet.kwam

The shape of a program

Profile → policy → server → discovery → client → replicate → guard → metrics → deploy.

A real KWAM program reads top to bottom as a single declaration of intent: choose the hardware profile, declare who may do what, stand up the server and discovery, pin a content-addressed client, spread replicas across fault domains, state the SLA, bind the metrics, and roll out under signed consent. Below is a representative excerpt, illustrative, not runnable, showing two of the nine blocks.

profile h100_dc {
  hardware     "h100"
  interconnect "nvlink+ib"
  health       [dcgm, nvml]
  # … profile tunables omitted …
}

guard sla {
  durability   6nines     # a DESIGN TARGET, checked vs the math
  integrity    sha256     # zero silently-corrupted bits
  on_violation quarantine
  # … MTTR, MTBF inputs, error budget omitted …
}

The complete worked program is provided to licensees.

What happens

At lowering and at runtime

At lowering

Verifies the trust anchor resolves and the imported module digest matches; confirms the pool identities hold the needed capabilities; refuses the rollout unless a consent reference is present and its scope is a subset of the token's resource glob; confirms the sandbox meets the floor; checks that 6nines is actually backed by the replication + MTTR + audited MTBF math; pins the cosigned client cid; arms the re-replication daemon and the kill-switches.

At runtime

Verifies the consent token's signature (against a key the server does not hold), freshness, and single-use status on every action; attests each target node's hardware-rooted quote before deploy; lets the tiny LLM propose only a permutation of enumerated candidates, off the critical path; on any restart, re-checks warm bits against the revocation set, not SHA alone.

The reject

When the validator says no

Change durability 6nines to 11nines and the compiler refuses: this is what makes "compiler-checked nines" credible rather than aspirational.

guard sla: REJECTED
  asserted: 11 nines   (far beyond what the configuration can back)
  backed:    6 nines   (under the correlated-failure model for this fleet)
  remedy:    strengthen replication / coding, or lower the claim to what the math supports

The honest headline 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. KWAM signs the number it can measure and reproduce, six nines, not the most flattering arithmetic. See the durability math →

Walk through it Reference

Legal

Ownership & governing law

KWAM is our intellectual property, grounded in Swiss law.

Intellectual property & governing law

KWAM is the sole and exclusive property of the owners of KWAM.CH

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