Developer Activity Comparison: jordotech vs jdkealy — Faction-V (Feb 16 - Mar 2, 2026)

developer-activity-report.md

Developer Activity Comparison — Faction-V Org

Period: Last 2 weeks (2026-02-16 to 2026-03-02) Organization: Faction-V Users compared: jordotech vs jdkealy

---

High-Level Metrics

Metric	jordotech	jdkealy	Ratio
Total commits	172	197	1 : 1.15
PRs created	24	18	1.3 : 1
Active repos	7	12	1 : 1.7
Active commit days	13 / 14	13 / 14	1 : 1
Lines added	~22,083	~34,656	1 : 1.6
Lines deleted	~5,210	~6,370	1 : 1.2

---

Repo Breadth — Commits by Repository

#	Repository	jordotech	jdkealy
1	gofigure_terraform	73	51
2	platform-api	50	34
3	mcp-servers-runner	2	45
4	agentic-backend	13	24
5	platform-frontend	19	4
6	qdrant-svc	10	—
7	local-goodies	—	13
8	workflow-builder-agent	—	11
9	chatagent	—	7
10	clj-pg-wrapper	5	4
11	composio-service	—	2
12	demo-proxy-app	—	2
13	politico-vue-demo	—	1

5 shared repos (gofigure_terraform, platform-api, agentic-backend, platform-frontend, clj-pg-wrapper) plus 2 jordotech-only and 6 jdkealy-only repos.

---

PR Involvement by Repo

Repository	jordotech PRs	jdkealy PRs
gofigure_terraform	9	3
platform-api	5	3
agentic-backend	4	2
platform-frontend	3	1
mcp-servers-runner	1	2
workflow-builder-agent	—	2
demo-proxy-app	—	2
clj-pg-wrapper	1	—
capai-claude-marketplace	1	—
chatagent	—	1
composio-service	—	1
local-goodies	—	1

---

Lines Changed by Repository

Repository	jordotech (+/−)	jdkealy (+/−)
gofigure_terraform	11,453+ / 2,403−	7,961+ / 625−
platform-api	4,133+ / 754−	6,208+ / 370−
platform-frontend	4,904+ / 1,013−	23+ / 33−
mcp-servers-runner	531+ / 862−	7,135+ / 953−
agentic-backend	296+ / 37−	5,775+ / 3,632−
qdrant-svc	302+ / 47−	—
clj-pg-wrapper	464+ / 94−	357+ / 331−
workflow-builder-agent	—	1,968+ / 287−
local-goodies	—	5,024+ / 122−
chatagent	—	97+ / 15−
composio-service	—	90+ / 0−
demo-proxy-app	—	14+ / 2−

---

Work Focus Areas

Domain	jordotech	jdkealy
Infrastructure / Terraform	Heavy (73 commits) — IRSA, Auth0 prod, XKS encryption, ECR, Azure AD	Active (51 commits) — staging deploys, image tags, health probes, Sentry wiring
Platform API	Heavy (50 commits) — SSO/Auth0, org management, releases, CHANGELOG	Heavy (34 commits) — chat agent routes, JWT minting, token relay, user auth
MCP Servers	Light (2 commits) — DNS notation, AI context	Heavy (45 commits) — composio server, workflow-builder server, auth consolidation, Sentry
Agentic Backend	Moderate (13 commits) — S3 proxy, SSO bearer auth	Active (24 commits) — Temporal workflows, Composio MCP injection, observability
Platform Frontend	Active (19 commits) — Auth0 SPA SDK, SSO admin UI, Vercel deploys	Light (4 commits) — feature flag removal, composio tool group, chat-agent fixes
Qdrant Service	Active (10 commits) — multi-WordPress, auth0 tokens	—
Chat Agent Infra	—	Heavy (chatagent + workflow-builder + local-goodies = 31 commits) — LibreChat deployment, MCP sidecar, Temporal design docs
Composio Integration	—	Active — composio-service CI, MCP provisioning, OAuth flow
Demo / Client	—	Light (demo-proxy-app, politico-vue-demo)

---

Key Themes — Last 2 Weeks

jordotech

• COM-18 SSO/Auth0 push: End-to-end SSO implementation spanning Terraform (Auth0 prod org, Azure AD enterprise connection), platform-api (SSO schemas, token handling), platform-frontend (Auth0 SPA SDK, SSO admin UI), clj-pg-wrapper (user ensure endpoint), and agentic-backend (Bearer auth for SSO users)
• Infrastructure hardening: XKS encryption with Azure cert auth, ECR replication to eu-west-1, IRSA for S3 presigned URLs
• Release management: Multiple version bumps and CHANGELOG updates across platform-api, qdrant-svc, agentic-backend
• Qdrant multi-WordPress: Per-site exclusion rules and migration tooling

jdkealy

• ENG-109/391/419 Chat Agent pipeline: Full-stack chat agent infrastructure — LibreChat (chatagent) K8s deployment, MCP servers runner with composio + workflow-builder servers, platform-api JWT minting and token relay, staging deployment orchestration
• MCP Servers heavy build-out: 45 commits — composio server, workflow-builder server, auth consolidation, conversation-based token relay, Sentry flow tagging
• Temporal workflow design: ENG-419 design docs and implementation plan for chat workflow execution, initial Temporal infrastructure in agentic-backend
• Composio integration: End-to-end — composio-service CI, per-user MCP provisioning, OAuth flow, DB registration
• Staging ops: Image tag management, health probes, test user creation, local-goodies orchestration

---

Cadence & Consistency

• jordotech committed on 13 of 14 days — consistent daily output across 7 repos.
• jdkealy committed on 13 of 14 days — consistent daily output across 12 repos.
• Both developers maintained near-identical cadence with essentially zero idle days.

---

Key Takeaways

1. Volume is comparable: Unlike the 14x gap seen in the 30-day jordotech vs aksubr comparison, jordotech and jdkealy are nearly matched on commit volume (172 vs 197) and active days (13 vs 13).
2. Different breadth profiles: jordotech focuses deeply on fewer repos (7), while jdkealy touches nearly twice as many (12) — driven by the chat agent feature spanning many services.
3. Complementary domains: jordotech owns SSO/Auth0 and infrastructure hardening; jdkealy owns the chat agent pipeline and MCP/Composio integration. Minimal overlap in feature work despite shared repos.
4. Shared repos, different concerns: In platform-api, jordotech works on SSO/org management while jdkealy works on chat agent routes. In gofigure_terraform, jordotech handles Auth0/XKS infra while jdkealy manages staging image deployments.
5. Lines of code: jdkealy has higher LOC (34.6k+ vs 22k+), largely driven by greenfield MCP server and agentic-backend work. jordotech's LOC is concentrated in Terraform and frontend SSO.