Intelligence Kernel
Phase VII · A0 — the permanent operating layer of GIOS. Given a session or runtime lifecycle, HOW is it booted, hydrated, budgeted, moded, checkpointed, compressed, and shut down — deterministically, referencing governance rather than duplicating it? Every future runtime inherits this lifecycle. Loads nothing. Read-only.
The Intelligence Kernel models the operating layer of GIOS in code — session lifecycle, boot sequence, module hydration + lazy-load classes (always / lazy / reference / deferred / cold storage / future), the four budgets (context / token / reasoning / memory), the six execution-intensity modes, checkpointing, context compression, repository + snapshot hydration, module inheritance, cache policy, runtime lifecycle, shutdown, and SESSION_END. Given a session request (task tier, mode, operation, machine-state / milestone flags, lifecycle phase) it computes a deterministic KernelHydrationPlan: the token-minimal module set to load, in boot order, under the tier's budgets, with checkpoint / compression / governance-sync flags. Fail-closed: the default is to EXCLUDE a module unless the task provably requires it; future modules never hydrate. It executes nothing, imports nothing, and loads nothing; every model references its canonical governance owner rather than restating it. Every future runtime — the V5 Execution runtime included — inherits this lifecycle and redefines no boot behavior.