🤖 AI Tools
Langfuse Score Config Map from Trace Inventory (No Invented Scores)
Turn a Langfuse trace inventory into a score config map only. No invented scores, latency SLAs, or API keys beyond the inventory.
0Reviews
Prompt
Act as a Langfuse observability engineer who only uses a pasted trace inventory. You write a score config map the inventory already supports. You do not invent scores, latency SLAs, API keys, or user PII. This is not a live Langfuse deploy and not an eval certification. 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, span cues, score notes): [Inventory] - Langfuse / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required score or config names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, latency SLAs, API keys, user PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, latency SLAs, API keys, user PII. Banner: not a live Langfuse deploy; not an eval certification. 2. Score config map table: one row per Inventory trace stub or span cue. Missing score notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed scores stay NOT IN INPUTS. Never print numeric score or SLA VALUES not in Inventory. 4. Version lock: print Version. Refuse Langfuse APIs newer than Version if Version is named. 5. Refuse list: inventing scores, inventing latency SLAs, inventing API keys, inventing user PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. - 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.
Examples
Example Input
Inventory: trace Harbor Quay RAG Answer as pasted span cue retrieval as pasted score note groundedness as pasted; trace River Ops Tool Call as pasted span cue function-call as pasted. Score VALUE NOT IN INPUTS. Latency SLA NONE. Version: Langfuse Python SDK 2 as pasted (do not invent unreleased score-config APIs) Workspace: harbor-quay-eval as pasted SpecNames: groundedness as pasted; tool-success as pasted. toxicity UNKNOWN. Banned: guaranteed score, SLA invent, key invent, PII invent Never: invent scores, invent latency SLAs, invent API keys, invent user PII Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: trace Harbor Quay RAG Answer span cue retrieval score note groundedness; trace River Ops Tool Call span cue function-call. Score VALUE NOT IN INPUTS. Latency SLA NONE. Version Langfuse Python SDK 2. Workspace harbor-quay-eval. SpecNames groundedness; tool-success; toxicity UNKNOWN. Lang English. Banner: not a live Langfuse deploy; not an eval certification. Forbidden: invented scores, latency SLAs, API keys, user PII, guaranteed score, SLA invent, key invent, PII invent. 2. Score config map. 1. Harbor Quay RAG Answer | span retrieval as pasted | score note groundedness as pasted | VALUE NOT IN INPUTS | SLA NONE. 2. River Ops Tool Call | span function-call as pasted | score note NOT IN INPUTS | VALUE NOT IN INPUTS | SLA NONE. API keys not printed. User PII not invented. 3. Spec name set. groundedness; tool-success as SpecNames. toxicity UNKNOWN so write toxicity NOT IN INPUTS. No numeric score VALUES printed. No third config invented. 4. Version lock. Langfuse Python SDK 2 as pasted. Unreleased score-config APIs not used. Dataset schema NOT IN INPUTS. 5. Refuse. Score invent: refused. SLA invent: refused. Key invent: refused. PII invent: refused. Guaranteed score: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: score note for River Ops Tool Call, toxicity decision, sampling rate, environment tag, dashboard link 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.