<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jeremylongshore on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/jeremylongshore/</link><description>Recent content in Jeremylongshore on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Thu, 09 Apr 2026 23:29:08 -0500</lastBuildDate><atom:link href="https://startaitools.com/tags/jeremylongshore/index.xml" rel="self" type="application/rss+xml"/><item><title>IRSB Prometheus Metrics, STCI CSV Upload, and Brand Refresh</title><link>https://startaitools.com/posts/irsb-prometheus-metrics-stci-csv-upload-brand-refresh/</link><pubDate>Mon, 02 Feb 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/irsb-prometheus-metrics-stci-csv-upload-brand-refresh/</guid><description>&lt;p&gt;Five repos touched, none of them deeply. February 2nd was a polish day — finishing things started earlier in the week and cleaning up loose ends across the portfolio. Sixteen commits total, none individually dramatic but collectively moving four projects forward.&lt;/p&gt;
&lt;h2 id="irsb-monorepo-epic-1-complete"&gt;IRSB Monorepo: Epic 1 Complete&lt;/h2&gt;
&lt;p&gt;Five commits closing out Epic 1. The headline is a shared Prometheus metrics package extracted from the monorepo&amp;rsquo;s services.&lt;/p&gt;
&lt;p&gt;Each IRSB service was instrumenting its own metrics with slightly different label names, histogram buckets, and counter naming conventions. The inconsistencies were small but compounding:&lt;/p&gt;</description></item><item><title>IntentVision Phases 8-14 and Personal Brand Repositioning</title><link>https://startaitools.com/posts/intentvision-phases-eight-fourteen-personal-brand-repositioning/</link><pubDate>Sun, 01 Feb 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/intentvision-phases-eight-fourteen-personal-brand-repositioning/</guid><description>&lt;p&gt;February opened with an IntentVision sprint. Seven phases in a single day, pushing the product from a working dashboard toward something you could actually sell.&lt;/p&gt;
&lt;p&gt;Twenty-eight commits across three repos. Nineteen on IntentVision, eight on jeremylongshore.com, and one on bounties. The IntentVision work was the main event. The jeremylongshore.com repositioning was strategic. The bounties commit was governance.&lt;/p&gt;
&lt;h2 id="intentvision-phases-8-through-14"&gt;IntentVision: Phases 8 Through 14&lt;/h2&gt;
&lt;p&gt;The first seven phases (covered in a previous post) gave IntentVision its data layer, visualization primitives, and dashboard composition. Phases 8 through 14 are about operational maturity — the difference between a demo and a product.&lt;/p&gt;</description></item><item><title>IRSB Data Integrity Fixes and Portfolio Expansion</title><link>https://startaitools.com/posts/irsb-data-integrity-fixes-portfolio-expansion/</link><pubDate>Tue, 27 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/irsb-data-integrity-fixes-portfolio-expansion/</guid><description>&lt;p&gt;Eight commits across three repos. Most of the day was bug fixes in the IRSB monorepo — the kind of work that doesn&amp;rsquo;t produce features but produces trust. Every item on today&amp;rsquo;s list existed because the testnet deployment exposed gaps between what the code assumed and what the chain actually returned.&lt;/p&gt;
&lt;h2 id="irsb-removing-the-lies"&gt;IRSB: Removing the Lies&lt;/h2&gt;
&lt;h3 id="demo-data-purge"&gt;Demo Data Purge&lt;/h3&gt;
&lt;p&gt;The IRSB dashboard had hardcoded demo data seeded for screenshots and investor demos. Fake operators, fake bounties, fake resolution events. The problem: some of that demo data leaked into the testnet deployment. A testnet user could see &amp;ldquo;Operator Alpha&amp;rdquo; with a fake track record and think it was real activity.&lt;/p&gt;</description></item><item><title>IRSB Public Site Redesign and git-with-intent v0.5.0 Release</title><link>https://startaitools.com/posts/irsb-public-site-redesign-gwi-v050-release/</link><pubDate>Mon, 26 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/irsb-public-site-redesign-gwi-v050-release/</guid><description>&lt;p&gt;Eighteen commits across four repos. The IRSB dashboard turned into a proper landing page, git-with-intent shipped its most important command yet, and the bounties platform stopped being unusable on phones.&lt;/p&gt;
&lt;h2 id="irsb-dashboard-to-landing-page"&gt;IRSB: Dashboard to Landing Page&lt;/h2&gt;
&lt;p&gt;The old IRSB site was a dashboard. If you landed on it without context, you saw data grids and charts that meant nothing. The redesign flips the model: the public site is a landing page that explains what IRSB does, and the dashboard lives behind authentication.&lt;/p&gt;</description></item><item><title>Landing Page Conversion Optimization and Legal Pages</title><link>https://startaitools.com/posts/landing-page-conversion-optimization-legal-pages/</link><pubDate>Tue, 20 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/landing-page-conversion-optimization-legal-pages/</guid><description>&lt;p&gt;Four commits across two repos. The work split between making the Intent Solutions landing page actually convert visitors and adding the legal foundation that a professional services company needs.&lt;/p&gt;
&lt;h2 id="intent-solutions-landing-projects-showcase"&gt;intent-solutions-landing: Projects Showcase&lt;/h2&gt;
&lt;p&gt;The landing page listed services but didn&amp;rsquo;t show work. The new projects showcase surfaces 17 active projects with consistent metadata:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Project name and one-line description&lt;/li&gt;
&lt;li&gt;Tech stack badges (React, Firebase, Vertex AI, etc.)&lt;/li&gt;
&lt;li&gt;Status indicator (active/maintained/archived)&lt;/li&gt;
&lt;li&gt;Link to live demo or documentation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The showcase renders as a responsive grid &amp;ndash; three columns on desktop, two on tablet, single column on mobile. Each card is intentionally minimal: name, description, stack, status. No screenshots, no long descriptions. The goal is density &amp;ndash; a visitor should scan all 17 projects in under 30 seconds and find the ones relevant to their needs.&lt;/p&gt;</description></item><item><title>Post-Merge Cleanup, Landing Redesign, and Portfolio Theme Overhaul</title><link>https://startaitools.com/posts/post-merge-cleanup-landing-redesign-portfolio-theme/</link><pubDate>Mon, 19 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/post-merge-cleanup-landing-redesign-portfolio-theme/</guid><description>&lt;p&gt;Seven commits across four repos. A cleanup day &amp;ndash; resolving merge debt from the previous week&amp;rsquo;s feature branches, filling content gaps on the landing site, and refreshing the personal site&amp;rsquo;s visual identity. None of these changes are individually significant, but collectively they close out a week of parallel development and get everything back to a clean main branch.&lt;/p&gt;
&lt;p&gt;The pattern of building features in parallel and then spending a day on merge cleanup is becoming standard for multi-repo work. It&amp;rsquo;s not glamorous, but skipping the cleanup creates compounding confusion.&lt;/p&gt;</description></item><item><title>Beads Rollout: 22 Repos, One Governance Pattern</title><link>https://startaitools.com/posts/beads-rollout-twenty-two-repos-org-governance/</link><pubDate>Fri, 19 Dec 2025 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/beads-rollout-twenty-two-repos-org-governance/</guid><description>&lt;p&gt;Seventy-six commits. Twenty-two repos. One day. And most of it was the same two commits repeated eleven times.&lt;/p&gt;
&lt;p&gt;December 19th was a governance rollout day. The beads task tracking system had been running in three repos for a week. It was time to deploy it everywhere.&lt;/p&gt;
&lt;h2 id="the-beads-pattern"&gt;The Beads Pattern&lt;/h2&gt;
&lt;p&gt;Beads (&lt;code&gt;bd&lt;/code&gt;) is the post-compaction recovery system for AI-assisted development. When Claude Code compacts a long conversation, it loses context about what you were working on. Beads persists task state in git so you can recover after compaction.&lt;/p&gt;</description></item></channel></rss>