Skip to main content

​
IDs, Crosswalks, and Bounded Windows

Most integration mistakes happen before the deep call, not during it. The safest pattern is to preserve provider refs exactly as they came back from the server and to keep every schedule-style request bounded in time.

​
Preserve the provider namespace

Start with resolve_entities.What to keep from the response:
  • gsdRefs for GSD-first tools
  • onRefs for program-context and current-state-aware tools when the provider exposed them
  • programHints for program-first follow-ons
  • meta.crosswalkConfidence before enriching across providers
Best next step:
  • choose one candidate
  • preserve the chosen ref with its provider namespace
  • call the smallest next tool that matches the job

​
Treat crosswalk confidence as a workflow signal

​
Keep schedule-like flows bounded

Bounded windows are required for: Bounded windows are optional, but must be paired when provided, for: Special case:
  • get_series_hub can omit the window. When omitted, it uses a bounded default window rather than an unbounded browse.
Why this matters:
  • it keeps fanout bounded
  • it keeps live and watchability answers scoped to a real product moment
  • it prevents the host from turning one prompt into an unbounded browse workload

​
Typical handoff pattern

  1. Resolve only if the user prompt is ambiguous.
  2. Pick one provider ref and preserve the namespace.
  3. Add timeFrom and timeTo when the workflow is schedule-like or watchability-like.
  4. Deepen only if the user still needs more context.

​
Read this next