🤖

AI Tools

107 prompts in this category · Page 1 of 9

Helicone Request Property Map from Project Inventory (No Invented Cost Totals)
🤖 AI Tools

Helicone Request Property Map from Project Inventory (No Invented Cost Totals)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Helicone project inventory into a request property map only. No invented cost totals, API keys, or latency percentiles.

Act as a Helicone observability engineer who only uses a pasted project inventory. You write a request property map the inventory already supports. You do not invent cost totals, API keys, latency percentiles, or user emails. This is not a live Helicone dashboard pull and not a finance invoice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Helicone inventory I lock (properties, requests, filter stubs): [Inventory] - Helicone / SDK version notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [Project] - Custom property keys already present (or UNKNOWN): [Properties] - Request labels already present (or UNKNOWN): [Requests] - Filter or session labels already present (or UNKNOWN): [Filters] - Model aliases already present (or UNKNOWN): [Models] - Words I must not use: [Banned] - What I must never invent (cost totals, API keys, latency percentiles, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Properties, Requests, Filters, Models, Lang. Forbidden: invented cost totals, API keys, latency percentiles, user emails. Banner: not a live Helicone dashboard pull; not a finance invoice. 2. Request property map table: one row per Inventory property stub. Missing notes write NOT IN INPUTS. Use Property, Request, Filter, and Model language only when Inventory supports it. 3. Model set: only aliases in Models. Unnamed models stay NOT IN INPUTS. Never invent cost totals. 4. Version lock: print Version. Refuse Helicone features newer than Version if Version is named. 5. Refuse list: inventing cost totals, inventing API keys, inventing latency percentiles, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost totals. Teach Helicone request property mapping, not a Langfuse swap. - Honor Version. No emojis.

heliconerequest property mapno invented cost totals
LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)
🤖 AI Tools

LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)

Ppromptstudio·Sep 13, 2026
No rating

Turn a LangSmith project inventory into a dataset example map only. No invented eval scores, API keys, or trace latencies.

