CHI Navigator

Concept prototype. Do not submit sensitive information. Planned instructions describe intended design, not an activated service.

Content owner: Program content reviewer (proposed; CHI assignment pending)
Review: Source-reviewed documentation; organizational and professional validation pending.
History: V5.8: public reference foundation · V6.0: enterprise specifications and linked registers

Purpose and audience

Coordinate approved support while preserving youth control.

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

Entry, authentication and boundaries

Proposed verified staff entry; public storyboard is not staff access.

May access: Only assigned, consented support tasks after provisioning.

May not access: Unassigned youth, private reflections, donor financial detail or broad clinical records.

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. Verify staff access: Establish verified provisioning and MFA before work. Responsible: CHI provisioning authority. Shared: Verified staff identity Approval: Trust permission, MFA and launch review.
2. Receive assignment: Accept only a scoped, approved request. Responsible: Central coordinator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Current youth consent and approved assigned scope.
3. Confirm youth wishes: Check what the youth wants shared and which goal matters. Responsible: Navigator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Current youth consent and approved assigned scope.
4. Review the barrier: Assess a transport or technology barrier without imposing goals. Responsible: Navigator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Assigned task and safeguarding policy.
5. Coordinate specialist: Request relevant education or career review. Responsible: Navigator. Shared: Only the explicitly selected goal or minimum necessary task summary; never private reflections. Approval: Approved referral and specialist scope.
6. Request partner review: Seek vetted support through Central, not direct unapproved contact. Responsible: Central coordinator. Shared: De-identified need until authorized Approval: Current youth consent and approved assigned scope.
7. Follow up: Review proposed fulfillment evidence; youth can contest inaccurate progress. Responsible: Navigator. Shared: Task evidence only Approval: Approved verification policy.
8. Close with youth: Offer a progress update; youth decides goal completion. Responsible: Young person and navigator. Shared: Consented goal milestone Approval: Youth approval and retention policy.

Exceptions and notifications

If trust permission, mfa and launch review is missing or invalid, stop this step. The responsible chi provisioning authority would review an appropriate alternative; the prototype sends no escalation or notification.

If approved referral and specialist scope is missing or invalid, stop this step. The responsible navigator would review an appropriate alternative; the prototype sends no escalation or notification.

If youth approval and retention policy is missing or invalid, stop this step. The responsible young person and navigator 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 chi navigator. The expected result today is understanding who acts, what is shared and where approval is required—not a saved record or fulfilled service.

Offer a progress update; youth decides goal completion.

Privacy and progress

Do not enter sensitive youth, clinical, donor or organizational information. Unassigned youth, private reflections, donor financial detail or broad clinical records.

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.