Explore the complete workflow
From a recording to a model delivery.
A hands-on demo of participant uploads, simulated training, administrator review, and delivery back to the participant.
- 01CollectParticipant uploads test data
- 02SimulateA worker processes the queue
- 03Review & releaseAdministrator chooses a candidate
- 04ReceiveParticipant downloads the fixture
Uploads and delivery history may reset when the container is replaced. This shared demo runs no GPU training and sends no Android push notifications.
Choose a viewpoint
One workflow.
Two sides of the experience.
Use a participant account to upload data and receive a released fixture. Use the administrator account to review uploads, run the simulator, and release a candidate.
p1001 and p1002 each have a separate participant workspace. admin manages both.
Demo password:
The administrator uses a separate private password.
Participant workspace
Your workspace
The worker is offline. New runs can be queued and will wait until the simulation worker starts.
Upload test data
01 / COLLECTChoose a plain text file for this participant.
Your uploads
0Files available in this participant workspace.
Open a file to preview its contents.
04 / Receive
Your model deliveries
Only an administrator release makes a fixture available here.
Released fixtures
Download, then explicitly report a simulated activation.
In-app inbox
In-app notificationsThis inbox stands in for future Android push notifications.
Run the training simulator
02 / SIMULATESelect active uploads above. The simulation worker will queue a run, simulate training and validation, and produce a fixture for review.
No uploads selected
Use this to observe a failed run, then start a new run with the option cleared.
Simulation runs
No GPUA successful run stops at review. It does not release automatically.
03 / Review & release
Review fixture candidates
Confirm the participant before releasing a candidate to their workspace.
Confirm recipient
This publishes the test fixture to this participant and adds an in-app notification.
Candidate fixtures
Test fixtures onlyThese artifacts are created by the simulator and have not learned from the uploaded data.
Delivery tracking
Release, download request, and participant-reported simulated activation are separate events.
Recent activity
Audit trailRecent activity across the demo accounts.