General

This part establishes the shared foundation that every driver module builds on — read it before the individual modules. Requirement keywords and conformance are defined in About This Specification.

What you’ll find here:

• Overview — what the Chiisai HAL is, the peripherals it covers, and what it deliberately leaves out.

• Architecture and Layering — where a driver sits in the system, how it is layered against the software above and the hardware below, and how it reports events upward.

• Naming Conventions — the naming scheme and file layout every driver follows, so modules from different vendors look and integrate consistently.

• Integration Guidelines — how a driver is packaged, configured, and wired into a project, from the integrator’s point of view.

• Guide — worked examples of the shared concepts in real driver code, generalized skeletons of the foundation headers, and the callout file an integrator fills in.

• Reference — the shared type system, compiler abstraction, and services every driver MUST provide and use (normative).

• Requirements — the cross-module rules every conformant driver MUST satisfy, clustered by severity.

• Design Decisions — the rationale behind the cross-module rules, so you understand why the contract looks the way it does.

• Overview
• Architecture and Layering
• Naming Conventions
• Integration Guidelines
• Guide
• Reference
• Requirements
• Design Decisions