Core API Overview

The core API is the stable foundation beneath content systems. Runtime evidence in the current 0.5.x line covers API initialization, version access, main-thread identity, diagnostics availability, mod registration, registered-mod lookup, dependency metadata, owner context identity and logger handoff.

The important architectural boundary is ownership: a mod operates through its registered owner/context, and registrations/subscriptions are tracked against that owner so cleanup and isolation are enforceable.

Core responsibilities

• consumer/mod registration;
• namespaced identity and owner validation;
• owner-scoped logging;
• disposable lifecycle/event subscriptions;
• diagnostics/state reporting;
• controlled integration with FTK2's game-data lifetime.

Generated type-by-type documentation belongs in the API Reference. Conceptual pages focus on lifecycle and rules that remain true across individual method names.