Skip to content

tldr prompt: ban active-orgs ratio in weekly report TL;DR#58

Open
Assaf Hay Eden (AssafHayEden) wants to merge 3 commits into
mainfrom
aheden/tldr-ban-active-orgs-ratio
Open

tldr prompt: ban active-orgs ratio in weekly report TL;DR#58
Assaf Hay Eden (AssafHayEden) wants to merge 3 commits into
mainfrom
aheden/tldr-ban-active-orgs-ratio

Conversation

@AssafHayEden
Copy link
Copy Markdown
Collaborator

Summary

Manager feedback on the first TL;DR run: "(now 15/18 active)" reads as a state metric, not a movement, and dilutes the actual headline.

The original prompt actively encouraged this — the big-news "Good" example literally taught the model to write "pushing Studio to 14 of 16 contract orgs active". This PR fixes that.

Changes to agents/reports/ltx-leadership-weekly-report/n8n/tldr_system_prompt.md:

  • New BANNED METRICS block under SELECTION RULES, banning:
    • Active-orgs ratio ("15/18 active", "14 of 16 contract orgs active")
    • Total contract count on its own
    • "Was X%" baselines without their own delta
  • New STYLE rule: "Prefer movement language ('signed', 'launched', 'broke out') over state language ('now X of Y'). Static ratios belong in the body, not the TL;DR."
  • Removed the offending phrase from the big-news Good example
  • Added an explicit Bad example showing the active-orgs anti-pattern
  • Changelog bumped

The body (render_body.js) still surfaces active orgs as a bullet — that's where state metrics belong. Only the TL;DR is constrained.

Test plan

  • Re-run the n8n workflow against the same week's data and confirm the regenerated TL;DR no longer surfaces the active-orgs ratio
  • Spot-check that contract org names still appear when there's a real transition (new contract signed, going inactive, ending)
  • If output drifts from the locked Reference TL;DR (week of Apr 27 → May 3) on the same input, investigate before merge

Made with Cursor

Manager feedback: "(now 15/18 active)" reads as state, not movement, and
distracts from the actual headline. Remove it from the prompt's good
example, add an explicit BANNED METRICS section, add a Bad example
showing the anti-pattern, and add a STYLE rule preferring movement
language over state language.
…add Enterprise Dashboard link

Restructures the weekly leadership Slack post so each lead is counted exactly
once across the three sections, and surfaces the Hex Enterprise Dashboard as
a deep-link from the Studio Enterprise section.

Bucketing rule (locked):
  OSS    = OSS PEL only (no PQL flow)
  API    = (API + Both) PQL and (API + Both) PEL
  Studio = Studio-only PQL and Studio-only PEL

SQL: new marketing_pels_by_product CTE on marketing.final_sf_lead_opportunity
  (lead-level, deduped) classifies PELs as API / Studio / Both / OSS via the
  ltx_api / ltx_studio flags. Surfaced as J_studio_summary.wow_trends.pels_by_product.
  Dry-run cost: 545 MB (was 537 MB).

render_body.js: drives the new bucketing off pqls_by_product and pels_by_product.
  The legacy Block G (G_pql_pel) is still emitted by the SQL but no longer
  rendered so all three sections share one source of truth. Adds a
  STUDIO_DASHBOARDS array with the Hex Enterprise Dashboard URL; the line is
  omitted when the array is empty.

tldr_system_prompt.md: extends the PEL-skip rule to all three PEL lines and
  calls out the OSS PEL bucket as especially noisy (sensitive to product-flag
  tagging gaps), so the LLM does not headline OSS PEL swings.

Verified end-to-end: PEL totals reconcile (388 OSS + 51 API+Both + 294 Studio
= 733, matches the lead-level table).

Co-authored-by: Cursor <cursoragent@cursor.com>
…rt-leads-regroup-and-dashboards

leadership-report: split PQL/PEL into OSS / API / Studio buckets and add Enterprise Dashboard link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants