[Onboarding Tracker] SimSwapAgeBands or SimSwapAgeTiers

[albertoramosmonagas]

API Repository Information

• API Repository Name: SimSwapAgeBands or SimSwapAgeTier (name TBC)
• Sub Project (or "Independent"): Number Insights
• Mailing List: sp-number-insights@lists.camaraproject.org
• Repository: TBC
• Wiki Page: TBC
• API Owner: @shilpa-padgaonkar, @KeldaAnders
• API Proposal: N/A
• Original Approval Issue: Add a third SIM Swap API endpoint to return SIM-Swap age band SimSwap#260

See more context on the last TSC meeting https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/1131708461/2026-09-17+TSC+Minutes

⚠️ Progress to the next gate only after completing all items in the current one.

---

GATE 0 – Codeowner Validation (must be completed before repository creation)

• Code owner(s) nominated and confirmed by API Backlog WG
• LF account active and Confluence access granted
• Subscribed to all@lists.camaraproject.org
• GitHub account active with notifications enabled
• Invitation to CAMARA GitHub Organization accepted
• EasyCLA validation successfully completed via test PR in camaraproject/EasyCLA

Once all items are complete, repository creation can proceed.

---

GATE 1 – Repository Onboarding (infrastructure established)

• Update APIBacklog.md with status: Onboarding
• Request wiki page and mailing list (email support@camaraproject.org, specify details)
• Confirm mailing list creation (only if Independent Sandbox) (LF Admin)
• Confirm wiki page creation (LF Admin)
• Repository created (LF Admin via automation)
• Add repository link to the API wiki page (LF Admin)
• Update README.md in the repository with API details (API owner)
• Update APIBacklog.md with status: Onboarded
• (Optional) Nominate initial Maintainers (API owner)
• (Optional) Submit PR to update MAINTAINERS.md and CODEOWNERS

---

GATE 2 – Initial Codeowner Tasks (first activities within the repository)

• Confirm that the CODEOWNERS file is correct and up to date
• Update the Scope section within README.md to reflect the agreed API purpose
• Create the first GitHub issues (e.g. for drafting the initial API specification or defining next milestones)
• Announce the start of development and share planned next steps via the API mailing list

Additional for new Independent Sandbox repositories:

• Agree on a regular meeting schedule with your team (via mailing list or initial call)
• Request a meeting link from support@camaraproject.org to be added to your recurring calendar invite
• Review and update the repository wiki page accordingly

---

Notifications:
CC: @camaraproject/admins @camaraproject/api-backlog_maintainers @camaraproject/marketing_maintainers

[tanjadegroot]

From what I have read in the API description, "SimSwapTimeFrame" would be a perfectly understandable title :-)

"SimSwapTimeslot" is another option (but sounds more evenly distributed to me then timeframe)

does require some rework of the text and schema names.