Softanza
StartFrançais
Softanza
StartFrançais
Reference · Systems & runtime

Web & app server

33 functions in 20 classes, grouped by what they do, each with the explanation the library gives of itself.

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

  • IsRunning server lifecycle in stzAppServer
  • IsObserved routing interface in stzAppServer
  • IsGoverned governance + cross-part audit in stzAppBackend
  • IsReachable Is the far backend actually answering? (stzAppServer serves /health with no route declared, so this needs nothing from the model.) in stzAppBackend
  • IsSandbox a double declares itself -- see stzServiceRegistry in stzPaymentsSandbox
  • IsEphemeral a directory survives a restart in stzFileBlobStore
  • IsLocalReal a genuine local equivalent, not a fake -- see stzServiceRegistry's postures in stzFileBlobStore
  • HasRoute Exact-only presence check (kept for back-compat / introspection). in stzAppRouter

Finding

  • LastMs The duration of the last crossing (ms, monotonic clock) -- the marshalling cost of one Create/Rows/RowCount, either mode. in stzAppBackend
  • LastStatus The HTTP status of the last crossing, either mode (0 = it never completed). 401 here means the far side refused the signature. in stzAppBackend
  • LastRoundtripMs governance + cross-part audit in stzAppBackend

Counting and measuring

  • MeanCrossingMs Mean crossing cost over the whole ledger (refusals, at 0 ms, excluded -- they never crossed). in stzAppBackend
  • NumberOfCallsTo how many times a URL was asked for -- the assertion that catches an N+1 or a retry storm. in stzHttpSandbox
  • NumberOfCalls COST: the fee-free promise, made measurable in stzLlmSandbox
  • Size listing, the S3 idiom in stzFileBlobStore

Replacing and setting

  • SetAgentSlice How long a single serve slice may park on the socket before due agents are ticked. Smaller = crisper agent timing, more loop turns. in stzAppServer
  • SetSecureCookies Add Secure to the auth cookies -- TRUE whenever the listener is TLS, so the session cookie never travels in clear text. in stzAppServer
  • SetPhase the phase -------------------------------------------------------- :development / :emulated -> sandboxes are expected. :production -> they are a violation. The phase is the SAME switch stzDelivery already uses, so nothing new decides what is real. in stzServiceRegistry
  • SetActor Bind the acting actor: cross-part WRITES then require an effectful one (an LLMActor reads the whole solution and commits none of it). Reads are sensing and stay open. Unbound = ungoverned (dev). in stzAppBackend
  • SetSigningKey The shared secret that authenticates the crossing. Set it on BOTH sides: the HOST uses it to require a signature, the CLIENT to produce one. It is the same secret, so this one call serves both roles -- which is also why a real deployment must deliver it out of band (env, vault, stzSecretStore), never in the model file or the command line. in stzAppBackend
  • SetStrict strictness in stzHttpSandbox
  • SetFallback A catch-all answer, for pipelines where the text does not matter and only the SHAPE does. Setting one turns strictness off for unmatched prompts. in stzLlmSandbox
  • SetParams Route path params (bound by the router: /user/:id -> Param("id")). in stzAppRequest

Removing

  • Delete routing interface in stzAppServer
  • Remove S3's DELETE is idempotent: removing what is not there SUCCEEDS. Kept, because a test that asserts otherwise would be asserting a fiction. in stzFileBlobStore

Converting

  • ParseHttpRequest Parse one complete HTTP/1.1 request (the engine frames it: full headers + Content-Length body, CRLF line endings). in stzAppServer
  • AsRuleGraph NOTE this does NOT duplicate the invariants above. Findings from Findings() already carry the report's shape, so the registry joins the shared CI gate directly: oReport.IngestLegacy(oReg.Findings(), "services"). What the GRAPH adds is the question a flag check cannot ask -- which PART of a solution depends on a fake -- and that needs the delivery's parts joined to these nodes (see stzDelivery.AsRuleGraph and stzServiceRuleSet). in stzServiceRegistry

Showing, drawing and formatting

  • Show governance + cross-part audit in stzAppBackend

Reading and writing

  • SaveModelTo Cells carry their TYPE (n/s) rather than being sniffed on the way back in: a price must stay a NUMBER for the revenue maths, and "looks numeric" is exactly how "007" silently becomes 7 -- a defect this library already paid for once in the CSV reader. Fields are percent-escaped . in stzAppBackend
  • Save the PORT contract ------------------------------------------------ Overwrites silently when the key exists, exactly as S3 does. in stzFileBlobStore
  • SaveFile large payloads, without passing through RAM in stzFileBlobStore

Walking and applying

  • Run Serve forever (until the process is killed or Stop() is called from a handler). The documented blocking entry point. in stzAppServer
  • RunFor With agents hosted, the serve slice is BOUNDED: ServeOne(nLeft) would otherwise park on the socket for the whole remaining time whenever no request arrives, and the agents -- which live on this same loop -- would never tick. So we serve for at most @nAgentSliceMs, then tick whatever is due, and repeat. Requests and perceive-decide-act interleave on ONE loop. in stzAppServer

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

Narrations about this area