Equipment Extract

Derived at runtime

• KTY_ID — extracted from {KTY_PATH}/_CONTEXT.md or inferred from folder name

Optional

• None

Runtime overrides

Read boundary

Reads are limited to:

• {RuntimeOverrides.KTY_PATH}/KA-*.md — all Knowledge Artifact files
• {RuntimeOverrides.KTY_PATH}/_CONTEXT.md — KTY identity metadata
• {RuntimeOverrides.KTY_PATH}/_REFERENCES.md — reference context

The skill must NOT read arbitrary files under ScopePath. It does not read Scoping.md, _STATUS.md, or files outside the KTY folder.

Write boundary

Writes are limited to:

• {RuntimeOverrides.OUTPUT_ROOT}/{KTY_ID}_Equipment_Extract.md

OUTPUT_ROOT must already exist. The skill does not create the directory.

Tool usage

• No deterministic tools. This is a reasoning-first extraction skill.
• The allowed-tools frontmatter field is intentionally omitted.

Disallowed behavior:

• No writing outside OUTPUT_ROOT
• No modification of any file in KTY_PATH
• No widening scope beyond the designated KTY folder

Method

Step 0 — Preconditions

1. Validate KTY_PATH exists and is a directory. If not: report RUN_STATUS=FAILED_INPUTS.
2. Validate OUTPUT_ROOT exists. If not: report RUN_STATUS=FAILED_INPUTS.

Step 1 — Read KTY context

1. Read {KTY_PATH}/_CONTEXT.md (best-effort).
2. Extract: KTY ID, KTY name, parent Category ID and name.
3. If _CONTEXT.md is missing or ambiguous, fall back to folder name. Record the fallback in Package Notes.

Step 2 — Enumerate and order KA files

1. List all KA-*.md files in the KTY folder.
2. Build the read list ordered by KA number.

Step 3 — Extract equipment from each KA

For each KA file, extract every discrete physical equipment item:

In scope (extract these):

• Vessels, separators, drums, columns, towers
• Compressors, pumps, blowers, fans
• Heat exchangers, coolers, heaters, reboilers, condensers
• Tanks, storage vessels
• Filters, strainers, coalescers, scrubbers
• Control valves, PSVs, ESDVs, shutdown valves, blowdown valves
• Instruments, meters, analyzers (when named as discrete devices)
• Motors and drivers (when described as discrete tagged/named equipment)
• Any other physically instantiated, discrete named/tagged device

Out of scope (do not extract):

• Virtual machines, software instances
• Buildings or structures (but include equipment housed within them)
• Documents, procedures, specifications
• Non-physical items (data points, software licenses, network addresses)

For each item, record:

Step 4 — Assemble equipment table

Combine all per-KA items into one ordered table with columns:

# | CAT | KTY | KA Source | Equipment Tag | Equipment Name | Package Name | Notes

Rows ordered by KA source (read-list order), then by order of appearance within each KA. Sequential row numbers starting at 1.

Step 5 — Write Package Notes

Contextual observations about:

• Formal vs. implied package/module assignments
• Notable groupings or splits
• Scope boundary ambiguities
• Items excluded with rationale
• Active conflicts or TBDs affecting equipment identification
• Null-result explanation for KTYs with zero physical equipment

Step 6 — Write output file

Write {OUTPUT_ROOT}/{KTY_ID}_Equipment_Extract.md containing, in order:

1. Title: # Equipment Extract — {KTY_ID} {KTY Name}
2. Metadata block: Category, Knowledge Type, Source KA files, Extraction date
3. Equipment Table: the assembled markdown table
4. Package Notes: the bulleted observations
5. Equipment count footer: **{KTY_ID} Equipment Count: {N}**

For KTYs with zero physical equipment: the table is empty or contains a single explanatory row; the count footer reads 0 with a parenthetical explanation; an informational inventory (e.g., virtual machines) may be included for traceability, clearly marked as excluded.

Outputs

• {KTY_ID}_Equipment_Extract.md in OUTPUT_ROOT

Non-negotiable constraints

• Read-only on KTY folders. Never modify any file in {KTY_PATH}.
• No invention. Only extract equipment explicitly mentioned in KA files.
• Exact tags. Equipment tags must be verbatim from source text, never inferred or constructed.
• Sourced package assignments. Package names come from KA text, are marked (indicated) when contextually implied, or are N/A.
• Complete coverage. Every KA-*.md in the folder must be read. Missing files must be reported.
• Null results documented. KTYs with zero physical equipment still produce an extract file with explanation.
• Source traceability. Every table row must cite the specific KA file from which it was extracted.

QA expectations

• All KA files in the folder were read (or absence reported).
• Every equipment table row cites a specific KA source file.
• No equipment items appear that are not in the KA source text.
• Equipment tags are verbatim from source.
• Package assignments are sourced, marked (indicated), or N/A.
• Output file contains all required sections: title, metadata, table, Package Notes, count footer.
• No files in {KTY_PATH} were written or modified.
• Null-result KTYs have an extract file with explanation.

Downstream consumer

This skill does not produce the consolidated Equipment_Master_List.csv. That is a separate assembly step that concatenates per-KTY extract tables after all extractions are complete.