SF TEAM

Abstract

SF TEAM is a delivery team compressed into agents. Each one holds a senior practitioner's specialty rather than a generic prompt: solution and data architecture, sharing and security models, Apex and asynchronous patterns, LWC, integration design, Health Cloud clinical data, eligibility and enrollment, claims and remittance, release management and CI/CD, packaging and security review, testing and quality. They coordinate the way a good team does. Clear scope, clean handoffs, no heroics. Every one of them works against the platform's real constraints (governor limits, data skew, sharing recalculation, deployment windows) instead of a whiteboard version of Salesforce.

Provenance

Came out of fourteen years of Salesforce delivery across Sales, Service, Health, Experience, and Data Cloud, seventeen certifications, and the platform underneath all of it: Apex, LWC, Flow, integration, packaging, and the patterns that keep an enterprise org standing after the consultants leave.

Declassified

The distinction that matters is architecture, not syntax. Anyone can ship Apex. What survives is a data model that scales past the demo, a sharing model that survives an audit, and an integration layer that outlives the org that commissioned it. So the agents are scoped to that: each one's authority is bounded to its specialty and checked against platform rules before it can recommend anything, and org access runs behind a deny-by-default guard so client environments can't be touched by accident. How they compose, how they escalate, and the delivery record behind them stay private.

Also in FORGE

• AARIA The orchestrator. Plan first, route always.
• SYNARK The flight panel. What the factory is actually doing.
• JUDGE PANEL Removing myself as the bottleneck, without removing the audit.