Datasets:
Droid traces preview
Thu, May 21
Do not use tools. Based only on the excerpts pasted below, produce a medium-length procurement renewal risk memo with renewal deadline math, missing exhibits, cost exposure, negotiation asks, and a final go/no-go recommendation.
CONTRACT EXCERPT:
Vendor Agreement Extract
Section 2. Term. Initial term ends 2026-08-31. Agreement renews automatically for successive one-year terms unless either party gives written notice at least 60 days before the end of the then-current term.
Section 4. Fees. Annual subscription fee is $144,000, paid upfront. Usage above 50 million events per month is billed at $0.45 per thousand events. Vendor may increase subscription fees by up to 7% at each renewal.
Section 6. Support. Premium support response targets are P1 within 2 hours, P2 within 8 business hours, P3 within 2 business days. Targets are not service credits.
Section 9. Data. Customer data may be processed in the United States and European Union. Vendor deletes customer data within 45 days of written termination request, except backups retained up to 180 days.
Missing exhibits: Exhibit B Security Controls, Exhibit D DPA, and uptime SLA appendix were referenced but not included.
VENDOR PACKET PDF TEXT EXCERPT:
%PDF-pretend fixture for Droid trace generation
Title: Vendor Packet Summary
Page 1: Contract renewal risk includes automatic renewal, 7 percent uplift, and missing DPA.
Page 2: Security review says penetration retest evidence is absent.
Page 3: Finance asks for a 12 month cost scenario at current event growth. 1
message Read images/revenue_dashboard.svg only. Do not inspect images/tiny_chart.png and do not run image conversion tools. Write outputs/medium/08-image-alt-text-and-data.md with accessible alt text, visible data points, and uncertainty notes. Final answer under 5 bullets. 1
message 5
tools Read images/revenue_dashboard.svg as SVG source only. Do not convert or render images. Write outputs/medium/07-dashboard-screenshot-critique.md with 5 concrete dashboard improvements and 3 misleading-metric risks inferred from the SVG text/shapes. Final answer: output path and one sentence. 1
message 6
tools Read data/support_tickets.csv and notes/customer_feedback.md directly. Do not use the Skill tool and do not run shell commands. Write outputs/medium/04-support-macro-cluster.md with 3 ticket clusters, 2 support macros, and 1 product escalation. Final answer under 6 bullets. 1
message 7
tools Read notes/competitors.md and notes/customer_feedback.md. Write outputs/medium/10-competitive-positioning.md with a positioning memo: target buyer, differentiators, proof points, weaknesses, and three website copy bullets. 1
message 15
tools Analyze logs/incidents.log alongside data/support_tickets.csv. Write outputs/medium/09-incident-root-cause.md with a concise incident timeline, likely root causes, customer impact, and prevention work. Include at least one cross-reference between a log line and a ticket. 1
message 11
tools Use the cfo-review skill. Compare data/vendor_scores.csv with docs/security_report.txt. Write outputs/medium/06-vendor-selection.md recommending one vendor for a regulated enterprise buyer. Include total cost, implementation risk, compliance fit, and what evidence is still missing. 1
message 12
tools Read data/sales_pipeline.csv and notes/competitors.md. Calculate probability-weighted pipeline by close month and segment, identify the three riskiest high-value deals, and write outputs/medium/05-sales-pipeline-forecast.md. Include a final recommendation for where leadership should intervene this week. 1
message 8
tools Use the cfo-review skill. Analyze data/cloud_spend.csv and identify the best 30-day cloud spend reduction plan that preserves reliability. Write outputs/medium/01-cfo-cloud-spend.md with: top 3 savings moves, dollar estimate, operational risk, owner, and one next data request. Keep the final response under 8 bullets. 1
message 5
tools Use the security-review skill. Review code/auth_diff.patch for security regressions. Write outputs/medium/03-security-diff-review.md with only actionable findings, exploit scenario, affected asset, severity, and a minimal remediation. If a finding is speculative, exclude it. 1
message 11
tools 
- Downloads last month
- 200