Section 30 of 101
29. Core Infrastructure Initialization
Stable section ID: S05-CON-006-SECTION-30 · 27 content blocks
Core Infrastructure Initialization establishes the minimum BIOS services required before building discovery and configuration validation can begin.
Services shall initialize in dependency order.
The minimum sequence is:
trusted identity services;
secure storage access;
configuration database;
time and sequence service;
event logging;
State Engine;
Policy and Rules Engine;
authorization services;
Hardware and Cartridge Abstraction Layer;
Interface Abstraction Layer;
Service Manager;
local API gateway;
- discovery services.
- Each service shall complete its startup health check before dependent services are activated.
Persistent configuration shall initially be loaded into a protected validation context. It shall not become the active configuration until schema, integrity, signature, version, and dependency checks have completed.
The BIOS shall establish a startup event channel before initiating discovery so that early faults and changes are not lost.
Communication interfaces shall initially operate with minimum privileges. Discovery traffic shall not automatically authorize control commands or unrestricted network access.
If a core service cannot start, the Service Manager shall identify:
failed service;
required dependencies;
affected functions;
permitted degraded mode;
recovery action;
whether building operation may continue.