The security 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. Guarding Secrets & Credentials

   When you deployed to the target sites, one line carried a promise we hadn't yet kept:

   series · Security & governance · 2026 · Mansour Ayouni · 2 of 8 blocks kept their promise
2. Governing a Project's Security

   The secrets narration showed a single stzSecret — a value that redacts itself and reveals only to an effectful actor. A real project has many secrets, several sites, and more than one actor, and the risk isn't one leaked key — it's the scatter: keys created...

   series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
3. The Front Door

   Every application eventually needs to answer "who is this?" And almost every application answers it badly the first time, not through carelessness but because the field is full of details that look optional and are not.

   series · Security & governance · 2026 · Mansour Ayouni · 0 of 10 blocks kept their promise
4. Answerable Forever

   stzGovernance.RecordDecision carried this comment:

   series · Security & governance · 2026 · Mansour Ayouni · 0 of 7 blocks kept their promise
5. Attestation and Export

   I1 made the ledger hash-chained and sealable, which makes a file tamper-evident. That is necessary and not sufficient. An auditor holding the file still has to ask: who exported this, when, over what range, under which key, and how do I check it? Those ques...

   series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
6. Detection over Sequences

   Softanza is full of rules. A graph rule asks whether a sandboxed actor can reach an effectful capability. A posture invariant asks what is true of the system right now. An org rule asks whether one position both approves and executes.

   series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
7. The Drill

   Seven phases built a system that witnesses, judges, correlates, contains and attests. Every one of them was guarded — but always with events the guard itself created.

   series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
8. The Security Event

   Softanza detects a great deal. A WebAuthn signature counter that fails to advance — the textbook cloned-credential signal. A SAML assertion presented twice. An HMAC that does not match. A nonce reused for the same key.

   series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
9. The Incident

   I4's case says what fired and photographs the moment. That is the right thing to keep, and the wrong thing to hand a human. An investigator needs the story: who, in what order, how far they could have gone, what is exposed, and what has been done about it.

   series · Security & governance · 2026 · Mansour Ayouni · not run: does not load as written
10. The Security Ledger

    It usually means a text file. Anyone who can write to it can rewrite it, and nothing about the file objects. "Trust me, it's in the log" is not a security property — which is why the industry built hash chains, transparency logs and WORM storage around the...

    series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
11. The Governed Response

    Witness, detect, reconstruct — none of those change anything. Contain does: it revokes a session, locks an account, rotates a secret. This is where a security system is most useful and most dangerous, and it is exactly where the library already has a doctrine:

    series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
12. The Rest of the Seams

    I2's first pass wired six classes and stopped. The design doc's section 7 table kept the rest of the rows in plain sight, and the completion document said so as the system's largest honest gap: a detection sees only what a seam emits.

    series · Security & governance · 2026 · Mansour Ayouni · not run: does not load as written
13. The Seams

    Three unrelated things happen to a running application: someone probes a signed-request gateway, someone guesses at the login door, and a sandboxed agent reaches for a production secret. Every one of those was already detected by Softanza.

    series · Security & governance · 2026 · Mansour Ayouni · not run: touches files, the network, the clock or chance
14. The Sentinel

    I3's detections judge when asked. Somebody still has to ask, and an investigation that begins with "did anyone look at the ledger today?" has already lost. The sentinel asks on a cadence — and, crucially, speaks only when something changes.

    series · Security & governance · 2026 · Mansour Ayouni · not run: does not load as written