Context
omkit.provider (ProviderBase, ProviderRegistry) and omkit.sanitize (sanitize_llm_output, sanitize_llm_response, extract_json) are LLM-specific concerns. LLM abstraction belongs in cortex (within the omur platform), not in the multi-tenant scaffolding kit.
Keeping them in omkit:
- bloats the surface area for services that don't talk to LLMs
- forces version-locking the LLM abstraction to omkit releases
- competes with LiteLLM / LangChain / Vercel AI SDK on a fight omkit shouldn't pick
Plan
- Inventory all internal consumers of
omkit.provider and omkit.sanitize
- Land the equivalent surface in cortex (LLM provider registry + LLM-output sanitizers)
- Mark
omkit.provider + omkit.sanitize as deprecated shims that re-export from cortex (one release)
- Remove from omkit in the following major
- Update
omkit.security facade — strip sanitize re-exports, keep log_security_event
Acceptance
Related
- omurlabs/omkit-go: paired removal of
provider package
Context
omkit.provider(ProviderBase,ProviderRegistry) andomkit.sanitize(sanitize_llm_output,sanitize_llm_response,extract_json) are LLM-specific concerns. LLM abstraction belongs in cortex (within the omur platform), not in the multi-tenant scaffolding kit.Keeping them in omkit:
Plan
omkit.providerandomkit.sanitizeomkit.provider+omkit.sanitizeas deprecated shims that re-export from cortex (one release)omkit.securityfacade — strip sanitize re-exports, keeplog_security_eventAcceptance
provider+ LLM-output sanitizersDeprecationWarningRelated
providerpackage