ARM64-first
Generic userspace validated for arm64 while leaving boot firmware to device packs.
Lightweight KINGAI userspace for ARM64, gateways, robotics, cameras and industrial PCs—with the same policy, memory and agent principles adapted to constrained devices.
KINGAI separates the portable agent/security/update layers from board-specific kernels, bootloaders, firmware and device trees. That avoids pretending one ARM image can boot every device.
Generic userspace validated for arm64 while leaving boot firmware to device packs.
Agents and device integrations can sit behind capability policy instead of direct root access.
Local policy, memory and compatible models can continue when cloud connectivity disappears.
Kernel, DTB, firmware and boot artifacts are declared, hashed and license-reviewed.
Each device pack declares architecture, board identity, boot method, artifacts, hashes, licensing and secure-boot capability.
Kernel, initrd, DTB and bootloader are board-specific.
Artifacts are hashed and manifests are expected to be signed before formal release.
Firmware and bootloader licensing is reviewed rather than assumed.
The generic image pipeline is verified, but public bootable device images require board-specific release evidence.