demo-componentslisted

# Demo Components Use live documentation and advance only as far as the user's request requires. Reuse content already fetched during the session. ## Discover components 1. Fetch `https://f5-sales-demo.github.io/demo-resources/llms.txt` with an available HTTP or fetch tool. 2. Read the component entries and their descriptions. Treat the returned catalog as authoritative. 3. Present only components that appear in the catalog. Recommend the smallest combination that meets the demo goal and link to the relevant catalog entries. 4. Ask the user to select a component when their requirements do not determine one. Common combinations include: - WAF, API security, or bot defense: an origin server plus a traffic generator. - CDN behavior: an origin server plus a CDN simulator. - Client-side defense: an origin server, with a traffic generator only when the scenario needs it. ## Inspect a component After validating the component slug against the live catalog, fetch its profile from: `https://f5-sales-demo.github.io/demo-resources/_llms-txt/en/{component}.txt` Summarize its purpose, architecture, installed software, inputs, outputs, integration points, and compatible components. Do not infer capabilities missing from the live profile. ## Prepare a deployment When the user wants deployment details, fetch: `https://f5-sales-demo.github.io/{component}/_llms-txt/en/03-deploy.txt` Then: 1. Confirm the target is an authorized demo or lab environment. 2. Follow the live guid