See the flows run — front end and back end, side by side.
A working walkthrough of how JobCare fills a case. Each portal below is a real interface with a live backend console showing every API call, database write, match step, and message the platform fires. It runs on 300 realistic (fake) candidates, and is the seed of the production app.
Choose a portal
Post cases and run candidate outreach, manage open cases, and — for admins — profile, staff, bench, billing & policy.
For home-care workers: profile & availability, job matches, messages, check-ins, training, reputation and referrals.
For households hiring directly: employer sign-up, care-recipient profiles, post a care request → matches, browse & rate aides.
The JobCare staff view: revenue & AR, the case pipeline, monthly billing, agency scorecards, integrity & compliance.
The specs behind the app, linked so you can move between the map and the live flows:System Map (who does what, by actor) andFlow Atlas (the B-flow sequence diagrams). Each System-Map capability marked ▶ is playable here in the Explorer.
First release: 45 of 58 capabilities are in v1; every capability caption in the app carries its tag —v1 in the first release, later deferred behind a named trigger (hover to read it), cut replaced or dropped. The tag is written once, in the requirements doc, and rendered here and on the System Map.
Where this runs: Movingthis demo moves into JobCare's non-production cloud account on the new stack, and the Explorer is kept there afterwards as the planning tool. The real product gets its own demo, apart from staging and on the demo image built from the same commit as production, with every outside provider replaced by a mock that answers with simulated replies, where the prospect logins JobCare creates, each in a pre-seeded demo agency of its own, persist across the nightly reset while everything else returns to the seed (ADR-0020). The real product is held to two measured objectives, the screens answering from outside 99.5 percent of a month and no text sent after a revocation took effect, and the operator queue is the page JobCare's operator reads (ADR-0021). It is proven by two kinds of test: safety tests, which block a merge, and correctness tests, which are the evidence its reviewer reads, while five browser journeys run nightly in staging and block nothing (ADR-0022). The aide is reached by a text and a web app that opens from its link and can be added to the home screen; the consent wording and the texts go out in Spanish at launch for an aide who chooses it, while the screens stay English (ADR-0023).
How the work moves: one short branch per story, squash-merged by JobCare's reviewer; theStoriespage is the tracker, with the next list at the top and each story's state (ADR-0024).