Guided Demo Follow-Up Prompts¶

This file collects thirteen follow-up prompts organized by the five flagship guided demos shipped with FCC. Each section states the prerequisite demo and then lists two or three next-step prompts that advance the learner's understanding. Every prompt pins the persona, the R.I.S.C.E.A.R. slot it targets, and the deliverable shape. All prompts assume the learner has already completed the named demo via DemoRunner or the docs walkthrough.

1. Web Frontend Demo Follow-Ups¶

Prerequisite demo. web-frontend (frontend/ React 18 + D3.js; 8 pages, 12 visualizations).

1A. Add a Persona Detail Panel¶

Personas/subsystems invoked. cw, dal. R.I.S.C.E.A.R. slot: Expected Output.

You are the Content Writer (cw). Data Analyst Lead (dal) reviews.

PREREQUISITE: you have completed the web-frontend guided demo.

TASK: Propose a new side panel on the persona catalog page that shows
the 6 Discernment traits for the selected persona as a small radar.

Include:
1. Component placement (which of the 8 pages).
2. Data source (PersonaRegistry JSON export).
3. D3 chart type and dimensions.
4. Accessibility notes (keyboard nav + data table alternative).

CONSTRAINTS:
- Only use existing API endpoints served by the backend.
- No new npm dependencies.

Deliverable: a 4-section Markdown proposal, 200 to 350 words.

Expected output notes. Real page named, no new npm deps, a11y alt present.

1B. Swap the Heatmap Color Scale¶

Personas/subsystems invoked. cw. R.I.S.C.E.A.R. slot: Style.

You are the Content Writer (cw).

PREREQUISITE: web-frontend demo completed.

TASK: Propose a colorblind-safe palette for the dimension heatmap
visualization. Produce:
1. The chosen scale (e.g., viridis) with hex codes.
2. Contrast-ratio check against white and black backgrounds.
3. A before/after mock description.

CONSTRAINTS:
- WCAG 2.1 AA contrast.
- No emojis.

Deliverable: Markdown with 3 sections, 150 to 300 words.

Expected output notes. WCAG check present; no emojis; hex codes listed.

1C. Instrument the Frontend with Tracing¶

Personas/subsystems invoked. sre, tr. R.I.S.C.E.A.R. slot: Responsibilities.

You are the Site Reliability Engineer (sre). Technical Reviewer (tr)
reviews.

PREREQUISITE: web-frontend demo completed.

TASK: Propose how page-load and interaction latency from the React
frontend can surface as spans in the FCC tracer
(src/fcc/observability/tracing.py).

Include:
1. Which events to emit from the frontend.
2. Backend ingestion endpoint and span mapping.
3. One example trace for a single page load.

CONSTRAINTS:
- Do not invent new event types; reuse from the 81 in events.py or
  propose a new enum value explicitly.

Deliverable: 3-section Markdown, 200 to 400 words.

Expected output notes. Real tracer referenced; explicit event-type proposal if new.

2. Distiller Bridge Demo Follow-Ups¶

Prerequisite demo. distiller-bridge (NanoCube query + discernment aggregation).

2A. Author a New NanoCube Query¶

Personas/subsystems invoked. dal. R.I.S.C.E.A.R. slot: Input + Expected Output.

You are the Data Analyst Lead (dal).

PREREQUISITE: distiller-bridge demo completed.

TASK: Design a new nanocube_query that cross-tabulates persona category
against the 6 Design Target Factors. Produce:
1. The query spec (dimensions, filters, aggregation).
2. Expected result shape.
3. One question it will answer that the demo did not answer.

CONSTRAINTS:
- Use only the NanoCube query primitives shown in the demo.
- No fabrication_request calls.

Deliverable: a YAML-style query block plus a 3-sentence rationale.

Expected output notes. Real query primitives; 3-sentence rationale; answers a new question.

2B. Persist Query Results as RDF¶

Personas/subsystems invoked. dal, tr. R.I.S.C.E.A.R. slot: Expected Output.

You are the Data Analyst Lead (dal). Technical Reviewer (tr) reviews.

PREREQUISITE: distiller-bridge demo completed.

TASK: Take a NanoCube result from the demo and export it as RDF by
routing through the KnowledgeGraph serializers
(src/fcc/knowledge/serializers.py).

Include:
1. Mapping of query result fields to KnowledgeGraph node types.
2. Which of the 4 serializers (OWL/RDF/SKOS/JSON-LD) to use.
3. A 10-line snippet of the resulting Turtle.

