Eve library

Sovereign Replacement Availability Certification

Guide

Revision 1

On this page

Phase 52 completion criterion: Sovereign replacements available for phased migration of the technology stack.

This certification is generated from @neith/qa path, manifest, and capability-marker audits. It verifies that Oshun already ships concrete sovereign replacement lanes that teams can migrate toward over time rather than depending exclusively on third-party foundations forever.

Summary#

  • Phased migration readiness: PASS
  • Certified lanes: 5/5
  • Certified replacement surfaces: 27
  • Missing paths: 0
  • Identity mismatches: 0
  • Missing capability markers: 0
  • Runtime foundation surfaces: 4
  • Release and QA surfaces: 4
  • Neith Linux platform surfaces: 7
  • Engine/media replacement surfaces: 8
  • AI local-stack surfaces: 4

Certification Rules#

  • Each migration lane must expose actual in-repo sovereign entrypoints, not just planning docs or empty package shells.
  • Workspace manifests or crate manifests must advertise the expected sovereign package identity for the replacement surface.
  • Source entrypoints must contain capability markers that prove the lane is wired for migration use, such as runtime exports, Linux control-center modules, OpenUSD/interchange tools, or local LLM factories.
  • The certification proves availability for phased migration. It does not claim that every Oshun product has already completed migration.

Certified Replacement Surfaces#

Lane Kind Package Path Detail
engine-media workspace-manifest @bellona/integration libs/bellona/integration/package.json Bellona integration manifest for sovereign migration bridges into Hathor and Isis
engine-media source-entrypoint n/a libs/bellona/integration/src/index.ts Bellona integration entrypoint for lore compilation and asset conversion bridges
engine-media workspace-manifest @bellona/interchange libs/bellona/interchange/package.json Bellona asset interchange manifest for GLTF/USD/FBX migration workflows
engine-media source-entrypoint n/a libs/bellona/interchange/src/index.ts Bellona interchange entrypoint for import/export, validation, and transforms
engine-media workspace-manifest @bellona/openusd libs/bellona/openusd/package.json Bellona OpenUSD pipeline manifest for sovereign scene, composition, and asset workflows
engine-media source-entrypoint n/a libs/bellona/openusd/src/index.ts Bellona OpenUSD entrypoint for stage, composition, and MaterialX tooling
engine-media workspace-manifest @bellona/virtual-production libs/bellona/virtual-production/package.json Bellona virtual production manifest for sovereign LED wall and tracking workflows
engine-media source-entrypoint n/a libs/bellona/virtual-production/src/index.ts Bellona virtual production entrypoint for bridge, tracking, LED wall, and compositing subsystems
runtime-foundation workspace-manifest neith-alloc libs/neith/core/crates/neith-alloc/Cargo.toml Neith sovereign memory allocator crate manifest
runtime-foundation source-entrypoint n/a libs/neith/core/crates/neith-alloc/src/lib.rs Neith allocator entrypoint exposing arena, TLSF, and virtual memory systems
runtime-foundation workspace-manifest neith-runtime libs/neith/core/crates/neith-runtime/Cargo.toml Neith sovereign async runtime crate manifest
runtime-foundation source-entrypoint n/a libs/neith/core/crates/neith-runtime/src/lib.rs Neith runtime entrypoint exposing executor, scheduler, and I/O subsystems
linux-platform workspace-manifest neith-creative libs/neith/linux/crates/neith-creative/Cargo.toml Neith creative workflow integration manifest
linux-platform source-entrypoint n/a libs/neith/linux/crates/neith-creative/src/lib.rs Neith creative workflow entrypoint for render farm, remote sessions, and workstation orchestration
linux-platform workspace-manifest neith-distro-core libs/neith/linux/crates/neith-distro-core/Cargo.toml Neith Linux distribution core manifest
linux-platform source-entrypoint n/a libs/neith/linux/crates/neith-distro-core/src/lib.rs Neith Linux distribution core entrypoint for channels, generations, and system identity
linux-platform workspace-manifest neith-settings libs/neith/linux/crates/neith-settings/Cargo.toml Neith Control Center manifest
linux-platform source-entrypoint n/a libs/neith/linux/crates/neith-settings/src/lib.rs Neith Control Center entrypoint for system settings and accessibility surfaces
linux-platform system-config n/a libs/neith/linux/flake.nix Neith Linux reproducible flake configuration for sovereign infrastructure builds
release-quality workspace-manifest @neith/qa libs/neith/qa/package.json Neith QA certification package manifest
release-quality source-entrypoint n/a libs/neith/qa/src/index.ts Neith QA entrypoint exposing code-quality and doc-quality auditors
release-quality workspace-manifest @neith/release libs/neith/release/package.json Neith release/distribution package manifest
release-quality source-entrypoint n/a libs/neith/release/src/index.ts Neith release entrypoint for pipeline, distribution, performance, and platform publishing
ai-local-stack workspace-manifest @oshun/ai libs/shared/ai/package.json Shared AI abstraction manifest that hosts local and remote provider routing
ai-local-stack source-entrypoint n/a libs/shared/ai/src/index.ts Shared AI entrypoint exposing Ollama and local stack factories for phased migration
ai-local-stack source-entrypoint n/a libs/shared/ai/src/local/index.ts Local LLM stack entrypoint for model management, inference, and quantization
ai-local-stack source-entrypoint n/a libs/shared/ai/src/providers/ollama.ts Ollama provider implementation for local sovereign LLM execution

Audit Result#

All required sovereign replacement surfaces are present and expose the expected migration-facing capabilities. The repository currently supports phased migration across runtime, release/QA, Linux platform, engine/media, and AI local-stack lanes.

Interpretation#

Oshun is still operating with transitional integrations, but it now has auditable sovereign replacement foundations in the repository for the major stack layers that matter to a long-horizon migration plan. That makes the migration path actionable instead of theoretical.