Lyra
Lyra is not a separate chatbot waiting for you to explain your career again. It reads the page you are on, the record you are editing, the CV you are tailoring, and the live question you are answering, then stages useful work for review.
WHY IT MATTERS
Generic AI can produce polished text from almost nothing, which is exactly the risk. Lyra works with the material already inside Alynd, then waits for approval before anything trusted changes. The result is assistance that feels faster without drifting away from your real work.
Open Lyra from any page. It minimises, resizes, and stays nearby while the record, CV, or interview remains in view.
Move between General, Nexus, Studio, and Interview. Lyra keeps the context in mind instead of treating every request the same.
Use @ to pull in a role, education entry, professional record, or CV, so the question points at the right evidence.
Switch tone in one click: Direct ATS for recruiter-safe clarity, Executive for outcome-led seniority, or Technical for implementation precision.
When Lyra proposes changes to a record, CV, or answer, the change is staged first. You approve before anything saves.
Responses arrive as they are generated, so you can stop, follow up, or refine while the thought is still fresh.
WORKFLOW
Use Lyra where the work is happening. The active record, selected CV, target role, or live question can all be part of the conversation.
STEP 1
Use the sparkles button in the sidebar. Lyra begins with the page you are already working on.
STEP 2
No prompt craft required. Ask for the work plainly: draft responsibilities, tailor this CV, help answer this question.
STEP 3
Use the answer as guidance, accept a staged action, or ask for another pass. Trusted records update only when you say yes.
LYRA IN MOTION
Lyra works inside Alynd, reads the active record, and stages changes for review. It helps the source become clearer without taking it over.
01 / Nexus
Ask Lyra to refresh every responsibility on a role in one pass. Each proposed line stays selectable, so you can keep the parts that sound true.
Large record cleanups become reviewable instead of turning into a blind replace.
02 / Nexus
Lyra reads the saved responsibilities and proposes skills that map to the evidence. Accept the list when it matches what you could defend in interview.
Skill lines stay tied to work you can explain, not keywords copied from a job advert.
03 / Nexus
Ask Lyra to find the themes that carry across roles. The label proposal appears in the same review flow when you are ready to apply it.
Filters, CV picks, and job-spec mapping stay coherent because the tags are explicit.
04 / Studio
Paste how the role is written. Lyra compares the job spec with the active CV and stages summary and skill updates for that CV only.
Tailoring stays scoped to the Studio document you are sending out.
05 / Studio
Switch to Studio context, focus the summary, set the writing style to Executive, and ask Lyra to sharpen the voice.
Tone changes stay visible in the UI instead of disappearing into hidden prompt text.
06 / Focus
Type @ and choose the role, education entry, professional record, or CV you mean. Lyra answers with that entity in scope.
You point at the evidence instead of re-describing your career in chat.
OUTCOMES
No more copying career data into a generic chatbot every time you apply
No more AI advice that ignores the records already inside the app
No more tailoring that overwrites the source you need next week
No more interview answers that drift away from the CV
CONNECTED PLATFORM
Each area becomes stronger when it draws from the same trusted career record.
