Eduardo González

Choose a style

Same content in ten visual styles. Every one passes automated WCAG 2.2 AA checks.

Default
Quiet
Bold
Interface

Work SITIMM

Case study · May 2025 to now

Running a union's platform with a team of AI agents.

SITIMM is a Mexican union of 70,000 members in 170 companies. Since May 2025 I've led its website, mobile app, admin panel and API as the only human engineer. I direct parallel AI agent sessions and hold them to the same gates I'd ask of a senior team.

My role
Lead engineer: architecture, scope, review, every merge
Team
Me, plus 5–6 parallel AI sessions; a second model reviews
Surfaces
Web, iOS and Android app, admin panel, API, shared types
Stack
FastAPI, PostgreSQL, Next.js, React, React Native

Screens

SITIMM's public website: a red header with nine sections, the union's name, a news carousel and counters for 70,000 members, 50 years and 170 companies.
The public website, sitimm.org. App and panel screens follow, with private data and sensitive panel areas left out.
  • The app's home screen greeting a member by name, with a news story below.
  • SitimmVito, the app's AI assistant, answering a question about member discounts.
  • An event ticket with a QR code, ready to scan at the door.
Scenes from the app's launch video. The member, Daniela, is a test account.
The full tour, two minutes, made for the union's leadership. The on-screen text is in Spanish. There is no sound, so the transcript below covers everything shown.
Transcript in English
  1. 0:00, opening. “I'm Daniela. I'm a SITIMM member.” A phone shows the app's splash screen with the union's seal.
  2. 0:04, home. “Everything important from the union, on the first screen.” The app greets Daniela by name, shows news and magazines up front, and searches all of SITIMM for “IMSS”.
  3. 0:15, magazines. “Keep up with union news in our weekly magazine, SITIMMFORMA, complete on your phone.” She opens issue 45 in the built-in reader and jumps through its index.
  4. 0:29, consultations. “Your union advisor, one message away: IMSS, INFONAVIT, AFORE or FONACOT, followed through until your case is closed.” She asks about IMSS and an advisor replies in a live chat.
  5. 0:53, SitimmVito AI. “Answers right away, whenever you need them, from the union's own information.” She taps a suggested question and the assistant answers.
  6. 1:01, day and night. “I use it day and night.” The app switches to dark mode.
  7. 1:06, announcements. “The union's official voice, the moment it's published.” General notices and the ones for her company.
  8. 1:15, discounts. “Member benefits: 114 businesses with discounts in 6 cities.” She filters by city, opens a business in Celaya and sees its hours and a map.
  9. 1:31, events. “Courses and workshops: sign up in a few steps and get in with your digital ticket.” She signs up and gets a ticket with a QR code.
  10. 1:50, in your language. “Available in 8 languages.” The same screen in Spanish, English, Chinese and Japanese.
  11. 2:00, close. “Yo Soy SITIMM. Sindicalismo de verdad.” (“I am SITIMM. Real unionism.”) QR codes for the App Store and Google Play.

The problem

Members needed news, events, benefits and their union services on their phones. The union had a legacy backend, no product team, and one engineer: me.

The constraints were real. One 16 GB laptop shared by every agent session. No paid CI: GitHub Actions has been off since September 2026, so every quality gate runs locally. And no room for a bad release on an app that 70,000 people can install.

What I owned, what the agents did

Me

  • Architecture, contracts between the five repos, and scope
  • Writing and ordering the tickets
  • Reviewing and merging every pull request
  • Releases, and QA on real phones
  • The rules every agent follows, and changing them after each incident

The agents

  • Write code and tests, each in its own git worktree
  • Run the local gate before every push
  • Review each other: a second model checks the first
  • Draft docs and handoffs between sessions
  • Never merge or deploy without my explicit OK

How a change ships

  1. TicketScoped in Jira, one at a time per session.
  2. WorktreeThe agent works in its own checkout, never the shared one.
  3. Code and testsTests come with the change.
  4. Local gateLint, types, tests, coverage of touched lines. One heavy job at a time on the machine.
  5. Cross-reviewA second model reviews and says what it actually read.
  6. My review and mergeNothing reaches main without me.
  7. DeployAPI by continuous deployment; web and panel on Netlify; app through the stores.

Guardrails, and the incident behind each one

Every rule here exists because something broke. That's the part of working with agents nobody shows.

Rules, the incident that caused each one, and how it's enforced
RuleWhat happenedHow it's enforced
One worktree per agentJul 2026: two sessions shared one checkout. One switched branches under the other's build and mixed two tickets on one branch.Writing agents get their own git worktree. The shared checkout is read-only.
Measure memory before heavy workSep and Nov 2026: the laptop rebooted twice under parallel pushes, test suites and a video render. In-flight work was lost.Under 40 % free memory, stop and ask. One heavy job at a time through a machine-wide lock.
No lock inside a lockNov 2026: a push run under the lock waited on its own pre-push check and held the machine for 8 hours.An environment flag tells nested steps the lock is already held.
Real installs in worktreesNov 2026: three pushes went out with no hooks because dependencies were symlinked.Install in each worktree and check the hooks exist before the first commit.
A review's GO has a scopeNov 2026: a reviewer approved after opening 25 of 106 files.Reviews report what they read; counts come before claims.
A fix needs a test that catches the bugFixes passed tests that would also pass without them.Reintroduce the bug and watch a test fail before calling it fixed.
Never cite a ticket you haven't checked22 references to Jira tickets that didn't exist.Ticket keys are verified against Jira.

Numbers

Figures for the SITIMM platform, with how each was measured
MetricValueHow it was measured
Commits since May 20258,790Git history of the five repos
Co-authored by an AI agent7,797 (89 %)Co-author lines in each commit
Merged pull requests2,526GitHub
Merged pull requests, last 7 days156GitHub, 13–20 Nov 2026
Tickets referenced in commits1,591Jira keys in the git history
Test files~3,600Files in the repos
App builds shipped148Release tags, up to version 3.7.0
Languages in the app8The app's language menu
Businesses with member discounts114The app's discount directory, Nov 2026
AI usage, one week$3,251List API price of 610 sessions' tokens; the work runs on a flat plan
AI usage per merged pull request≈ $21That week's usage divided by its merged pull requests, all work included

What I'd do differently

  • Write the guardrails before the first incident, not after. Most of the table above was learned the hard way.
  • Measure cost per task from the first week. I only started in November 2026.
  • Keep one CI runner off the laptop. Local gates work, but one machine is a single point of failure.

Want the details?

I'm happy to walk through any of this, including the parts that went wrong.