Intentvision on Start AI Tools - Presented by Intent Solutions

GWI IDP Specification Suite, Bounties EV Scoring, and IRSB Resilience Patterns

Tue, 03 Feb 2026 10:00:00 -0600

Fifty-five commits across six repos. The highest single-day commit count of the month, though the commit count overstates the architectural significance. Most of these were specification documents, not code.

git-with-intent: The IDP Specification Sprint

Twenty-nine commits, and the bulk of them were specification documents for an Internal Developer Platform.

The IDP spec suite covers the standards a platform team needs to evaluate and enforce:

RAG pipeline specifications (chunking strategy, embedding model requirements, retrieval evaluation thresholds)
DORA metrics tracking (deployment frequency, lead time, change failure rate, MTTR)
SOC2 compliance requirements (access control logging, data retention policies, incident response)
SAST integration standards (which tools, which severity levels block merge, false positive handling)
Feature flag governance (TTL requirements, flag cleanup automation, percentage rollout gates)
Incident response procedures (severity classification, escalation paths, post-mortem templates)

Twenty-plus documents in total, each following the same template — purpose, scope, requirements, validation criteria, and integration points with git-with-intent’s analysis engine.

IntentVision Phases 8-14 and Personal Brand Repositioning

Sun, 01 Feb 2026 10:00:00 -0600

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.

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.

IntentVision: Phases 8 Through 14

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.

x402 Quickstart, GWI ARV Fixes, and the IntentVision DevOps Playbook

Sat, 31 Jan 2026 10:00:00 -0600

Twenty-two commits. Five repos. The kind of day where no single project gets a dramatic breakthrough but every project gets meaningfully better. IRSB led with thirteen commits of documentation and CI stabilization. git-with-intent got three targeted fixes. IntentVision got a real execution plan.

x402: The 30-Minute Quickstart

The x402 payment protocol shipped yesterday. Today it got a quickstart guide designed to take a developer from zero to a working payment flow in 30 minutes.

Architecture Reboot: git-with-intent Connector Framework and GA Hardening

Tue, 16 Dec 2025 10:00:00 -0600

One day after bootstrapping git-with-intent to v0.2.0, I threw most of it away.

Not literally. The core intent classification engine survived. But the architecture around it — the CLI structure, the plugin system, the way connectors talked to the core — all of it got rebooted. Forty-one commits in a single day, and the result was a product that looked nothing like what shipped 24 hours earlier.

Why Reboot After One Day

The v0.2.0 architecture had a fundamental problem: every integration was hardcoded. Want to analyze GitHub PRs? Write a GitHub module. Want to analyze GitLab MRs? Write a GitLab module. Want to read from Bitbucket? Another module. Each one duplicated the same patterns — authentication, pagination, rate limiting, error handling — with slight variations.

Two Products Bootstrapped from Zero to Release in One Day

Mon, 15 Dec 2025 10:00:00 -0600

December 15th was a bootstrapping day. Two products went from empty directories to tagged releases. Not prototypes. Not “hello world” scaffolds. Actual versioned releases with real functionality.

git-with-intent: 11 Commits Through 7 Phases

git-with-intent is the AI-assisted git workflow tool. On December 15th it went from concept to v0.2.0 across 11 commits.

The phases tell the story:

Phase 1: Core commit analysis engine. Parse git history, extract semantic meaning from diffs.
Phase 2: Intent classification. Map commits to intent categories (feature, fix, refactor, chore).
Phase 3: Workflow templates. Predefined patterns for common git workflows.
Phase 4: CLI scaffolding. Commander.js setup with subcommands for each operation.
Phase 5: Configuration system. User-level and repo-level config with sensible defaults.
Phase 6: Output formatting. Structured output for terminal, JSON, and markdown.
Phase 7: Release prep. Version bump, changelog generation, LICENSE, README.

Each phase was a focused commit or two. No phase depended on a phase that hadn’t been built yet. The ordering was deliberate — you can’t build intent classification without a commit analysis engine, and you can’t build a CLI without knowing what operations you’re exposing.