Review Project/Provision terminology for modern identity alignment

[JayVDZ]

Summary

Review and potentially rename the Project and Provision terms used throughout JIM to ensure alignment with modern identity management terminology.

Background

JIM currently uses these terms with the following meanings:

• Project — creating a Metaverse Object (MVO) from a Connected System Object (CSO) (i.e., establishing a new identity in the metaverse based on an external source)
• Provision — creating a Connected System Object (CSO) from a Metaverse Object (MVO) (i.e., pushing an identity out to a connected system)

These terms originate from legacy ILM tools and may cause confusion in the modern identity landscape. For example, Projection is now commonly used in the industry to describe pushing an identity to a connected system — which conflicts with how JIM uses the similar term "Project" (which means the opposite direction).

Goals

• Audit all uses of "Project" and "Provision" in code, UI, documentation, and configuration
• Research current industry-standard terminology for these operations
• Evaluate whether renaming improves clarity for new users and aligns with modern expectations
• If renaming is warranted, plan and execute the migration (code, database, UI, docs)

Considerations

• Consistency with terminology used in SCIM, Azure AD / Entra ID provisioning, other modern identity platforms, industry standards (e.g. from the OpenID Foundation), and emerging patterns in the identity space
• Impact on documentation, user guides, and admin UI

Scope

This is a terminology review — the outcome may be "keep as-is" if the current terms are deemed clear enough, or a rename plan if modern alternatives are better suited.