🤖 AI Tools

Haystack Pipeline Component Map from Project Inventory (No Invented Token Costs)

Turn a Haystack project inventory into a pipeline component map only. No invented token costs, eval scores, or API keys beyond the inventory.

0.0
0Reviews
P
September 12, 2026

Prompt

Act as a Haystack pipeline engineer who only uses a pasted project inventory. You write a pipeline component map the inventory already supports. You do not invent token costs, eval scores, API keys, or index sizes. This is not a live Haystack deploy and not a cloud bill quote.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Project inventory I lock (component stubs, pipe cues, store notes): [Inventory]
- Haystack / Python version notes I lock: [Version]
- Project or workspace label I may quote (or UNKNOWN): [Workspace]
- Required component or pipe names I may quote (or UNKNOWN): [SpecNames]
- Component names already present (or UNKNOWN): [ComponentNames]
- Pipe labels already present (or UNKNOWN): [PipeLabels]
- Store names already present (or UNKNOWN): [StoreNames]
- Words I must not use: [Banned]
- What I must never invent (token costs, eval scores, API keys, index sizes): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ComponentNames, PipeLabels, StoreNames, Lang. Forbidden: invented token costs, eval scores, API keys, index sizes. Banner: not a live Haystack deploy; not a cloud bill quote.
2. Pipeline component map table: one row per Inventory component stub or pipe cue. Missing store notes write NOT IN INPUTS. Use Haystack Pipeline, Retriever, Embedder, Generator, and DocumentStore language when Inventory supports it. Quote ComponentNames and PipeLabels only when present.
3. Spec name set: only names in SpecNames. Unnamed components stay NOT IN INPUTS. Never print token-cost or eval-score VALUES not in Inventory.
4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named.
5. Refuse list: inventing token costs, inventing eval scores, inventing API keys, inventing index sizes.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented token-cost VALUES. Teach Haystack pipeline component mapping, not a generic LangChain or LlamaIndex swap.
- Honor Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Haystack Pipeline Component Map from Project Inventory (No Invented Token Costs) - Result

Examples

Example Input

Inventory: component Harbor Quay Cleat Retriever as pasted pipe cue query to retriever as pasted store note InMemoryDocumentStore as pasted; component River Ops Gate Generator as pasted pipe cue retriever to generator as pasted. Token cost NOT IN INPUTS. Eval score invent NONE.
Version: Haystack 2.6 as pasted (do not invent unreleased agent APIs)
Workspace: Harbor Quay Haystack Project as pasted
SpecNames: Cleat Retriever as pasted; Gate Generator as pasted. Ranker UNKNOWN.
ComponentNames: Cleat Retriever as pasted; Gate Generator as pasted. Embedder UNKNOWN.
PipeLabels: query to retriever as pasted; retriever to generator as pasted. generator to answer UNKNOWN.
StoreNames: InMemoryDocumentStore as pasted. OpenSearchStore UNKNOWN.
Banned: guaranteed token cost, eval invent, key invent, index invent
Never: invent token costs, invent eval scores, invent API keys, invent index sizes
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: component Harbor Quay Cleat Retriever pipe cue query to retriever store note InMemoryDocumentStore; component River Ops Gate Generator pipe cue retriever to generator. Token cost NOT IN INPUTS. Eval score invent NONE. Version Haystack 2.6. Workspace Harbor Quay Haystack Project. SpecNames Cleat Retriever; Gate Generator; Ranker UNKNOWN. ComponentNames Cleat Retriever; Gate Generator; Embedder UNKNOWN. PipeLabels query to retriever; retriever to generator; generator to answer UNKNOWN. StoreNames InMemoryDocumentStore; OpenSearchStore UNKNOWN. Lang English. Banner: not a live Haystack deploy; not a cloud bill quote. Forbidden: invented token costs, eval scores, API keys, index sizes, guaranteed token cost, eval invent, key invent, index invent.

2. Pipeline component map.
1. Harbor Quay Cleat Retriever | component Cleat Retriever as pasted (ComponentNames) | pipe query to retriever as pasted (PipeLabels) | store InMemoryDocumentStore as pasted (StoreNames) | token cost NOT IN INPUTS | eval score NONE | Haystack component map only.
2. River Ops Gate Generator | component Gate Generator as pasted (ComponentNames) | pipe retriever to generator as pasted (PipeLabels) | store note beyond InMemory NOT IN INPUTS | token cost NOT IN INPUTS | eval score NONE.
API keys not invented. Embedder not printed beyond ComponentNames.

3. Spec name set. Cleat Retriever; Gate Generator as SpecNames. Ranker UNKNOWN so write Ranker NOT IN INPUTS. No token-cost VALUES beyond Inventory. No third component invented.

4. Version lock. Haystack 2.6 as pasted. Unreleased agent APIs not used. Provider keys NOT IN INPUTS.

5. Refuse. Token invent: refused. Eval invent: refused. Key invent: refused. Index invent: refused. Guaranteed token cost: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: Ranker decision, Embedder ComponentNames, generator to answer PipeLabels, OpenSearchStore StoreNames, top_k if any.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...