Purpose and audience

Explore support on a shared device without retaining another visitor’s identity.

Audience: Community Kiosk Visitor. This article describes proposed operations; the tour itself is a public-safe read-only storyboard.

Entry, authentication and boundaries

Fictional Connect kiosk; no live fleet is deployed.

May access: Anonymous discovery, language options and accessibility controls.

May not access: Previous visitor content, staff records and guaranteed human connection.

Step-by-step workflow

The 8-step guided tour is navigable with visible controls, keyboard arrows and horizontal touch swipes. These controls only change the explanation shown.

  • 1. Start a clean visit: Confirm the device is at an anonymous starting point. Responsible: Visitor / device steward. Shared: None Approval: Approved shared-device configuration.
  • 2. Choose language: Select one of five languages; machine-assisted text needs review. Responsible: Visitor. Shared: Language preference Approval: No account required.
  • 3. Adjust accessibility: Use text, contrast or reduced-motion options. Responsible: Visitor. Shared: Display preference Approval: No compliance guarantee.
  • 4. Explore a need: Browse without identity or sensitive input. Responsible: Visitor. Shared: Resource category Approval: Anonymous access.
  • 5. Choose an option: Read that responder and service demonstrations are simulated. Responsible: Visitor. Shared: Optional temporary choice Approval: No live connection.
  • 6. Enter optional practice: Use fictional goals only after explicit entry. Responsible: Visitor. Shared: Local-memory practice Approval: Explicit practice entry.
  • 7. Recognize expiry: Kiosk inactivity clears personal content at sixty seconds. Responsible: Device session controls. Shared: No retained temporary personal text Approval: No extend for kiosk personal content.
  • 8. Exit for the next visitor: Clear the session and return to anonymous discovery. Responsible: Visitor / device steward. Shared: None Approval: Shared-device exit boundary.

Exceptions and notifications

If approved shared-device configuration is missing or invalid, stop this step. The responsible visitor / device steward would review an appropriate alternative; the prototype sends no escalation or notification.

If no live connection is missing or invalid, stop this step. The responsible visitor would review an appropriate alternative; the prototype sends no escalation or notification.

If shared-device exit boundary is missing or invalid, stop this step. The responsible visitor / device steward would review an appropriate alternative; the prototype sends no escalation or notification.

No notification, application, invitation or escalation is sent by this public tour. Future communication needs approved services, consent and appropriate safeguarding.

Example and expected result

Use fictional Alex’s GED/employment journey or a fictional supporter project to follow community kiosk visitor. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Clear the session and return to anonymous discovery.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Previous visitor content, staff records and guaranteed human connection.

Storyboard progress is a URL coordinate, not an operational record. Proposed service evidence, finance reconciliation and youth goal updates require separate approved systems. Youth retain final control of goal completion.

Current status and future dependencies

Tour controls: local prototype. Operational steps: Planned unless the step explicitly describes an existing public demonstration. Account activation, live coordination, payments and assignments remain Blocked pending reviews.

Prerequisites include verified CHI authority, appropriate consent, scoped permissions, MFA for staff, safeguarding/finance review, recovery readiness and a separately approved implementation/test package.