Interactive fictional workflow

Turn evidence into
an owned decision—
without surveillance.

Open a fictional learner record, inspect the reason and rubric, and simulate a disposition. Every row and number is invented for workflow testing; nothing here is a result or claim about a real person.

Work the demo queue Read the facilitator guide

Demonstration data only. Simulated actions change this browser view only. They do not write learner data or count as program evidence.

Demo records12fictional learners
Projects submitted7/12current-week state
Review queue8ready or revision
Guided work94%assigned lessons complete
Support signals4categories, not diagnoses
Facilitator work queue

One record.
One owned next action.

The queue is ordered for action, not prediction. Select any row to inspect the minimum evidence needed for an authorized person to follow program procedure.

Show
Demo IDRouteGuided workProjectReviewSupportLast activeOwned next action
Week 521/22readyTodayReview job pipeline
Week 416/17draftrevisionscheduleYesterdayFinish career evidence
Week 522/22readyTodayIndependent rubric review
Week 310/12missingnoneaccess4 daysAccess check-in
Week 519/22draftwaiting2 daysComplete two lessons
Week 27/7revisionreferral6 daysFollow referral protocol
Week 522/22readyTodayPrepare AI workflow
Week 414/17missingnoneschedule3 daysReschedule work session
Week 520/22waitingYesterdayFacilitator feedback
Week 312/12ready2 daysBegin target-role scan
Week 417/17draftrevisionTodayRevise proof statements
Week 522/22readyTodayReview interview stories

Showing 12 of 12 fictional records.

Selected record · P-101

Job-search command center

ready
Recommended actionReview the pipeline before adding applications

The project is present and activity is high, but every open opportunity needs a dated next action.

Evidence state
C13/4C23/4C34/4C43/4

Support: no open category. Last active: Today.

In production, a disposition would store reviewer identity, timestamp, criterion ratings, feedback, ruleset/version, and any override reason.
Optional group session record

Record what happened.
Do not rewrite activity as success.

The staff workspace can record duration, group size, attendance, delivered activities, adaptations, technical issues, and non-identifying support categories for each supported week.

01

Delivery

  • Date, mode, minutes, staff
  • Group and attendance counts
  • Activities delivered or omitted
02

Variation

  • Planned adaptations
  • Technical failures and recovery
  • Access barriers by category
03

Action

  • Review backlog and ownership
  • Misconceptions across the group
  • Next product improvement
Operational safeguards

Signals need a protocol
and an accountable person.

Access

Only authorized staff roles see identifiable learner records. Public activity totals use privacy-protective suppression and aggregation.

Support

Access, schedule, or referral categories start a human check-in. They do not diagnose a condition or automatically remove a learner.

Project review

Published rubrics, reviewer preparation, timestamps, revision decisions, and specific feedback make the process auditable.

Exports

Organizations receive only fields required for approved support through a documented, time-limited process.