How to Use: Langfuse Trace Session Map from Project Inventory (No Invented Token Totals)

You pasted a messy Langfuse inventory and need a clean deliverable without invented numbers. This PromptDig prompt turns only what you already listed into a structured map or checklist for this job handoff.

What this prompt does

It locks your inventory, version, workspace label, and domain fields, then builds a ledger plus a table that refuses fake metrics. Missing cells stay NOT IN INPUTS instead of guessing.

Use it when you already have real stubs from Langfuse and want a teachable map for this job, not a generic template swap from another vendor. The Generate steps name Langfuse nouns on purpose so a title swap into another category would fail the swap-title test.

The deliverable is aimed at Langfuse maps. Reviewers should see Inventory nouns echoed in the table rows, not marketing fluff. Cap style limits stay soft unless you add them later in Extra.

How to fill the brackets

1. Paste your Inventory with concrete nouns only. Prefer two labeled rows so the example shape stays visible after you swap names.
2. Lock Version to what you actually run. If you do not know the version, write unknown rather than guessing a marketing release name.
3. Fill labels you may quote only when you already have names you are allowed to use.
4. Complete the domain fields that match this job. Leave blanks as UNKNOWN instead of inventing metrics the inventory never stated.
5. Set Banned and Never to the phrases you refuse. Keep Format and Lang explicit.

Who it is for

Practitioners who inherit messy Langfuse inventories. It is also useful when a teammate hands you a partial export and you need a map that stays honest about gaps.

How to run it

1. Open Langfuse Trace Session Map from Project Inventory (No Invented Token Totals) on PromptDig.
2. Copy the prompt into ChatGPT, Claude, or Gemini.
3. Replace every bracket with your locked inventory. Do not leave sample Harbor nouns in place if they are not yours.
4. Run once, then fix only the gaps list. Do not ask the model to invent missing metrics.
5. Paste the map into your handoff doc and keep NOT IN INPUTS visible for reviewers.

What good output looks like

A strong run starts with an honesty ledger that quotes your Inventory nouns and Version. The map tables attach only names that appeared beside each other in Inputs. Refuse lines explicitly reject fake metrics.

Weak output invents metrics, adds vendor features not in Version, or swaps in another tool's nouns. If you see that, tighten Banned and Never, then rerun.

Common mistakes

• Inventing numbers the inventory never stated.
• Treating UNKNOWN as a cue to guess defaults.
• Dropping the gaps list so reviewers cannot see what is still owed.
• Softening Never so the model pads with industry averages.

When to skip this prompt

Skip it if you need live Langfuse automation, paid analytics claims, or legal advice. This job is an inventory map only. For broader catalogs, use Browse more prompts. If you ship a better variant, Share a prompt.

Related PromptDig links

• Prompt: Langfuse Trace Session Map from Project Inventory (No Invented Token Totals)
• Browse: Browse more prompts
• Contribute: Share a prompt
• Home: PromptDig

Why inventory-first maps beat template swaps

Most failed handoffs start with a pretty template that assumes metrics you do not have. An inventory-first map forces the model to quote only nouns you pasted. That keeps reviewers aligned and stops silent padding.

When a teammate later fills a gap, you update one cell instead of rewriting the whole deliverable. The refuse list also trains the model to reject vanity metrics that would otherwise sneak into stakeholder decks.

Reviewer pass

Ask a second person to scan for invented numbers, tool nouns from another vendor, and missing gaps bullets. If any appear, tighten Never and rerun once. Keep the original Inventory block attached so audits stay cheap.

Privacy and safety notes

Strip personal emails, student identifiers, patient details, and payment account numbers before you paste. If regulated content appears, keep the one-line not-advice banner the prompt asks for. Do not ask the model to fabricate compliance certificates.

Final checklist

• Inventory pasted with at least two concrete rows
• Version locked or marked unknown
• Domain fields filled or UNKNOWN
• Banned and Never explicit
• Output keeps NOT IN INPUTS and a five-bullet gaps list