Add Inspur Group OEM Redfish profile

bible-local/05-collectors.md

@@ -100,6 +100,13 @@ Live Redfish collection must expose profile-match diagnostics:
 - the collect page should render active modules as chips from structured status data, not by
   parsing log lines
 
+Profile matching may use stable platform grammar signals in addition to vendor strings:
+- discovered member/resource naming from lightweight discovery collections
+- firmware inventory member IDs
+- OEM action names and linked target paths embedded in discovery documents
+- replay-only snapshot hints such as OEM assembly/type markers when they are present in
+  `raw_payloads.redfish_tree`
+
 On replay, profile-derived analysis directives may enable vendor-specific inventory linking
 helpers such as processor-GPU fallback, chassis-ID alias resolution, and bounded storage recovery.
 Replay should now resolve a structured analysis plan inside `redfishprofile/`, analogous to the

bible-local/10-decisions.md

@@ -918,3 +918,34 @@ hardware change.
 - Hardware event history (last 7 days) visible in Reanimator `EventLogs` section.
 - No impact on existing inventory pipeline or offline archive replay (archives without `redfish_log_entries` key silently skip parsing).
 - Adds extra HTTP requests during live collection (sequential, after tree-walk completes).
+
+---
+
+## ADL-036 — Redfish profile matching may use platform grammar hints beyond vendor strings
+
+**Date:** 2026-03-25
+**Context:**
+Some BMCs expose unusable `Manufacturer` / `Model` values (`NULL`, placeholders, or generic SoC
+names) while still exposing a stable platform-specific Redfish grammar: repeated member names,
+firmware inventory IDs, OEM action names, and target-path quirks. Matching only on vendor
+strings forced such systems into fallback mode even when the platform shape was consistent.
+
+**Decision:**
+- Extend `redfishprofile.MatchSignals` with doc-derived hint tokens collected from discovery docs
+  and replay snapshots.
+- Allow profile matchers to score on stable platform grammar such as:
+  - collection member naming (`outboardPCIeCard*`, drive slot grammars)
+  - firmware inventory member IDs
+  - OEM action/type markers and linked target paths
+- During live collection, gather only lightweight extra hint collections needed for matching
+  (`NetworkInterfaces`, `NetworkAdapters`, `Drives`, `UpdateService/FirmwareInventory`), not slow
+  deep inventory branches.
+- Keep such profiles out of fallback aggregation unless they are proven safe as broad additive
+  hints.
+
+**Consequences:**
+- Platform-family profiles can activate even when vendor strings are absent or set to `NULL`.
+- Matching logic becomes more robust for OEM BMC implementations that differ mainly by Redfish
+  grammar rather than by explicit vendor strings.
+- Live collection gains a small amount of extra discovery I/O to harvest stable member IDs, but
+  avoids slow deep probes such as `Assembly` just for profile selection.