CONSTRAINTS:
- Do not add a new serializer.
- Reference real node/edge types from graph.py.

Deliverable: mapping table + serializer choice + Turtle snippet.

Expected output notes. Real node/edge types; Turtle snippet ~10 lines; no new serializer.

3. Open Science Demo Follow-Ups¶

Prerequisite demo. open-science (deterministic runs + publication pipeline).

3A. Pre-Register a Follow-Up Hypothesis¶

Personas/subsystems invoked. dal, ra. R.I.S.C.E.A.R. slot: Constraints.

You are the Data Analyst Lead (dal). Risk Analyst (ra) reviews.

PREREQUISITE: open-science demo completed.

TASK: Draft a pre-registration for a follow-up study that extends one
of the demo's findings. Include:
1. Hypothesis (single sentence).
2. Design: scenarios touched, seeds used (>= 3), personas involved.
3. Analysis plan with explicit stop rules.
4. Compute budget.

CONSTRAINTS:
- Deterministic simulation mode only.
- No hosted AI providers in the plan.

Deliverable: 4-section Markdown, 300 to 500 words.

Expected output notes. 3+ seeds, deterministic only, compute budget given.

3B. Publish Results via Quarto¶

Personas/subsystems invoked. cw. R.I.S.C.E.A.R. slot: Expected Output.

You are the Content Writer (cw).

PREREQUISITE: open-science demo completed.

TASK: Produce a one-chapter Quarto source that reports the demo's
findings in the academic profile. File will live under
publications/ and be included in _quarto-academic.yml.

Include:
1. Abstract (<= 150 words).
2. Methods (<= 200 words).
3. Results (tables + one figure).
4. Discussion with limitations.

CONSTRAINTS:
- Use `make pub-all` conventions; do not invent new build steps.
- No emojis.

Deliverable: a .qmd body, 400 to 700 words.

Expected output notes. Fits academic profile; no emojis; build-step compatible.

3C. Reproduce with a Different Seed¶

Personas/subsystems invoked. tr, dal. R.I.S.C.E.A.R. slot: Constraints.

You are the Technical Reviewer (tr). Data Analyst Lead (dal) reviews.

PREREQUISITE: open-science demo completed.

TASK: Describe the exact steps to reproduce the demo's primary result
with seeds {42, 123, 456}. Produce:
1. Shell commands.
2. Expected output hash or numeric match tolerance.
3. How deviation is surfaced if it occurs.

CONSTRAINTS:
- Reproduction must complete in under 10 minutes on a laptop.
- Mock provider only.

Deliverable: a 3-section Markdown runbook.

Expected output notes. Mock provider only; three seeds enumerated; timing budget stated.

4. SkyParlour Demo Follow-Ups¶

Prerequisite demo. sky-parlour (web + protocols + streaming visualization).

Personas/subsystems invoked. sre, cw. R.I.S.C.E.A.R. slot: Expected Output.

You are the Site Reliability Engineer (sre). Content Writer (cw)
reviews.

PREREQUISITE: sky-parlour demo completed.

TASK: Propose an events-per-second sparkline on the SkyParlour
dashboard that subscribes via websockets to EventBus events.

Include:
1. Event type filter (pick from the 81).
2. Sampling window and smoothing.
3. Performance budget (render time, memory).

CONSTRAINTS:
- No new npm deps.
- Must degrade gracefully when the stream stalls.

Deliverable: 3-section Markdown, 200 to 350 words.

Expected output notes. Real event types; graceful degradation path; performance budget.

4B. Harden the Protocol Bridge¶

Personas/subsystems invoked. sre, tr. R.I.S.C.E.A.R. slot: Constraints.

You are the Site Reliability Engineer (sre). Technical Reviewer (tr)
reviews.

PREREQUISITE: sky-parlour demo completed.

TASK: Produce a 5-item hardening checklist for the ws-bridge command
(fcc protocol ws-bridge) in a multi-user deployment.

Cover:
1. Connection caps.
2. Auth (opt-in).
3. Back-pressure strategy.
4. Health endpoint semantics (already on the same port).
5. Clean shutdown.

CONSTRAINTS:
- Do not require Kubernetes; chart is optional.

Deliverable: a 5-row table plus a 2-paragraph summary.

Expected output notes. 5 rows; K8s optional; real CLI command referenced.

5. Full-Stack Ecosystem Demo Follow-Ups¶

Prerequisite demo. full-stack-ecosystem (cross-project plugin + vocabulary providers + federation).

5A. Add a Second Vocabulary Provider¶