Extracts Factory Service Manual (FSM) section codes (e.g. 8A-9, 6E-92) from contents tables and body text and writes them onto the Qdrant manuals payload, giving a second, structural retrieval axis alongside the embedding-derived system tags. On telep-mainframe, code under ~/knowledgebase/kb-vectors/.
For Agents — what gets written
- A finite-state parser pulls FSM codes (
8A-9,6E-92, …) from contents tables + text.- Qdrant payload gains:
section_codes,section_names,section_prefixeson 490 pages.- Index file:
kb-vectors/section_index.json= 1254 codes.
Prefix → system-tag map
Each code’s alpha-numeric prefix maps to a vehicle system:
| Prefix(es) | System |
|---|---|
8A / 8B / 8C | Electrical |
6E / 6C / 6J / 6K | Fuel & Emissions |
6A | Engine |
6B | Cooling |
7A–7F | Drivetrain |
3x | Steering & Suspension |
1A / 1B | HVAC |
9J | Body |
0x | Diagnostics |
Complementary to the text system-tags, not redundant
~61% agreement = two independent signals worth keeping both
The section-prefix system and the embedding-derived text system-tags (see 2026-08-06-kb-embedding-classifiers-system-tags-and-image-types) agree ~61% of the time. That partial agreement means they are complementary, not redundant — the section code is a hard structural signal from the manual’s own contents table, while the text tag is a soft semantic signal from the page prose. Where they disagree, both are worth surfacing (one may catch what the other misses).
Related
- 2026-08-06-kb-embedding-classifiers-system-tags-and-image-types — the embedding-derived system-tags this cross-checks (~61% agreement)
- 2026-08-06-kb-orphan-heading-recovery-subsystem — a sibling Qdrant-payload enrichment pass over the same
manualscollection - 2026-07-24-kb-vectorize-complete — the Qdrant
manualscollection these payloads attach to - kb-agent-api — agent-facing search; section codes are a candidate structural filter
- telep-mainframe — the host
- SESSION-HANDOVER
- homelab
- LOG
- TOPICS