Module class 

2026-09-30: A kernel class (kernels/<class>/) as the planner sees it: its inheritance chain and build defines from HARDWARE.toml, its fusion rules (FUSIONS.toml, inherited and overridden along the chain) and its kernel families (KERNEL_FAMILIES.toml, with points rediscovered from the class’s own resolved sources and evidence kept per class).

Owner: metrale-circuit (hardware). Invariants:

• Rules: a class’s common/FUSIONS.toml either stands alone or names inherits = "<class>", in which case its rules replace the parent’s rules of the same id, add new ones, and remove drops parent rules by id. A class without the file takes its HARDWARE.toml parent’s rules; a class with neither has no rules (ClassRules::None), which the planner reports, never fills in.
• Families: evidence is a measurement on one class. Families inherited from another class’s manifest keep their points (re-resolved against this class’s sources) and lose their evidence, so a report on this class says “unmeasured”, never “optimized”.

Structs

ClassInfo

2026-09-30: What one HARDWARE.toml says about the class.

Enums

ClassRules

2026-09-30: A class’s resolved rule set.

Functions

chain

2026-09-30: The class and its ancestors, own class first.

class_discovered

2026-09-30: The points the manifest’s discover rules find in the class’s OWN trees: each rule’s kernels/<manifest>/... path re-rooted at every class of the chain that is not the manifest’s, matched against what the class compiles. A class’s own copy of a kernel (a per-class file the manifest never listed) becomes a point of its family on that class.

class_families

2026-09-30: The kernel families class is classified against: the nearest KERNEL_FAMILIES.toml along the chain as the base (evidence dropped unless it is the class’s own), the class’s own manifest overriding families by id, and every point re-resolved against the class’s sources (class_points).

class_points

2026-09-30: The points of a family that sources realises: the files of a point that the class compiles as they are, or through its own copy of the same file name (a shadow), rewritten to what the class compiles. Host-side files (crates/...) are shared by every class. A point is kept with the files the class compiles (a point realised by several per-model copies exists where one of them is compiled) and dropped when none is.

class_rules

2026-09-30: The rules class plans with.

parse_class

2026-09-30: Parse kernels/<name>/HARDWARE.toml.

planning_chain

2026-09-30: The classes a plan on class reads rules and families from: its HARDWARE.toml chain, continued through the inherits of the last class’s FUSIONS.toml (a class that does not inherit gb10’s sources may still declare that it plans with gb10’s rules).