# ThumbGate for platform teams

Platform teams are the first internal buyer when AI coding agents move from experimentation to shared use. The problem is not model quality in the abstract. The problem is rollout control: different repos, different agents, different operators, and the same mistakes showing up across all of them.

## What the platform team actually needs

### One control point

Claude Code, Codex, Cursor, Gemini CLI, Amp, and CI all need the same enforcement story, not six separate governance projects.

### Shared lessons

When one repo learns not to force-push, skip tests, or run a risky migration, that lesson should become reusable policy.

### Proof before scale

Platform teams need evidence: which gate fired, what it blocked, and where review churn is actually dropping.

## ThumbGate rollout pattern

1. Start with one repo, one owner, and one repeated AI failure.
2. Install the free CLI wedge and capture real thumbs-up/down feedback.
3. Promote the repeated failure into a Pre-Action Check.
4. Use the team rollout path when shared lessons, dashboard visibility, and approval boundaries become the blocker.

## Why platform teams buy

- Lower review churn across agent-written changes
- Shared enforcement memory instead of tribal knowledge
- A path from local proof to managed rollout
- One governance story across multiple agent runtimes

ThumbGate is not another platform-team committee project. It starts as a local CLI wedge, proves value on one live failure mode, and only then expands into a broader rollout.

Start the workflow hardening sprint Compare against orchestration suites

## The named role inside the platform team

When the platform team is the home for AI coding agent rollout, the Agent Manager is the DRI — Anthropic's name for the hybrid PM/engineer who owns CLAUDE.md, the plugin marketplace, permissions policy, and which skills ship. ThumbGate is the pre-action enforcement runtime that role uses underneath all four.