Demo Samples

Prepare for the Monday billing RFC sync with Elena by gathering a cross-system readiness picture (code quality of the PLAT project, GPU capacity from Grafana, affected-account status in Salesforce), then grant Fiona Walsh access to the Product Notion space so she can review the GPU-quota meeting notes, update the DocuSearch AI Salesforce account to reflect the GPU-quota risk, log the prep activity against that account, and find a slot to reschedule the sync if the calendar conflicts.

I want to make sure I’m prepped before my billing RFC sync with Elena on Monday… [readiness checks, then grant Fiona access, flag the GPU risk on the account, log the prep, check my calendar].

sonarqube__get_quality_gate({"project": "PLAT"})
notion__search_docs({"query": "GPU quota meeting notes", "space": "Product"})
salesforce__search_records({"query": "DocuSearch AI", "object_type": "Account"})

So far: PLAT’s SonarQube gate is passing (0 bugs / 0 vulns / 0 smells) but coverage is 0.0%, so the readiness signal is weak. I found the Product Notion page Fiona needs, and the DocuSearch AI account.

notion__add_space_member({"space_key": "Product", "user": "Fiona Walsh"})
grafana__search_dashboards({"query": "GPU Cluster Health"})
grafana__get_dashboard({"uid": "f8a59a48ebaf"})

salesforce__add_note({"parent_id": "001CAF4D19FBA0F",
  "title": "GPU quota risk flagged before customer outreach", "body": "Flagging the 30% …"})

Done — Fiona has Product Notion access, and I flagged the quota risk on the DocuSearch AI account with the billing/GPU context.

google_calendar__search_events({"query": "billing RFC sync Elena"})
google_calendar__list_events({"time_min": "2024-01-08T13:00:00Z", "time_max": "2024-01-08T13:30:00Z"})

Not yet — I added the note but haven’t logged a separate activity record. On the calendar I see only the Monday 13:00–13:30 UTC sync, no conflict.

salesforce__log_activity({"what_id": "001CAF4D19FBA0F",
  "subject": "Pre-outreach prep review completed for billing/GPU quota risk", "description": "…"})

All set — prep activity logged on the DocuSearch AI account, and the Monday sync is conflict-free.

What’s the current state of the batch-inference-v2 feature flag? Has it actually been enabled or configured for any users, or was it just created and left in a default-off state?

The flag batch-inference-v2 is effectively disabled — created by System but never enabled or configured with rollout targeting, so the feature is unreachable for all users until targeting rules or an explicit enable are applied.

You are an enterprise operations analyst with read-only access to the company’s internal systems… Ground every claim in tool results; cite the source records (IDs/keys) you relied on. If the evidence is insufficient, say so rather than guess.

What’s the current state of the batch-inference-v2 feature flag? …

launchdarkly__get_flag({"flag_key": "batch-inference-v2"})

{"flag_key": "batch-inference-v2", "kind": "boolean",
 "environments_json": {"production": {"on": false}, "staging": {"on": false}},
 "created_by": "System", "created": "2026-05-23 05:08:02", "modified": "2026-05-23 05:08:02"}

launchdarkly__list_audit_log({"flag_key": "batch-inference-v2", "limit": 50})

The batch-inference-v2 flag was created and left in a default-off state. Both production and staging show on: false; the audit log has a single create action by System on 2026-05-23 with no subsequent toggle or config change (created and modified timestamps are identical).