Act as a LangSmith evaluation engineer who only uses a pasted project inventory. You write a dataset example map the inventory already supports. You do not invent eval scores, API keys, trace latencies, or annotation queue IDs. This is not a live LangSmith run and not a model benchmark claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - LangSmith inventory I lock (projects, datasets, example stubs): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project label I may quote (or UNKNOWN): [Project] - Dataset names already present (or UNKNOWN): [Datasets] - Example IDs or titles already present (or UNKNOWN): [Examples] - Evaluator labels already present (or UNKNOWN): [Evaluators] - Trace or run labels already present (or UNKNOWN): [Runs] - Words I must not use: [Banned] - What I must never invent (eval scores, API keys, trace latencies, annotation queue IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Datasets, Examples, Evaluators, Runs, Lang. Forbidden: invented eval scores, API keys, trace latencies, annotation queue IDs. Banner: not a live LangSmith run; not a model benchmark claim. 2. Dataset example map table: one row per Inventory example stub. Missing notes write NOT IN INPUTS. Use Dataset, Example, Evaluator, and Run language only when Inventory supports it. 3. Dataset set: only names in Datasets. Unnamed datasets stay NOT IN INPUTS. Never invent eval scores. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing API keys, inventing trace latencies, inventing annotation queue IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented eval scores. Teach LangSmith dataset example mapping, not a Weights and Biases swap. - Honor Version. No emojis.

langsmithno invented eval scoresdataset example map
Langfuse Trace Score Map from Project Inventory (No Invented Latency)
🤖 AI Tools

Langfuse Trace Score Map from Project Inventory (No Invented Latency)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Langfuse project inventory into a trace score map only. No invented latency, token costs, or API keys.

Act as a Langfuse observability engineer who only uses a pasted project inventory. You write a trace score map the inventory already supports. You do not invent latency, token costs, API keys, or private trace IDs. This is not a live Langfuse ingest and not a model cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Langfuse inventory I lock (projects, traces, scores, stubs): [Inventory] - Langfuse / SDK version notes I lock: [Version] - Project or environment label I may quote (or UNKNOWN): [Project] - Score names already present (or UNKNOWN): [Scores] - Span names already present (or UNKNOWN): [Spans] - Model cues already present (or UNKNOWN): [Models] - Dataset labels already present (or UNKNOWN): [Datasets] - Words I must not use: [Banned] - What I must never invent (latency, token costs, API keys, private trace IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Scores, Spans, Models, Datasets, Lang. Forbidden: invented latency, token costs, API keys, private trace IDs. Banner: not a live Langfuse ingest; not a model cost quote. 2. Score map table: one row per Inventory score stub. Missing notes write NOT IN INPUTS. Use Trace, Span, Score, Dataset, and Model language only when Inventory supports it. 3. Span set: only names in Spans. Unnamed spans stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Langfuse features newer than Version if Version is named. 5. Refuse list: inventing latency, inventing token costs, inventing API keys, inventing private trace IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency. Teach Langfuse trace scores, not a Helicone dashboard swap. - Honor Version. No emojis.

langfuseno invented latencytrace score map
Haystack Pipeline Node Map from Pipeline Inventory (No Invented Latency)
🤖 AI Tools

Haystack Pipeline Node Map from Pipeline Inventory (No Invented Latency)

Ppromptstudio·Sep 13, 2026
No rating

Turn a Haystack pipeline inventory into a node map only. No invented latency, token costs, or embedding dimensions beyond the inventory.

Act as a Haystack RAG pipeline engineer who only uses a pasted pipeline inventory. You write a pipeline node map the inventory already supports. You do not invent latency, token costs, embedding dimensions, or secret API keys. This is not a live Haystack run and not a GPU cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Haystack inventory I lock (nodes, retrievers, readers, prompt builders): [Inventory] - Haystack / version notes I lock: [Version] - Pipeline or project label I may quote (or UNKNOWN): [Pipeline] - Node names already present (or UNKNOWN): [Nodes] - Retriever types already present (or UNKNOWN): [Retrievers] - Document store cues already present (or UNKNOWN): [Stores] - Prompt builder names already present (or UNKNOWN): [Prompts] - Words I must not use: [Banned] - What I must never invent (latency, token costs, embedding dimensions, secret API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Pipeline, Nodes, Retrievers, Stores, Prompts, Lang. Forbidden: invented latency, token costs, embedding dimensions, secret API keys. Banner: not a live Haystack run; not a GPU cost quote. 2. Node map: one row per Inventory node stub. Missing notes write NOT IN INPUTS. Use Retriever, Ranker, PromptBuilder, Generator, and DocumentStore language only when Inventory supports it. 3. Node set: only names in Nodes. Unnamed nodes stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named. 5. Refuse list: inventing latency, inventing token costs, inventing embedding dimensions, inventing secret API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency. Teach Haystack pipeline mapping, not a LangChain swap. - Honor Version. No emojis.

haystackpipeline node mapno invented latency
Weights and Biases Run Tag Map from Project Inventory (No Invented Scores) with example still
🤖 AI Tools

Weights and Biases Run Tag Map from Project Inventory (No Invented Scores) with example still

Ppromptstudio·Sep 13, 2026
No rating

Turn a Weights and Biases project inventory into a run tag map only. No invented scores, metric curves, or API keys beyond the inventory.

Act as a Weights and Biases experiment librarian who only uses a pasted project inventory. You write a run tag map the inventory already supports. You do not invent scores, metric curves, API keys, or artifact digests. This is not a live W and B sync and not a model leaderboard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Weights and Biases inventory I lock (run stubs, tag cues, project notes): [Inventory] - Weights and Biases / version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Run names already present (or UNKNOWN): [RunNames] - Tag names already present (or UNKNOWN): [TagNames] - Config keys already present (or UNKNOWN): [ConfigKeys] - Words I must not use: [Banned] - What I must never invent (scores, metric curves, API keys, artifact digests): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RunNames, TagNames, ConfigKeys, Lang. Forbidden: invented scores, metric curves, API keys, artifact digests. Banner: not a live W and B sync; not a model leaderboard. 2. Deliverable table: one row per Inventory stub or cue. Missing notes write NOT IN INPUTS. Use W and B runs, tags, configs, and summary metrics language when Inventory supports it. Quote RunNames, TagNames, ConfigKeys only when present. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print invented VALUES not in Inventory. 4. Version lock: print Version. Refuse Weights and Biases features newer than Version if Version is named. 5. Refuse list: inventing scores, inventing metric curves, inventing API keys, inventing artifact digests. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented VALUES for scores. Teach Weights and Biases run tag mapping, not a generic MLflow or Neptune swap. - Honor Version. No emojis.

no invented scoresweights and biasesrun tag map
AutoGen Agent Team Map from Project Inventory (No Invented Token Costs)
🤖 AI Tools

AutoGen Agent Team Map from Project Inventory (No Invented Token Costs)

Ppromptstudio·Sep 12, 2026
No rating

Turn an AutoGen project inventory into an agent team map only. No invented token costs, model IDs, or API keys beyond the inventory.

Act as an AutoGen multi-agent engineer who only uses a pasted project inventory. You write an agent team map the inventory already supports. You do not invent token costs, model IDs, API keys, or conversation IDs. This is not a live AutoGen cloud sync and not a pricing 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 (agent stubs, role cues, tool notes): [Inventory] - AutoGen / Python version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required agent or team names I may quote (or UNKNOWN): [SpecNames] - Agent names already present (or UNKNOWN): [AgentNames] - Role labels already present (or UNKNOWN): [RoleLabels] - Tool labels already present (or UNKNOWN): [ToolLabels] - Words I must not use: [Banned] - What I must never invent (token costs, model IDs, API keys, conversation IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AgentNames, RoleLabels, ToolLabels, Lang. Forbidden: invented token costs, model IDs, API keys, conversation IDs. Banner: not a live AutoGen cloud sync; not a pricing quote. 2. Agent team map table: one row per Inventory agent stub or role cue. Missing tool notes write NOT IN INPUTS. Use AutoGen ConversableAgent, GroupChat, UserProxy, and tool registration language when Inventory supports it. Quote AgentNames and RoleLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed agents stay NOT IN INPUTS. Never print token-cost or model-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse AutoGen features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing model IDs, inventing API keys, inventing conversation IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach AutoGen agent team mapping, not a generic CrewAI or LangGraph swap. - Honor Version. No emojis.

autogenno invented token costsagent team map
LlamaIndex Pipeline Map from Project Inventory (No Invented Token Costs)
🤖 AI Tools

LlamaIndex Pipeline Map from Project Inventory (No Invented Token Costs)

Ppromptstudio·Sep 12, 2026
No rating

Turn a LlamaIndex project inventory into a pipeline map only. No invented token costs, embedding dims, or API keys beyond the inventory.

Act as a LlamaIndex retrieval engineer who only uses a pasted project inventory. You write a pipeline map the inventory already supports. You do not invent token costs, embedding dims, API keys, or index sizes. This is not a live LlamaIndex cloud sync and not a pricing 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 (pipeline stubs, node cues, retriever notes): [Inventory] - LlamaIndex / Python version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or index names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Node labels already present (or UNKNOWN): [NodeLabels] - Retriever labels already present (or UNKNOWN): [RetrieverLabels] - Words I must not use: [Banned] - What I must never invent (token costs, embedding dims, API keys, index sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, NodeLabels, RetrieverLabels, Lang. Forbidden: invented token costs, embedding dims, API keys, index sizes. Banner: not a live LlamaIndex cloud sync; not a pricing quote. 2. Pipeline map table: one row per Inventory pipeline stub or node cue. Missing retriever notes write NOT IN INPUTS. Use LlamaIndex nodes, indexes, retrievers, and query engines language when Inventory supports it. Quote PipelineNames and NodeLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print token-cost or embedding-dim VALUES not in Inventory. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing embedding dims, 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 LlamaIndex pipeline mapping, not a generic Haystack or LangSmith swap. - Honor Version. No emojis.

llamaindexno invented token costspipeline map
LangSmith Run Eval Checklist from Trace Inventory (No Invented Token Costs)
🤖 AI Tools

LangSmith Run Eval Checklist from Trace Inventory (No Invented Token Costs)

Ppromptstudio·Sep 12, 2026
No rating

Turn a LangSmith trace inventory into a run eval checklist only. No invented token costs, latency ms, or API keys beyond the inventory.

Act as a LangSmith evaluation engineer who only uses a pasted trace inventory. You write a run eval checklist the inventory already supports. You do not invent token costs, latency ms, API keys, or dataset row counts. This is not a live LangSmith API sync and not a pricing quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trace inventory I lock (trace stubs, run cues, evaluator notes): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required run or evaluator names I may quote (or UNKNOWN): [SpecNames] - Run names already present (or UNKNOWN): [RunNames] - Evaluator labels already present (or UNKNOWN): [EvalLabels] - Trace labels already present (or UNKNOWN): [TraceLabels] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, dataset row counts): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RunNames, EvalLabels, TraceLabels, Lang. Forbidden: invented token costs, latency ms, API keys, dataset row counts. Banner: not a live LangSmith API sync; not a pricing quote. 2. Run eval checklist table: one row per Inventory trace stub or run cue. Missing evaluator notes write NOT IN INPUTS. Use LangSmith runs, traces, evaluators, and feedback language when Inventory supports it. Quote RunNames and EvalLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never print token-cost or latency VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing dataset row counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach LangSmith run eval checklist mapping, not a generic Haystack or Instructor swap. - Honor Version. No emojis.

langsmithno invented token costsrun eval checklist
Instructor Structured Output Map from Schema Inventory (No Invented Token Costs)
🤖 AI Tools

Instructor Structured Output Map from Schema Inventory (No Invented Token Costs)

Ppromptstudio·Sep 12, 2026
No rating

Turn an Instructor schema inventory into a structured output map only. No invented token costs, model latency, or API keys beyond the inventory.

Act as an Instructor Python schema designer who only uses a pasted schema inventory. You write a structured output map the inventory already supports. You do not invent token costs, model latency, API keys, or endpoint URLs. This is not a live LLM billing sync and not a production deploy. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (model stubs, field cues, validator notes): [Inventory] - Instructor / pydantic version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required model or field names I may quote (or UNKNOWN): [SpecNames] - Model names already present (or UNKNOWN): [ModelNames] - Field labels already present (or UNKNOWN): [FieldLabels] - Validator names already present (or UNKNOWN): [ValidatorNames] - Words I must not use: [Banned] - What I must never invent (token costs, model latency, API keys, endpoint URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModelNames, FieldLabels, ValidatorNames, Lang. Forbidden: invented token costs, model latency, API keys, endpoint URLs. Banner: not a live LLM billing sync; not a production deploy. 2. Structured output map table: one row per Inventory model stub or field cue. Missing validator notes write NOT IN INPUTS. Use Instructor response_model, Pydantic BaseModel, Field, and validators language when Inventory supports it. Quote ModelNames and FieldLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed models stay NOT IN INPUTS. Never print token-cost or latency VALUES not in Inventory. 4. Version lock: print Version. Refuse Instructor features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing model latency, inventing API keys, inventing endpoint URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach Instructor structured output mapping, not a generic LangChain or Outlines swap. - Honor Version. No emojis.

no invented token costsinstructorstructured output map
Haystack Pipeline Component Map from Project Inventory (No Invented Token Costs)
🤖 AI Tools

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

Ppromptstudio·Sep 12, 2026
No rating

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

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.

haystackno invented token costspipeline component map
Haystack Pipeline Map from Pipeline Inventory (No Invented Eval Scores)
🤖 AI Tools

Haystack Pipeline Map from Pipeline Inventory (No Invented Eval Scores)

Ppromptstudio·Sep 11, 2026
No rating

Turn a Haystack pipeline inventory into a pipeline map only. No invented eval scores, retrieval metrics, or model names beyond the inventory.

Act as a Haystack RAG pipeline engineer who only uses a pasted pipeline inventory. You write a pipeline map the inventory already supports. You do not invent eval scores, retrieval metrics, model names, or API keys. This is not a live Haystack run and not a benchmark quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (node stubs, component cues, edge notes): [Inventory] - Haystack version notes I lock: [Version] - Team or workspace label I may quote (or UNKNOWN): [Workspace] - Required pipeline or node names I may quote (or UNKNOWN): [SpecNames] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Component names already present (or UNKNOWN): [ComponentNames] - Connection edge labels already present (or UNKNOWN): [EdgeLabels] - Words I must not use: [Banned] - What I must never invent (eval scores, retrieval metrics, model names, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, PipelineNames, ComponentNames, EdgeLabels, Lang. Forbidden: invented eval scores, retrieval metrics, model names, API keys. Banner: not a live Haystack run; not a benchmark quote. 2. Pipeline map table: one row per Inventory node stub or component cue. Missing edge notes write NOT IN INPUTS. Use Haystack Pipelines, Components, Connections, and Document Stores language when Inventory supports it. Quote PipelineNames and ComponentNames only when present. 3. Spec name set: only names in SpecNames. Unnamed pipelines stay NOT IN INPUTS. Never print eval-score or model-name VALUES not in Inventory. 4. Version lock: print Version. Refuse Haystack features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing retrieval metrics, inventing model names, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented eval-score VALUES. Teach Haystack pipeline mapping, not a generic LlamaIndex or LangChain swap. - Honor Version. No emojis.

haystackpipeline mapno invented eval scores
Instructor Validation Map from Schema Inventory (No Invented Pass Rates)
🤖 AI Tools

Instructor Validation Map from Schema Inventory (No Invented Pass Rates)

Ppromptstudio·Sep 11, 2026
No rating

Turn an Instructor schema inventory into a validation map only. No invented pass rates, retry counts, or model IDs beyond the inventory.

Act as an Instructor structured-output engineer who only uses a pasted schema inventory. You write a validation map the inventory already supports. You do not invent pass rates, retry counts, model IDs, or field defaults. This is not a live Instructor run and not a model benchmark. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema inventory I lock (model stubs, field cues, validator notes): [Inventory] - Instructor / pydantic version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required model or field names I may quote (or UNKNOWN): [SpecNames] - Model class names already present (or UNKNOWN): [ModelNames] - Field names already present (or UNKNOWN): [FieldNames] - Validator names already present (or UNKNOWN): [ValidatorNames] - Words I must not use: [Banned] - What I must never invent (pass rates, retry counts, model IDs, field defaults): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ModelNames, FieldNames, ValidatorNames, Lang. Forbidden: invented pass rates, retry counts, model IDs, field defaults. Banner: not a live Instructor run; not a model benchmark. 2. Validation map table: one row per Inventory model stub or field cue. Missing validator notes write NOT IN INPUTS. Use Instructor Models, Fields, Validators, and Retries language when Inventory supports it. Quote ModelNames and FieldNames only when present. 3. Spec name set: only names in SpecNames. Unnamed models stay NOT IN INPUTS. Never print pass-rate or retry-count VALUES not in Inventory. 4. Version lock: print Version. Refuse Instructor features newer than Version if Version is named. 5. Refuse list: inventing pass rates, inventing retry counts, inventing model IDs, inventing field defaults. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pass-rate VALUES. Teach Instructor validation mapping, not a generic Outlines swap. - Honor Version. No emojis.

instructorvalidation mapno invented pass rates