<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/governance/</link><description>Recent content in Governance 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/governance/index.xml" rel="self" type="application/rss+xml"/><item><title>git-with-intent Vitest 4 Migration Pain and IRSB Governance with 104 Moloch Tests</title><link>https://startaitools.com/posts/gwi-vitest4-migration-pain-irsb-governance-moloch-tests/</link><pubDate>Thu, 12 Feb 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/gwi-vitest4-migration-pain-irsb-governance-moloch-tests/</guid><description>&lt;p&gt;Eighteen commits across three repos. git-with-intent fought through a Vitest 4 migration that broke CI seven different ways. IRSB shipped v1.4.0 with governance contracts and a 104-test Moloch DAO suite. Perception got a dashboard fix.&lt;/p&gt;
&lt;h2 id="git-with-intent-vitest-4-migration"&gt;git-with-intent: Vitest 4 Migration&lt;/h2&gt;
&lt;p&gt;The v0.8.0 prep for git-with-intent included upgrading from Vitest 3.x to Vitest 4. The test suite passed locally. CI failed. Then it failed six more times in six different ways.&lt;/p&gt;
&lt;h3 id="mock-pattern-changes"&gt;Mock Pattern Changes&lt;/h3&gt;
&lt;p&gt;Vitest 4 changed how &lt;code&gt;vi.mock()&lt;/code&gt; interacts with module resolution. In Vitest 3, mock declarations were hoisted above imports automatically. Vitest 4 introduced &lt;code&gt;vi.hoisted()&lt;/code&gt; as an explicit mechanism and stopped auto-hoisting in several edge cases.&lt;/p&gt;</description></item><item><title>IRSB Security Audit Fixes, git-with-intent v0.6.0, and GitHub Profile Overhaul</title><link>https://startaitools.com/posts/irsb-security-audit-fixes-gwi-v060-github-profile-overhaul/</link><pubDate>Thu, 29 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/irsb-security-audit-fixes-gwi-v060-github-profile-overhaul/</guid><description>&lt;p&gt;Forty commits across five repos. The biggest day of January by commit count, and most of it was security work that made the IRSB protocol auditable.&lt;/p&gt;
&lt;h2 id="irsb-security-fixes-16-commits"&gt;IRSB Security Fixes (16 Commits)&lt;/h2&gt;
&lt;p&gt;Yesterday built the audit scaffold. Today started closing the findings.&lt;/p&gt;
&lt;h3 id="high-severity-fixes"&gt;HIGH Severity Fixes&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;SEC-001: Reentrancy in bounty settlement.&lt;/strong&gt; The &lt;code&gt;settleBounty&lt;/code&gt; function transferred tokens before updating the bounty status. Classic reentrancy vector — a malicious resolver contract could re-enter &lt;code&gt;settleBounty&lt;/code&gt; during the token transfer callback and claim the bounty twice.&lt;/p&gt;</description></item><item><title>Nixtla BSL License Pivot</title><link>https://startaitools.com/posts/nixtla-bsl-license-pivot/</link><pubDate>Tue, 06 Jan 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/nixtla-bsl-license-pivot/</guid><description>&lt;p&gt;Two commits. One governance decision. The thinnest day of the month so far.&lt;/p&gt;
&lt;h2 id="why-bsl-11"&gt;Why BSL 1.1&lt;/h2&gt;
&lt;p&gt;Nixtla&amp;rsquo;s baseline lab has been MIT-licensed since inception. MIT is the default choice for developer tools — maximum adoption, zero friction, everyone can use it however they want.&lt;/p&gt;
&lt;p&gt;The problem with MIT for a commercial product: competitors can take your code, wrap a paid service around it, and sell it back to the same market you&amp;rsquo;re trying to serve. You built it. They profit from it. Your only competitive advantage is moving faster, which is not a sustainable moat when someone with a bigger team can fork and iterate.&lt;/p&gt;</description></item><item><title>GWI RBAC Governance and Hustle CI Stabilization</title><link>https://startaitools.com/posts/gwi-rbac-governance-hustle-ci-stabilization/</link><pubDate>Fri, 26 Dec 2025 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/gwi-rbac-governance-hustle-ci-stabilization/</guid><description>&lt;p&gt;December 26th. Three commits on git-with-intent, three on hustle. The GWI work was about governance. The hustle work was about not breaking things.&lt;/p&gt;
&lt;h2 id="git-with-intent-rbac-and-governance"&gt;git-with-intent: RBAC and Governance&lt;/h2&gt;
&lt;p&gt;The RBAC system adds the multi-tenant access layer that git-with-intent needed before any real organization could use it. Three commits covering the full governance surface.&lt;/p&gt;
&lt;h3 id="tenant-management"&gt;Tenant Management&lt;/h3&gt;
&lt;p&gt;Each tenant gets an isolated namespace with its own configuration, agent definitions, and run history.&lt;/p&gt;
&lt;p&gt;Tenant creation provisions the namespace, sets default quotas, and generates an API key scoped to that tenant. Tenant deletion is soft — the namespace gets marked inactive, data is retained for the audit retention period, and the API key is revoked immediately.&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>