DefiantMob

DefiantMob is production operator software. The portfolio lists 250 commits. The project tree table lists it as a second production domain, with ledgers and automation: 250 commits and 420k lines.

Member ops, ledgers, training-desk automation, and payouts. The portfolio calls this the substrate agent systems have to touch.

The evidence claim dates live operation to February 2026 through May 2026: DefiantMob production operator software reached live operation with 250 commits, 94 merged pull requests, and automated member management, ledgers, and payout tracking.

The verified findings say MobHub and Defiant Mob reached production. The record covers source, testing, deployment, restoration, and repair. The retrieved Defiant history includes 94 merged pull requests. MobHub includes 24 and a verified Raspberry Pi auto-deployment path. The connected engineering record for the retrieved MobHub, Defiant Mob, and Atlas records includes source, automated checks, commits, pull requests, merges, migrations, deployments, health checks, release repairs, restorations, and recoveries.

In the early 2026 chapter, MobPay, DefiantMob, BeltBrain, and DHG became live desks for access, money movement, ledgers, and planning.

What production taught

On the learning page, the Defiant production lesson is that security controls made the application stronger.

Inherited file permissions, content-security policy, redirects, and a database safety setting interrupted real flows at different points. One release returned to its prior version.

I treated every control as a useful signal. I repaired the permissions, policies, and migration state, then verified the recovery before moving forward.