docs(plan): recipe links on the MCP surface and a Grafana stack #27

Merged
TimCane merged 1 commit from docs/plan-recipe-links-and-grafana into main 2026-07-21 22:40:37 +01:00
TimCane commented 2026-07-21 22:06:00 +01:00 (Migrated from github.com)

Summary

  • replaces the completed usage-audit plan with the next two workstreams
  • recipe links: website_url is already in v_recipe and populated by both sources, but only get_recipe returns it - it moves onto RecipeSummary so search results carry a citable link
  • the cite-the-source rule lands in ServerInstructions as well as tool descriptions and prompts: instructions are the only channel every agent sees, prompts only fire when a user invokes one
  • never construct a URL from a slug or id - a guessed link is a broken link with the source's name on it
  • Grafana: ten dashboards over the audit, scrape and public views, provisioned from grafana/ at container start rather than built in the UI
  • a dedicated read-only role scoped to public views, audit and scrape, so a new source still needs no grant of its own

Test plan

  • plan only, no code - verification lands with each workstream
## Summary - replaces the completed usage-audit plan with the next two workstreams - recipe links: `website_url` is already in `v_recipe` and populated by both sources, but only `get_recipe` returns it - it moves onto `RecipeSummary` so search results carry a citable link - the cite-the-source rule lands in `ServerInstructions` as well as tool descriptions and prompts: instructions are the only channel every agent sees, prompts only fire when a user invokes one - never construct a URL from a slug or id - a guessed link is a broken link with the source's name on it - Grafana: ten dashboards over the audit, scrape and public views, provisioned from `grafana/` at container start rather than built in the UI - a dedicated read-only role scoped to public views, audit and scrape, so a new source still needs no grant of its own ## Test plan - [ ] plan only, no code - verification lands with each workstream
Sign in to join this conversation.
No description provided.