jordotech

RFC: Git-Tracked Claude Skill Management

Team: Agentic Backend Author: Engineering Date: 2026-03-07 Status: Implementation planned — [plan at docs/plans/2026-03-07-cli-skill-management.md]

---

Problem

jordotech

Multi-Regional Deployment: EY SSO Region Redirect

What Are We Building?

EY has 3 regional deployments, each with its own frontend and backend:

Region	Frontend	Backend
US (us-east-2)	platform-ey-us-east-2.capitol.ai	US backend
EU (eu-west-1)	platform-ey-eu-west-1.capitol.ai	EU backend

jordotech

Agentic-Backend PR Comparison: #363 vs #362

PR #363 (sso_user_id_updates by CapitolCoder) — 527 additions, 8 deletions, 3 files PR #362 (feature/COM-18-ad-phase-1 by jordotech) — 8 additions, 1 deletion, 1 file

Both PRs add Authorization: Bearer header support to get_current_user() so SSO users can authenticate with agentic-backend.

Diff Comparison

| Aspect | PR #363 | PR #362 (ours) |

jordotech

Platform-API PR Comparison: #365 vs #363

PR #365 (sso_user_id_updates by CapitolCoder) — 3,143 additions, 80 deletions, 16 files PR #363 (feature/COM-18-ad-phase-1 by jordotech) — 3,124 additions, 264 deletions, 22 files

Both PRs target the same goal: make platform-api Auth0-aware so SSO users get proper UUIDs instead of Auth0 sub strings.

Scope Comparison

| Aspect | PR #365 | PR #363 |

jordotech

SSO Authentication Support for agentic-backend

Problem

As part of the Auth0 tenant migration (COM-18), we identified that SSO users cannot authenticate with agentic-backend. This is a pre-existing gap — not a regression from the migration — but it blocks SSO rollout for EY and future enterprise clients.

Root Cause

The frontend sends tokens differently depending on auth method:

jordotech

EY Agentic-Backend: Q4 2025 Anthropic Inference Cost Estimate

Prepared: 2026-02-23 Period: October 1 - December 31, 2025 Data sources:

• platform.claude.com cost exports (3 CSV files, full months)
• Langfuse project cap-llm token usage (Nov 22 - Dec 31, 2025)

---

jordotech

EY SSO Integration: Technical Update

Overview

This document describes an enterprise SSO implementation for EY using Auth0 and Azure Entra ID. Phase 1 is complete and validated end-to-end on staging as of February 23, 2026.

Architecture

Authentication Flow

• Email-first discovery: Users enter email, backend checks org memberships AND email domain for SSO configuration
• Dual-path discovery: Both membership-based and domain-based checks always run, results are merged with deduplication

jordotech

Feature Flags Architecture — Response

Good doc, Masha. The direction is right. Here's my take with some additional considerations.

Where I Agree

1. Registry as source of truth for what flags exist — yes, absolutely
2. Validate flag keys on write — reject keys not in registry. This prevents drift
3. Merge on read — registry defaults + per-org overrides. This is the core change
4. Show ALL registry flags in the admin UI — this is actually the highest-impact change

jordotech

PR #357 Assessment: Feature Flag Registry Improvements

PR: https://github.com/Faction-V/platform-api/pull/357 Author: masha-maltseva (via Cursor) Branch: feat/BE-762-feature-flag-registry-improvements → feature/BE-762-be-ff-enforce Files changed: 1 (src/feature_flag_registry.py, +13 / -214)

---

Summary of Changes

jordotech

{
  "Ansi 7 Color (Light)" : {
    "Red Component" : 0.7810397744178772,
    "Color Space" : "sRGB",
    "Blue Component" : 0.78104829788208008,
    "Alpha Component" : 1,
    "Green Component" : 0.78105825185775757
  },
  "Ansi 15 Color (Light)" : {
    "Red Component" : 0.99999600648880005,