<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Operator&apos;s Log — LanternOps</title><description>The weekly record of one operator running three businesses with managed AI teams. Real numbers, real artifacts, misses included.</description><link>https://lanternops.io/</link><atom:link href="https://lanternops.io/log/rss.xml" rel="self" type="application/rss+xml"/><item><title>Week five: the ceiling moved</title><link>https://lanternops.io/log/2026-07-13-week-five/</link><guid isPermaLink="true">https://lanternops.io/log/2026-07-13-week-five/</guid><description>The week ending July 12. The fleet worked 430 hours against 28 of mine, the widest gap yet, and the reason is a security review that ran itself. Breeze closed a twelve-finding OAuth audit, hardened the agent trust boundary, and started speaking four new languages.</description><pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Week four: one policy, every org</title><link>https://lanternops.io/log/2026-07-06-week-four/</link><guid isPermaLink="true">https://lanternops.io/log/2026-07-06-week-four/</guid><description>The week ending July 5. Breeze stopped treating an MSP as a pile of separate customers and let one policy own the whole book of business. The money side grew deposits and scheduled reports, and Hive turned the lights on in its own house.</description><pubDate>Mon, 06 Jul 2026 00:00:00 GMT</pubDate></item><item><title>Week three: hardening the house</title><link>https://lanternops.io/log/2026-06-29-week-three/</link><guid isPermaLink="true">https://lanternops.io/log/2026-06-29-week-three/</guid><description>The week ending June 28. After building the money side, Breeze spent the week locking the doors: a security and authorization sweep, vulnerability management, EDR, and a framework upgrade under the whole thing. And the brand I called out last week as the model&apos;s default finally became a choice.</description><pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Week two: Breeze learns to get paid</title><link>https://lanternops.io/log/2026-06-22-week-two/</link><guid isPermaLink="true">https://lanternops.io/log/2026-06-22-week-two/</guid><description>The week ending June 21. Breeze grew the whole money side of a business in seven days, quotes, invoices, contracts, and a catalog, while the engine taught itself to run live agents from a dashboard and LanternOps started teaching in public.</description><pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Week one: the engine keeps the books</title><link>https://lanternops.io/log/2026-06-15-week-one/</link><guid isPermaLink="true">https://lanternops.io/log/2026-06-15-week-one/</guid><description>The first full week the fleet counted itself, June 8 to 14. A heavy one: Breeze shipped v0.70.0 with native ticketing, privileged access, and an in-Excel client assistant, while the engine grew two new triage colonies of its own.</description><pubDate>Mon, 15 Jun 2026 00:00:00 GMT</pubDate></item><item><title>What the fleet already built</title><link>https://lanternops.io/log/2026-06-09-foundation/</link><guid isPermaLink="true">https://lanternops.io/log/2026-06-09-foundation/</guid><description>The record starts here. Before week one of the log: a brand built in two days, an open-source RMM with 1,300+ commits, three more products in flight, and the engine that runs it all. Reconstructed numbers, honestly marked.</description><pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate></item></channel></rss>