New codes

[saturnflyer]

AFSC Code Discrepancies - Needs Investigation

The following codes from our application could not be verified against official sources or have format issues. These need further investigation before adding to the gem.

Codes Not Found or Wrong Format

App Code	Issue	Notes
5C0X1	May be Space Force, not Air Force	Current AF Command Post is 1C3X1. Code 5C0X1 appears in Space Force (USSF) as Cyber Operations.
5I0X1	Inspector General is in 8I series	IG codes are SDIs: 8I000 (Superintendent), 8I100 (Inspections), 8I200 (Complaints) - all already in gem
5I2X1	Same as above	8I200 (Complaints & resolution coordinator) already exists
5S0X1	May be Space Force	Appears to be USSF Space Systems Operations
8G0X1	Invalid RI format	RI codes use digits, not "X". Correct format is 8G000 (Premier Honor Guard) - already exists
8F100	Not found in official sources	Only 8F000 (First Sergeant) exists in SPECAT documentation

Codes That Already Exist (Different Numbers)

App Code	Existing Code	Name	Action Needed
8R100	8R200	Second-tier recruiter	Already in gem - verify app is using correct code
8T300	8T200	Development advisor	Already in gem - verify app is using correct code
9S000	9S100	Scientific applications specialist	Already in gem - verify app is using correct code

Sources Consulted

• Wikipedia AFSC Article
• DAFECD April 2025
• SPECAT Guide
• Forever Wingman AFSC Database
• Official CFETPs on static.e-publishing.af.mil

Recommended Actions

1. Check application database - Verify the exact codes being used in production
2. Space Force consideration - If supporting USSF codes, the 5C, 5I, 5S series should go in a separate Space Force file
3. Code mapping - Consider if app has legacy codes that need mapping to current AFSCs

[chriskottom]

@saturnflyer I'm in the process of rebuilding the above referenced PR for Skedify to use this gem. Once done, I can have a look at updating the gem to open up namespaces for other types of specialty codes.

• USSF (Space Force)
• MOS (Army)
• MOS (USMC)
• NEC (Navy)
• Rating (USCG)

Assumptions:

• Each type managed independent of the others.
• Codes might be repeated across different specialty code schemes.
• Not enough to use just the specialty code name as the namespace as even these might be reused (ex: MOS used by both Army and Marines).