equipment-extract

Equipment extraction from Knowledge Artifact markdown files involves reading KA-*.md documents within a specific Knowledge Type folder to identify physically instantiated items like vessels, tanks, and valves. It generates a structured equipment register document with source-traceable item rows and a summary count.

A per-KTY equipment register is a structured document cataloging discrete physical equipment items extracted from Knowledge Artifact files. You need to build one when you require a traceable inventory of physical assets like heat exchangers, instruments, and tanks from a specific Knowledge Type folder for downstream audits.

No, generating an equipment extract requires KA-*.md files within the target Knowledge Type folder. While the extraction process reads _CONTEXT.md and _REFERENCES.md for related metadata, the core equipment identification relies on parsing the KA-*.md files to produce the OUTPUT_ROOT/{KTY_ID}_Equipment_Extract.md document.

The best way to build a traceable equipment register from KA files is to process a single Knowledge Type folder and extract named tags representing physical equipment. This method enforces strict read/write boundaries and produces an output markdown file with a structured table, notes, and a total item count.

Yes, equipment extraction supports downstream audits by maintaining strict read/write boundaries and source traceability. The resulting per-KTY equipment register document contains source-traceable item rows extracted directly from KA-*.md files, ensuring data integrity for physical asset verification.

Extractable physical equipment items from KA-*.md files include vessels, tanks, heat exchangers, valves, and instruments. The extraction process identifies these physically instantiated assets as named tags within the Knowledge Artifact documents to populate the structured equipment register table.