Skip to main content

Using the app (first report)

Who this is for​

This page is for people who want to use VibeSwitch in the browser: read today’s assessment, understand what moved the score, and contribute evidence—without touching code.

Getting into the app​

  1. Open the VibeSwitch link your organization uses.
  2. If you see a sign-in prompt, sign in with the Google account your operator approved.

You should land on the Report tab.

Reading today’s assessment​

The report is designed to be readable in two passes:

  1. Fast scan (1–2 minutes)
  • Read the top summary.
  • Look for the 2–3 biggest component movements.
  1. Proof mode (5 minutes)
  • For any surprising score, open the evidence under that component.
  • Ask: “What changed in the evidence compared to yesterday?”

If you can quickly point to the top evidence items behind a score, the system is behaving correctly.

Asking follow-up questions (chat)​

After the report loads, you can ask questions like:

  • “Why did community cohesion drop?”
  • “Which municipalities reported disruptions today?”
  • “What evidence supports the highest risk component?”

Good questions are specific. VibeSwitch should answer using evidence already present (and say “I don’t know” when it can’t support a claim).

Submitting your own evidence​

At the top of the page there’s an evidence submission bar.

  • Paste a link, a quote, or a short observation.
  • Click Submit.
  • Confirm it appears in the Submissions tab.

Your submission should be incorporated on the next assessment run.

Other tabs you’ll use​

  • Submissions: your manual inputs and status
  • Education: education disruption/participation signals
  • Municipalities: municipality-by-municipality status, backed by evidence
  • Naftali: tracked activity stream

Troubleshooting​

  • I see “No assessment is available yet”
    • What it usually means: today’s ingestion/analysis didn’t run.
    • What to do: ask your operator to run the daily pipeline for today (see Operate the daily pipeline).
  • The report date is old (yellow banner)
    • What it usually means: you’re looking at the last successful cached run.
    • What to do: have today’s pipeline run, then refresh.
  • I’m stuck in a sign-in loop / “Unauthorized”
    • What it usually means: your account isn’t authorized for this instance.
    • What to do: ask your operator to authorize your account or verify auth config (see Auth setup).
  • A score looks wrong
    • What it usually means: evidence changed (or is too thin).
    • What to do: open the evidence items under that component; if evidence is thin, add/ingest more. If evidence is strong but scoring seems off, flag it to the operator and include the evidence links.