# SDK Portfolio

> Decide a public API's language-SDK portfolio - which languages get official SDKs, built how, tiered how, versioned
> how, and retired on what evidence. List every language with its traffic share, deal requests and today's status;
> the browser reads each against a self-set add-threshold and the integrating vertical's language map, gives it one
> action, ranks the build model, checks the three versioning policies stay apart and holds every end-of-life to the
> exclusive-usage evidence. Metered runs write the portfolio strategy, and the end-of-life cases. Built on the
> SkillSafe skill @samber/sdk-portfolio-strategy, from samber/developer-platform-skills (MIT), by Samuel Berthe.

https://sdk-portfolio.skillsafe.ai/

## What is free
- The language order: each language's traffic share and named deal requests against the add-threshold, the vertical's map (fintech front-loads Java, C#, Ruby, Go; AI front-loads Python and TypeScript), and team fluency - with no telemetry, the vertical's top three stand in.
- One action per language: add, keep, promote (a community SDK past the threshold, through the gate), community (listed with a non-guarantee), self-service (spec-driven), evidence (an official SDK below the threshold with no exclusive-usage count), retire (no account depends on it alone).
- The build model ranked: a commercial generator by default, the free OpenAPI Generator when procurement or self-hosting rules a vendor out, a handwritten flagship when the API is the product and one language carries half the traffic; spec state, exit plan.
- The gates: the surface decision, telemetry coverage, the spec as the source of truth, three versioning policies kept apart, no EOL without evidence; plus a portfolio table, a languages CSV, the checks (.csv) and everything (.json).

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (strategy or sunset), `platform`, `languages`, `carry` (sunset only: the strategy's decisions) and `facts`.
- `strategy` replies with `summary`, `shape`, `languages` (each with the page's action), `build`, `tiers`, `versioning`, `threshold`, `community_policy` and `caveats`.
- `sunset` replies with `summary`, `cases` (each end-of-life case with its evidence, successor, steps and windows) and `caveats`.
The page holds every reply to its own facts: the shape, every language's action in order, the ranked build model with an exit plan, two tiers and a gate, SemVer SDKs never tied to API versions, a self-set threshold; nothing announced before the evidence, and retirements run final release, announcement, archive inside 6 to 24 months.

## Links
- API tutorial: https://sdk-portfolio.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/sdk-portfolio-strategy