Purpose and audience

Separate request, approval, fulfillment and reconciliation.

Audience: The participants named at each handoff. This article describes proposed operations; the tour itself is a public-safe read-only storyboard.

Entry, authentication and boundaries

Public-safe multi-party storyboard; all operational transitions are proposed.

May access: Read-only explanation and local navigation; no operational services.

May not access: No records, accounts, notifications, payments, assignments or permission changes.

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. Need is expressed: Share only the chosen assistance barrier. Responsible: Young person. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Youth consent.
  • 2. Navigator reviews: Confirm request scope and suitability. Responsible: Navigator. Shared: Minimum need summary Approval: Assigned review.
  • 3. Eligibility is checked: Apply an approved policy. Responsible: Assistance coordinator. Shared: Necessary eligibility evidence Approval: Reviewed policy.
  • 4. Assistance is authorized: Verify funding source and independent approver. Responsible: Financial approver. Shared: Decision evidence Approval: Budget and financial authority.
  • 5. Fulfillment is approved: Separate disbursement from request and authorization. Responsible: Disbursement authority. Shared: Minimum fulfillment task Approval: Independent authorization.
  • 6. Delivery is verified: Require actual assistance evidence. Responsible: Verifier. Shared: Delivery evidence Approval: Verification policy.
  • 7. Finance reconciles: Compare authorization with actual fulfillment. Responsible: Reconciler. Shared: Permitted finance evidence Approval: Reconciliation controls.
  • 8. Safe reporting follows: Return only consented progress and suppressed aggregates. Responsible: Navigator / data steward. Shared: Minimum milestone / aggregates Approval: Youth and reporting approval.

Exceptions and notifications

If youth consent is missing or invalid, stop this step. The responsible young person would review an appropriate alternative; the prototype sends no escalation or notification.

If independent authorization is missing or invalid, stop this step. The responsible disbursement authority would review an appropriate alternative; the prototype sends no escalation or notification.

If youth and reporting approval is missing or invalid, stop this step. The responsible navigator / data 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 e · from financial need to approved assistance. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Return only consented progress and suppressed aggregates.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. No records, accounts, notifications, payments, assignments or permission changes.

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.