Variable: KernelSchemas

Makaio Framework

---

Makaio Framework / kernel / KernelSchemas

Variable: KernelSchemas

const KernelSchemas: object

Defined in: ../../../packages/kernel/src/namespace/kernel-schemas.ts:16

Kernel domain schemas.

Provides subjects for kernel introspection and lifecycle signalling. Plugin/extension discovery has moved to the kernel:extension.* namespace served by the ExtensionCoordinator.

Type Declaration

isReady

isReady: object

Probe kernel readiness state.

Subject: kernel.isReady Type: Request (RPC) Purpose: Allows clients that connect after startup to query readiness without waiting for the one-time kernel.ready event.

isReady.request

request: ZodObject<{ }, $strip>

isReady.response

response: ZodObject<{ machineId: ZodString; ready: ZodBoolean; }, $strip>

lifecycle.shutdown

lifecycle.shutdown: object

Notify observers that lifecycle wiring shutdown has completed.

Subject: kernel.lifecycle.shutdown Type: Request (RPC) Purpose: Used as an observability/synchronization hook. Package teardown is performed by the extension coordinator, not by handlers on this subject.

lifecycle.shutdown.request

request: ZodObject<{ }, $strip>

lifecycle.shutdown.response

response: ZodObject<{ }, $strip>

lifecycle.start

lifecycle.start: object

Notify observers that lifecycle wiring has completed.

Subject: kernel.lifecycle.start Type: Request (RPC) Purpose: Used as an observability/synchronization hook. Package startup is performed by the extension coordinator, not by handlers on this subject.

lifecycle.start.request

request: ZodObject<{ machineId: ZodString; }, $strip>

lifecycle.start.response

response: ZodObject<{ }, $strip>

phase.busCreated

phase.busCreated: ZodObject<{ machineId: ZodString; }, $strip> = phaseMachinePayload

Signal that the bus has been created and is ready for use.

Subject: kernel.phase.busCreated Type: Event (fire-and-forget) Purpose: Emitted immediately after bus creation so early external observers (e.g., transport bridges) can attach before config or services start.

phase.coordinatorReady

phase.coordinatorReady: LocalSubjectSchema<{ request: ZodObject<{ machineId: ZodString; }, $strip>; response: ZodObject<{ }, $strip>; }>

Lifecycle barrier emitted after the extension coordinator has started all loaded packages.

Subject: kernel.phase.coordinatorReady Type: Broadcast request Purpose: Allows host-owned integrations to finish post-coordinator wiring before the kernel announces full readiness.

phase.coreReady

phase.coreReady: ZodObject<{ machineId: ZodString; }, $strip> = phaseMachinePayload

Signal that the bus, config service, and runtime-host resource handlers are ready.

Subject: kernel.phase.coreReady Type: Event (fire-and-forget) Purpose: Emitted after bus creation, config service registration, and runtime resource provider registration — before lifecycle wiring begins. External transports (e.g., WebSocket bus server) hook in here so they have bus and machine identity but are available before full service readiness.

phase.servicesReady

phase.servicesReady: ZodObject<{ machineId: ZodString; }, $strip> = phaseMachinePayload

Signal that lifecycle wiring and lifecycle.start have completed.

Subject: kernel.phase.servicesReady Type: Event (fire-and-forget) Purpose: Emitted after startLifecycleWiring and lifecycle.start complete. All core services are registered and ready to handle requests at this point.

ready

ready: ZodObject<{ machineId: ZodString; }, $strip> = phaseMachinePayload

Signal that the kernel has completed initialization.

Subject: kernel.ready Type: Event (fire-and-forget) Purpose: SharedWorker waits for this before considering the backend ready. Eliminates the handler registration race where tabs send requests before registerRuntimeHandlers() completes.