<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://suhailmohebi.com/feed.xml</id>
  <title>Suhail Mohebi — operating notebook</title>
  <subtitle>Field notes and methods for verifiable work with AI agents.</subtitle>
  <link href="https://suhailmohebi.com/feed.xml" rel="self" type="application/atom+xml"/>
  <link href="https://suhailmohebi.com/"/>
  <updated>2026-07-17T12:00:00Z</updated>
  <author><name>Suhail Baqer Mohebi</name><uri>https://suhailmohebi.com/</uri></author>
  <entry>
    <id>https://suhailmohebi.com/notes/when-success-is-still-broken/</id>
    <title>When ‘success’ is still broken</title>
    <link href="https://suhailmohebi.com/notes/when-success-is-still-broken/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>Why a 200 response, green check, or finished-looking agent answer can still hide a failed user outcome—and what evidence closes the gap.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/stale-worktree-that-passed/</id>
    <title>The stale worktree that passed every check</title>
    <link href="https://suhailmohebi.com/notes/stale-worktree-that-passed/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>A postmortem pattern for the dangerous case where tests are green because they ran against the wrong source of truth.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/local-model-field-notes/</id>
    <title>Local model field notes</title>
    <link href="https://suhailmohebi.com/notes/local-model-field-notes/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>A living test format for LM Studio, Gemma-family models, context limits, privacy, latency, failure modes, and honest cloud comparisons.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/position-sizing-for-agent-autonomy/</id>
    <title>Position sizing for agent autonomy</title>
    <link href="https://suhailmohebi.com/notes/position-sizing-for-agent-autonomy/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>What derivatives, portfolio construction, and surviving volatility teach about permissions, stop conditions, and bounded agent action.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/hermes-on-telegram/</id>
    <title>Hermes on Telegram: a pocket control plane</title>
    <link href="https://suhailmohebi.com/notes/hermes-on-telegram/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>How a Telegram-facing agent routes questions, monitoring, digests, diagnostics, bounded workflows, evidence, and human approvals without exposing the underlying systems.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/designing-skills-and-loops/</id>
    <title>Designing skills and loops for certain and uncertain outcomes</title>
    <link href="https://suhailmohebi.com/notes/designing-skills-and-loops/"/>
    <updated>2026-07-17T12:00:00Z</updated>
    <summary>How to package agent skills as explicit contracts, use deterministic loops for exact predicates, and bound non-deterministic work with rubrics, budgets, reviewers, and human gates.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#kimi-k3-first-signal-not-verdict</id>
    <title>Kimi K3: open does not automatically mean local</title>
    <link href="https://suhailmohebi.com/#kimi-k3-first-signal-not-verdict"/>
    <updated>2026-07-16T12:00:00Z</updated>
    <summary>Kimi K3 sharpened a distinction I keep returning to: on-device AI runs on one machine, private AI runs inside infrastructure you control, and open frontier AI can publish weights while still requiring data-centre-scale hardware. The weights are opening; inference, caching, routing and deployment correctness are becoming the moat.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#notebook-becomes-operating-system</id>
    <title>The notebook becomes an operating system</title>
    <link href="https://suhailmohebi.com/#notebook-becomes-operating-system"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A timeline of AI-assisted work is useful, but a system is more useful. We reorganised this notebook around the loops behind the work — orientation, direction, building, verification, memory and learning — then connected every deep dive to the larger practice.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/the-toolbench/</id>
    <title>The four-agent toolbench</title>
    <link href="https://suhailmohebi.com/notes/the-toolbench/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>Claude, Codex, Droid and Cursor — what each is best at, how to route work between them, and the one mirrored context file that keeps them in sync.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/tuning-the-knobs/</id>
    <title>Tuning the knobs: models &amp; settings</title>
    <link href="https://suhailmohebi.com/notes/tuning-the-knobs/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>Reasoning effort, model tier, temperature, tool-use — and separate saved profiles for coding speed versus agentic work, with copy-usable configs.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/voice-driven-development/</id>
    <title>Voice-driven development</title>
    <link href="https://suhailmohebi.com/notes/voice-driven-development/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>Driving a fleet of agents by talking — handling transcription artifacts, and the shorthand that expands one spoken phrase into a whole workflow.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/the-cookbook/</id>
    <title>The cookbook</title>
    <link href="https://suhailmohebi.com/notes/the-cookbook/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>Seven copy-usable recipes — cache-bust blast radius, CSP hash recompute, adversarial verify, config recovery from live headers — each with the reasoning.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/local-uncensored-models/</id>
    <title>Local &amp; uncensored models</title>
    <link href="https://suhailmohebi.com/notes/local-uncensored-models/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>Running open-weight models on your own machine — the stack, why privacy and cost make it worth it, and a plain, responsible explanation of what abliteration is.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/the-verification-loop/</id>
    <title>The verification loop</title>
    <link href="https://suhailmohebi.com/notes/the-verification-loop/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A practical evidence ladder for turning ‘looks right’ into a result another person or agent can trust.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/context-without-oversharing/</id>
    <title>Context without oversharing</title>
    <link href="https://suhailmohebi.com/notes/context-without-oversharing/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>How to give agents enough context to work well while keeping private systems, personal details, credentials, and non-public facts out of public artifacts.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/from-brief-to-published-page/</id>
    <title>From rough brief to published page</title>
    <link href="https://suhailmohebi.com/notes/from-brief-to-published-page/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>How a loose idea becomes a structured, visual, connected page—and leaves the seed for what to publish next.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/live-truth-before-local-assumptions/</id>
    <title>Before the AI edits: find the live truth</title>
    <link href="https://suhailmohebi.com/notes/live-truth-before-local-assumptions/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A source-of-truth protocol for checking production, deploy state, repositories and generated artifacts before an agent changes the wrong version.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/handoff-packets/</id>
    <title>Handoff packets that do not lose the plot</title>
    <link href="https://suhailmohebi.com/notes/handoff-packets/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A copy-usable transfer format for current state, decisions, evidence, stop conditions, and the smallest safe continuation.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/parallel-agents-without-collisions/</id>
    <title>Parallel agents without branch collisions</title>
    <link href="https://suhailmohebi.com/notes/parallel-agents-without-collisions/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A practical ownership and integration method for running agents in parallel without colliding on shared files, generated artifacts, cache versions, or release state.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/notes/decision-ledgers/</id>
    <title>Decision ledgers for long-running agent work</title>
    <link href="https://suhailmohebi.com/notes/decision-ledgers/"/>
    <updated>2026-07-14T12:00:00Z</updated>
    <summary>A practical way to preserve why an agent rule exists, append evidence that confirms or changes it, and name the trigger for its next review.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#this-site-built-in-one-sitting</id>
    <title>This site, built in one sitting</title>
    <link href="https://suhailmohebi.com/#this-site-built-in-one-sitting"/>
    <updated>2026-07-13T12:00:00Z</updated>
    <summary>The notebook you're reading was designed, coded, and deployed inside a single conversation. I pointed at a domain that had sat untouched on a website builder for years; the AI checked its DNS, proposed the migration, and built this — aurora gradients, particle field, command palette and all. Very meta. Hello, world.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#content-cluster-overnight</id>
    <title>A content cluster, shipped overnight</title>
    <link href="https://suhailmohebi.com/#content-cluster-overnight"/>
    <updated>2026-07-12T12:00:00Z</updated>
    <summary>We planned, wrote, cross-linked, and published a full topical content cluster — hub pages, reference guides, and spokes — in one overnight session, complete with citations, structured data, and social cards generated to match the template family. Proof that an AI can hold a whole content architecture in its head at once.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#multi-agent-site-audit</id>
    <title>The multi-agent site audit</title>
    <link href="https://suhailmohebi.com/#multi-agent-site-audit"/>
    <updated>2026-07-11T12:00:00Z</updated>
    <summary>Instead of one AI reading one file at a time, we fan out: a dozen specialised agents audit a whole site in parallel — accessibility, structured data, performance, links, consistency — then a separate adversarial council tries to refute every finding before it reaches me. False positives die in review, not in production.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#template-redesign-verified</id>
    <title>A template redesign, verified page by page</title>
    <link href="https://suhailmohebi.com/#template-redesign-verified"/>
    <updated>2026-07-09T12:00:00Z</updated>
    <summary>A full visual redesign of one page template rolled out across twenty pages — new hierarchy, cleaner layout, consistent design tokens — verified page by page in a real browser before shipping. The AI takes the screenshots; the human takes the decisions.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#optimising-for-ai-search</id>
    <title>Optimising for AI answers, not just Google</title>
    <link href="https://suhailmohebi.com/#optimising-for-ai-search"/>
    <updated>2026-07-07T12:00:00Z</updated>
    <summary>Search is splitting: classic blue links on one side, AI answers on the other. We build entity hub pages, definition-first answer blocks, and machine-readable facts so primary sources are easy for search engines and AI assistants to retrieve and cite. SEO's next chapter, tested in public.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#let-data-overrule-taste</id>
    <title>Let the data overrule the taste</title>
    <link href="https://suhailmohebi.com/#let-data-overrule-taste"/>
    <updated>2026-07-02T12:00:00Z</updated>
    <summary>We'd banned a certain inline prompt for looking pushy. Then analytics showed pages carrying a subtle, dismissible version retained readers far better than we assumed — so we reversed the rule, rolled it out only where relevant, and pinned the list with a test so it can't silently grow.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#domain-expert-chatbot</id>
    <title>A domain-expert chatbot</title>
    <link href="https://suhailmohebi.com/#domain-expert-chatbot"/>
    <updated>2026-06-27T12:00:00Z</updated>
    <summary>We shipped a site chatbot built around a curated knowledge base and a live-fetched fact source. It answers visitor questions, proposes actions the server validates before running, and can hand a conversation to a human. Built, tested, and iterated across several sessions of this partnership.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#lean-mobile-pages</id>
    <title>Lean mobile pages</title>
    <link href="https://suhailmohebi.com/#lean-mobile-pages"/>
    <updated>2026-06-24T12:00:00Z</updated>
    <summary>Mobile readers don't scroll through essays. We restructured a mobile template around a lean above-the-fold — the essentials first, the deep detail collapsed behind intent. Load less, keep more.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#teaching-ai-to-distrust-itself</id>
    <title>Teaching the AI to distrust itself</title>
    <link href="https://suhailmohebi.com/#teaching-ai-to-distrust-itself"/>
    <updated>2026-06-20T12:00:00Z</updated>
    <summary>The most useful pattern we've found: don't let one AI pass-grade its own homework. Significant changes go through sign-off batches — independent review lenses, contamination sweeps for stale branches, and pre-push audits that catch what a single context window can't hold.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#shipping-every-surface-in-sync</id>
    <title>Shipping across every surface at once</title>
    <link href="https://suhailmohebi.com/#shipping-every-surface-in-sync"/>
    <updated>2026-06-03T12:00:00Z</updated>
    <summary>One change can touch dozens of surfaces: the page, the indexes, structured data, sitemaps, machine-readable files, tests. We turned that into a repeatable checklist the AI runs end to end — so a launch is a review, not a scramble.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#crossing-eighty-articles</id>
    <title>Crossing eighty articles</title>
    <link href="https://suhailmohebi.com/#crossing-eighty-articles"/>
    <updated>2026-05-13T12:00:00Z</updated>
    <summary>The library passed eighty published articles — every one fact-checked against primary sources, structured for both human readers and machine retrieval, and run through an automated ten-point checklist before it ships.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#two-sites-two-jobs</id>
    <title>Two sites, two jobs</title>
    <link href="https://suhailmohebi.com/#two-sites-two-jobs"/>
    <updated>2026-05-04T12:00:00Z</updated>
    <summary>We split one project into two sites with distinct roles — a primary destination and a separate evidence-first layer for references and analysis — deliberately connected but never cross-wired. Two jobs, cleanly separated.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#interactive-calculator</id>
    <title>An interactive calculator</title>
    <link href="https://suhailmohebi.com/#interactive-calculator"/>
    <updated>2026-04-20T12:00:00Z</updated>
    <summary>An interactive calculator that turns confusing unit math into a few guided inputs — built mobile-first with progressive disclosure and shipped after real-device testing. Still one of the most-used tools we've built.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#war-reached-dubai</id>
    <title>The night the war reached Dubai</title>
    <link href="https://suhailmohebi.com/#war-reached-dubai"/>
    <updated>2026-02-28T12:00:00Z</updated>
    <summary>On 28 February 2026, Iran launched missile and drone attacks on the UAE. A Shahed-238 drone struck the forecourt at Fairmont The Palm, while air defences intercepted incoming weapons over Dubai ( UAE Ministry of Foreign Affairs ; Human Rights Watch ). We were lucky; many weren't. That week changed how I work: everything that could be delegated got delegated, verified, and shipped. Every entry above this one traces back to that decision.</summary>
  </entry>
  <entry>
    <id>https://suhailmohebi.com/#where-this-started</id>
    <title>Where this started</title>
    <link href="https://suhailmohebi.com/#where-this-started"/>
    <updated>2026-01-15T12:00:00Z</updated>
    <summary>A founder in Dubai, a static site, and an AI in a terminal. What began as &quot;help me fix this page&quot; became a standing partnership with its own memory, playbooks, and division of labour. This notebook is the public record of where it goes.</summary>
  </entry>
</feed>
