Concurrency & distribution

The story of this area, for a general reader: what a crafter does with it, an example run and its rated lanes, is on its Platform page.

The functions, by what they do

Testing and checking

• CanAdmit admission (the load-isolation primitive) in stzWorkerProfile
• Has queries in stzFacetCatalog
• IsConnected No global init required for the engine HTTP client. in stzNetwork

Finding

• LastTraceId The trace id assigned to the most recent Route (correlates the front host's record with the worker's _trace on the wire). in stzAppCluster
• LastCallMs Duration of the last FederatedCall, ms (gates + signing + transport; refusals cost what the gates cost). in stzComputeFederation
• LastSignature The envelope [ :kid, :ts, :nonce, :sig ] of the most recent SIGNED FederatedCall (empty [] if the last call was unsigned). in stzComputeFederation

Counting and measuring

• NumberOfTraces trace lookups in stzClusterTelemetry

Replacing and setting

• SetRateLimit Rate limit a facet at the front door: nRatePerSec sustained with a bucket of nBurst (the largest instantaneous burst absorbed). A facet with no SetRateLimit is UNLIMITED. Requests over the limit are shed with a -429 status before any worker is touched. in stzAppCluster
• SetCircuitBreaker Circuit breaker: after nThreshold consecutive failures a worker's circuit OPENS (it is skipped for nCooldownMs, then half-open: one probe re-closes on success or re-opens on failure). in stzAppCluster
• SetAuth HTTP auth (Basic by default; libcurl base64-encodes + handles the challenge). Use SetAuthType for digest/ntlm/negotiate/any. in stzHttpClient
• SetBearer Bearer / OAuth2 token auth. in stzHttpClient
• SetTimeout ── timeouts (engine-backed) ───────────────────────────── These now drive the custom HTTP/1.1 client's per-socket and connect deadlines via the engine, replacing the slice-2 no-ops. in stzHttpClient
• SetProxyAuth Proxy credentials, "user:pass". in stzHttpClient
• SetUserAgent stzNetwork.init handles its own fields. ── headers / cookies ──────────────────────────────────── in stzHttpClient
• SetClientCert mTLS: client certificate + private key (file paths, PEM). in stzHttpClient
• SetCookieFile Persistent cookies: read from / write to a Netscape cookie file. in stzHttpClient
• SetTraceParent ── distributed tracing (W3C Trace Context) ────────────── Inject a `traceparent` header so downstream services can correlate this request into a single distributed trace (Tier 2 observability). in stzHttpClient
• SetDefaultTimeouts Set the process-wide engine defaults (connect / request / idle in ms). 0 leaves a field unchanged. Affects every client. in stzHttpClient
• SetMutualTls Run the federation transport over WIRE mTLS: every FederatedCall now goes over a mutually-authenticated, encrypted mbedTLS channel -- this node PRESENTS pcCert/pcKey and VALIDATES the peer's server cert against pcCa (slices 2-3). Combined with governance (SLA) + request signing (per-request auth), this is the full node-to-node security stack: encrypted + mutually cert-authenticated + signed + governed. in stzComputeFederation

and 6 more in the reference

Adding

• AddProfile declaring the fleet composition ------------------------------------ Declare nWorkers processes of a profile (capability tag + caps). One @aFleet row per worker is created NOW (port assigned at Start), so FleetSize/WorkersOf are correct before and after launch. in stzAppCluster
• AddFacet Add a profile for a facet DEFINED IN THIS POOL'S CATALOG: capabilities, provenance and external tool are taken from the catalog. in stzWorkerPool
• AddActor Register an actor identity (stzSystemActor): the verified key id names the actor whose capability KINDS gate admitted tags. in stzNode
• AddKeyword TIER 2: the capability-lexical vocabulary -------------------------- Extend the synonym lexicon (a word that hints a facet). Capability names are matched automatically; keywords add natural phrasing. in stzRequestClassifier

Walking and applying

• RunLocal the running topology ----------------------------------------------- Every node = a child OS process on this machine, under REAL supervision, over the REAL wire (loopback). Same semantics as a multi-machine run; only the latency differs. (D4 scope: the first Supervise() group sets the strategy; every node is supervised.) in stzNodeApp
• Run running ------------------------------------------------------------ Thread pInput through every stage in order; each stage's output feeds the next. Returns the final output. Records a per-stage trace. A stage that RAISES is CONTAINED: the failure is traced, the facet slot is released (no leak), the pipeline HALTS and returns NULL, and Why()/ Failed() explain -- one bad stage never crashes the whole pipeline. in stzComputePipeline
• RunBatch Run many inputs through the WHOLE pipeline; returns a result list (same order). The trace reflects the LAST input. in stzComputePipeline

The explanations are the ones the library gives of itself, read from its documentation comments on 2026-10-01 04:14, from the library at commit 0e72e2e2c, by the library's own stzSelfDoc over 635 class sources.

The classes of this area

• stzAppCluster · 48 methods
• stzHttpClient · 45 methods
• stzComputeFederation · 29 methods
• stzWorkerPool · 25 methods
• stzWorkerProfile · 24 methods
• stzNodeApp · 20 methods
• stzClusterTelemetry · 19 methods
• stzNodeSupervisor · 19 methods
• stzComputePipeline · 18 methods
• stzNode · 17 methods
• stzTcpClient · 14 methods
• stzClusterSupervisor · 13 methods
• stzRequestClassifier · 13 methods
• stzFacetCatalog · 12 methods
• stzTcpServer · 12 methods
• stzWebSocket · 12 methods
• stzNetwork · 9 methods
• stzNodeRegistry · 8 methods

Narrations about this area

No narration is attached to this area yet.