Beacon Labs community support demo kit

Beacon Labs, its SDKs, package names and policies are fictional teaching data.
Do not install the example packages. No credentials or provider receipts are included.

Use the accompanying tutorial for the complete numbered setup:
https://quickchat.ai/post/discord-community-management-bot

1. Create a dedicated demo Agent. Add the five knowledge/*.md files as individual
   Knowledge Base articles and wait for Ready.
2. Paste main-prompt.txt into Identity > Main Prompt.
3. Follow sheets-recipe.md to authorize Google, create two tabs, and configure the
   Actions. Files ending in -headers.tsv are spreadsheet headers, not HTTP headers.
4. Follow discord-setup.md to connect the shared bot and test real member delivery.
5. Follow handoff-setup.md. Use handoff-confirmation.txt for the Confirmation field.
6. Use simulation-messages.txt and simulation-rubric.txt for independent questions.
   test-cases.json has thirteen prepared sequences and desired outcomes, not a set
   of successful results. Complete feedback submissions are recorded immediately
   for team review. If details are missing, send a complete restatement. Inspect
   calls and rows after every turn; a Discord Reply can start a different Inbox
   conversation. Active Actions can write during testing. The failure case uses a
   verified missing tab to produce a real Google error; restore the exact URL.
7. source-update-addendum.md is an optional temporary source update for the negative
   test. Do not include it in the initial Knowledge Base; remove it again afterward.

This recipe uses AI-decided Actions. It records a complete explicit
submission without a second approval step. Intent selection, documentation-gap
selection and acknowledgment handling remain model behavior. Repeated complete
submissions can create duplicate rows. The team reviews feedback and candidate
knowledge gaps and handles corrections or withdrawals of saved rows.

Remove sensitive details before posting; do not rely on model redaction. The
tutorial's fictional-secret probe showed that a reply can omit a marker while the
saved row retains it. Inspect the actual spreadsheet cells as well as the reply.
Required fields use No default.

The JSON bodies use platform placeholders; select the Google token through the
editor's Add AI Data > System Tokens menu. Copy the spreadsheet endpoint created by
the native connection and replace only its range/query suffix as documented.

SHA256.json lists the packaged source-file hashes. These files are editable recipes,
not a one-click import.
