context-foundry

Use when the user is running fleet checks, iDRAC/racadm queries, SSH batch loops, or Dell server inventory lookups from a management server. Covers grep -w hostname lookups, ConnectTimeout SSH options, and labeled batch output.

Use when the user is building a standalone Workday-Marketplace compliance rule engine (ACA, multi-state tax, Davis-Bacon, or similar). Covers rule-function signatures, rule ID naming, input normalization, ordering dependencies, and the Phase 2 Workday bridge.

Fleet ops and iDRAC/racadm pitfalls — grep substring matches, SSH hangs, batch output labeling, Dell OME CPLD limitations. Use when scripting fleet checks or batch ops.

Workday Marketplace compliance agent pitfalls — dict-key normalization, inclusive date ranges, rule-id overlap, exemption ordering, jurisdiction-specific thresholds, SPEC drift. Use when building compliance rule engines.

Review a Flowise flow in fresh context using validation and Floweyes findings. Use when a generated Flowise flow needs an independent audit.

Build or update a Flowise AgentFlow v2 JSON file with selective retrieval, validation, and audit. Use when asked to create or modify audited Flowise flows.

Promote a passing Flowise flow from output into example-flows and update retrieval metadata. Use when a draft flow becomes a durable reference.

Repair a Flowise AgentFlow v2 file until validation and Floweyes both pass. Use after build-flowise or when audit findings already exist.