How CovCare Works — Role-Based Guided Tours

How CovCare works.

Every participant has a different path. Each proposed handoff has a decision-maker, a purpose and a privacy boundary.

Choose an audience or workflow

Multi-party concept workflow

F · Impact Circle Lifecycle

A shared purpose can start with one person; participation does not confer authority.

Tour steps

Entry & authentication

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

Access boundary

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

Unavailable: No records, accounts, notifications, payments, assignments or permission changes.

F · Impact Circle LifecycleProposed / fictional storyboard

STEP 1 OF 8

Purpose is proposed

Define a fictional circle purpose.

What the participant sees

Multi-party storyboard: purpose is proposed. This is not an operational queue.

What happens next

Continue to chi reviews circle after the stated approval.

Decision owner: Organizer

Information shared

Purpose only

Approval required

No size or donation minimum

If something goes wrong

If no size or donation minimum is missing or invalid, stop this step. The responsible organizer would review an appropriate alternative; the prototype sends no escalation or notification.

Actual current functionality

These controls navigate public documentation only. Operational review, notification, assignment, finance and service fulfillment are not activated. Existing public practice remains separate. This step describes intended design, not a completed operational task.

1/8

Read the detailed guide Open temporary full demo

Related formal specifications

Service blueprints ↗