The performance series

Read in the repository's doc/narrations folder at commit 4a184e6f0. Every article is a page. On 2026-10-08 each was run in Haro's name inside the library, block after block; a block that kept its promise says so, the others are illustrations. The code of the articles is Haro code: where an article was written before the language took its present name, the name was changed and nothing else. Genre, area and series are read from the file's name and the year from its first commit: derived, until each article carries its own header.

A series is read in order.

1. Structured Logging with stzLog

   Most logging ends the same way: a wall of text, and a grep the next morning. The trouble is that the moment you format an entry into a line, you throw away its structure — the level, the category, the fields — and spend the rest of its life trying to parse...

   series · Performance · 2026 · Mansour Ayouni · 1 of 5 blocks kept their promise
2. Metrics and the Monitor

   P1 gave the engine senses -- it can read its own memory and CPU. But a sense is not an instrument: nothing named the readings, nothing kept them, nothing watched on a cadence. P2 adds the two missing objects.

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
3. The Governed Loop

   The notebook's pipeline ends where the stakes begin: Monitor -> Alert -> Analyze -> Optimize. The first three verbs only read; the fourth scales fleets, drains workers, restarts processes.

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
4. Judgment

   The industry adds performance thresholds after the incident, in a monitoring tool, in that tool's language. Softanza's position is the notebook's original two words -- SLA: design -- the promise is part of the program, stated in the operational vocabulary n...

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
5. The Profile

   Everything before P5 measures: the stopwatch times, the senses read, the metrics keep, the seams attribute, the SLA judges.

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
6. The Seams

   P2 built the instruments; until now they measured what you handed them. P3 attaches them to the places where requests actually flow, so R (response time) and X (throughput) stop being examples and become your server's numbers. The whole attachment is one verb:

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
7. The Tail

   P4 admitted a limit honestly: alerts did not carry the trace ids of the requests that tripped them, because nothing captured traces per request. P2 owed the OTLP metrics batch a sibling for spans.

   series · Performance · 2026 · Mansour Ayouni · 0 of 3 blocks kept their promise
8. The Driven Load

   P7 ruled the R-vs-X harness out honestly: the knee -- response time exploding as throughput nears its ceiling -- is queueing's signature, queueing needs CONCURRENT arrivals, and a serial in-process harness cannot produce them.

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
9. The Frame Profiler

   The senses (P1) say WHETHER the process computes; the metrics (P2) say what each operation costs in aggregate. Neither says WHERE inside your own code the time lives. That is a profiler's question, and P10 answers it two honest ways at once.

   series · Performance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
10. Labels and Dimensions

    The vs-the-field document called flat metric names this system's most consequential absence: http.request.ms measured everything, so "which route is slow?" had no direct answer.

    series · Performance · 2026 · Mansour Ayouni · 0 of 4 blocks kept their promise
11. Log-Trace Correlation

    After P8 the system had spans, metrics and logs -- but the logs stood apart: a log line knew when but not for which request. The field solves this with context propagation frameworks;

    series · Performance · 2026 · Mansour Ayouni · 0 of 3 blocks kept their promise