Recovery workflow
Turn experience into a direction to test and a bounded seven-day plan.
Describe your starting point
Enter your experience, priorities, practical constraints and available weekly time. Start small: a few specific achievements are more useful than a long list of general skills. Recovery supports up to 15 achievement claims, three source excerpts and three job targets per session.
Review what your claims support
In the Angular app, attach exact quotations from pasted résumé or project-note excerpts. Confirm, reject or leave each achievement unverified. A quotation identifies a source; your confirmation records your review, not independent verification.
Correcting a claim records its history, resets confirmation and revokes dependent requirement links. Only confirmed claims can support manual job-requirement links or enter optional recovery AI review.
Read the evidence rules ↗ and job-requirement guide ↗ for exact behavior.
Choose a hypothesis
- Return: explore similar work to what you have done.
- Shift: explore a different kind of work using transferable evidence.
- Bridge: explore a stepping-stone role or a smaller deliverable.
Review the assumptions and unknowns before choosing. These routes describe possibilities to test, not employability scores or hiring predictions.
Try a manageable next action
Generate a seven-day plan bounded by your stated available hours. Complete an action, record what happened and revisit the direction if the evidence changes. You choose which opportunities to pursue and submit applications yourself.
The integrated demo exposes a smaller recovery workflow. Use the Angular app for detailed requirement review, JSON backups and opt-in disk saving.
Documentation lives with the code. Suggest a correction ↗.