Skip to content

Add guide: analyze allocations with the AI Assistant#178

Open
simozzy wants to merge 2 commits into
mainfrom
docs/allocation-cost-trace-guide
Open

Add guide: analyze allocations with the AI Assistant#178
simozzy wants to merge 2 commits into
mainfrom
docs/allocation-cost-trace-guide

Conversation

@simozzy

@simozzy simozzy commented Jun 11, 2026

Copy link
Copy Markdown
Member

What

Adds the missing customer guide for the AI Assistant's allocation cost-trace capabilities, under guides/allocations/results/. These are user-driven (you ask the assistant in plain English) but weren't documented anywhere.

New page: Analyze Allocations With the AI Assistant — covers:

  • Why an allocation changed — root cause (size, what drove it, top contributors).
  • Slice drill-down — separating "the pool moved" from "the slice's share moved".
  • Lineage both directions — where values come from / what a table feeds (all branches).
  • What drives an allocation — driver vs input usage.
  • What-if — forward estimates, framed as an upper bound.
  • Discovery — what allocations exist.

It documents the clean vs partial answer model (incl. that filtered allocations now resolve clean) and the two honest limitations as callouts: dimension allocations (precise "why" needs point-in-time hierarchy history — a later release) and cascaded allocations (scope to a slice). Cross-linked from the existing Allocation Results page.

Notes

  • Built locally with npm run build1459 pages, no errors.
  • Matches the existing using-ai-assistant.mdx pattern (frontmatter, <Aside> import/usage, spaced em dashes, Title Case headings).
  • Reflects behaviour shipped in plaid #6223 / #6224 / #6226 / #6227 (clean global on filtered allocations; honest partial on dimension allocations; full lineage fan-out).

Document the AI Assistant's allocation cost-trace capabilities — explain
why an allocation changed (root cause + slice drill-down), trace lineage
both directions, see what drives an allocation, and run what-if
estimates — with the clean/partial answer model and the dimension /
cascade limitations. Cross-linked from the allocation results page.
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 11, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
plaidcloud-docs 30bea23 Commit Preview URL

Branch Preview URL
Jun 11 2026, 02:50 AM

The capabilities are MCP tools driven from an external AI agent (Claude
Code/Desktop, Cursor, ChatGPT, etc.) connected to the workspace MCP
server - not the in-product AI Assistant tab. Retitle to 'Analyze
Allocations With an AI Agent', add a note pointing to the Connect an AI
Coding Agent setup tutorial, and link there from Next Steps.
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.

1 participant