Build log | Krishnendu Biswas https://krishnendu.me/log/ What I build and run with agents, reviewed before publishing. en Sat, 03 Oct 2026 20:00:00 +0530 Rebuilt this site and ran a fact audit on its numbers https://krishnendu.me/log/2026/10/site-rebuild-fact-audit/ https://krishnendu.me/log/2026/10/site-rebuild-fact-audit/ Sat, 03 Oct 2026 20:00:00 +0530 This site went from a game-themed page to a professional portfolio. A planning model wrote the spec, a builder agent worked through it from a task board, and served screenshots were reviewed before it went live. The diagrams and charts are now 14 inline SVG figures, each with a data table. What changed: This site went from a game-themed page to a professional portfolio. A planning model wrote the spec, a builder agent worked through it from a task board, and served screenshots were reviewed before it went live. The diagrams and charts are now 14 inline SVG figures, each with a data table.

Why it matters: I mapped 380 numbers on the site to a source line. A script measures diagram text on 23 pages at 3 screen widths. Rows under the 13px floor went from 18 to 0.

How a site change moves from plan to mergeFive steps left to right: plan, build, fact audit, screenshot review, merge. A return arrow runs from fact audit back to build, labelled fabricated draft discarded.PlanBuildFact auditScreenshotreviewMergeFabricated draft discarded

Result: Merged and live on 3 Oct 2026, with 0 failing rows on the text size check.

Lesson: An earlier draft contained claims that did not match my records, and the fact audit caught them before release. An automated review also passed a build with visible defects, so every release now gets a separate check of the rendered pages before it goes live.

Sources: Task card: v2 visual redesign with diagrams and charts, including the reviewer run and the model fallback, Task card: v2.1 diagram polish, facts map and diagram text size check, Task card: v1.2 agent case studies, where the unmatched claims were found

]]> Moved the agents from laptop to cloud server https://krishnendu.me/log/2026/09/cloud-migration/ https://krishnendu.me/log/2026/09/cloud-migration/ Sun, 20 Sep 2026 20:00:00 +0530 Hermes Agent, the open-source framework my agents run on, moved from a Linux virtual machine on my MacBook (M1 Max) to a cloud server running Ubuntu. The model gateway (9Router, which sends each request to a model) and the provider sync now run as system services on that server. What changed: Hermes Agent, the open-source framework my agents run on, moved from a Linux virtual machine on my MacBook (M1 Max) to a cloud server running Ubuntu. The model gateway (9Router, which sends each request to a model) and the provider sync now run as system services on that server.

Why it matters: The agents keep working when the laptop is closed. Scheduled jobs and the daily progress report no longer depend on my machine being awake.

Before and after the move to a cloud serverLeft: the laptop setup, a Linux virtual machine on a MacBook (M1 Max) running Hermes Agent and the model gateway. Right: the cloud server running Ubuntu with Hermes Agent, and the model gateway and provider sync as system services. Arrow between them labelled moved 20 Sep 2026.Before: MacBook (M1 Max)Linux virtual machineHermes AgentModel gatewayAfter: cloud server,UbuntuHermes AgentModel gateway, as a serviceProvider sync, as a serviceMoved 20 Sep 2026

Result: Gateway and sync were deployed as services on 21 Sep 2026.

Lesson: The date of this move rests on a billing record and a boot log rather than my memory. I now log milestones to an append-only ledger with an ID and cite that ID when I write about them.

Sources: Ledger: first billed day of the cloud server (billing record, amount withheld), Ledger: cloud server first boot on 20 Sep, from the system boot log, Ledger: agent runtime moved from laptop to cloud server, Ledger: model gateway and provider sync deployed as system services

]]>