Glossary
Look up any Ysra term, from access mode to workspace, with a link to the page that explains it in full.
On this page
This page defines the words Ysra uses, A to Z, each with a link to the page that explains it in full. Labels you see in the app are in bold.
Product labels in the interface#
Only Ysra and Mayz keep their English names in every language. The other product labels are:
| English | Français | العربية | Español |
|---|---|---|---|
| Ask | Demander | اسأل | Preguntar |
| Code | Code | البرمجة | Código |
| Learn | Apprendre | تعلّم | Aprender |
| Team | Équipe | الفريق | Equipo |
| Routines | Routines | المهام الدورية | Rutinas |
| Library | Bibliothèque | المكتبة | Biblioteca |
@mentions, CLI commands and flags, file paths and code retain their literal spelling. Keyboard shortcuts stay left to right in Arabic layouts.
- Access mode
- What a Code thread may do: Auto, Asks first or Read only. Plan first is a separate switch. Access modes
- Acceptance criteria
- The checklist a Code thread is reviewed against: yours, derived from your goal, or Ysra's quality baseline. Plans and criteria
- Approval
- Your consent to one exact outside action — an email, a Slack post, a Jira change. Editing the content needs a new approval. In a routine run, an approval waits 7 days, then the step is dropped. Actions and approvals, How routines work
- Automatic top-up
- Credits added on their own when the balance goes under a level you set, up to a monthly limit. Off until you turn it on. Plans and billing
- Autonomy policy
- What Ysra may do without asking, for your account and per repository. Autonomy policy
- Browser proof
- Interactive requirements executed in a real browser, with steps and screenshots. Review and verification
- Build idea
- An idea for something to build, saved under Code's message box by Set up with Ysra. Nothing is built until you choose Start building. Set up with Ysra
- Citation
- A numbered link from a claim in an Ask answer to a source that was actually read. Sources and citations
- Cloud project
- A Code project in Ysra's cloud with no GitHub repository: started from New cloud project, worked on a cloud machine, and downloadable as a zip. In Ysra's cloud
- Code thread
- A conversation in Code about one piece of work; each change asked for in it runs as a task. How a Code thread works
- Colleague
- An AI person your business hires at Team → Hire, with a role, a purpose, sources and capabilities. Colleagues answer in Ask, can run routines and can have a public link. Colleagues
- Credit pack
- A set number of extra credits you add once, kept until used. Plans and billing
- Credits
- The one unit of usage: threads, routines, Machines and Ask all use them. When they run out, work stops before its next step and keeps everything. Credits and usage
- Deep dive
- A research-style Ask answer with findings, evidence and open questions. Ask
- Delivery
- Getting your changes into your repository: commit them, then push a branch, each only when you say so. Commit and push
- Deployment
- Putting a change live with your own tools on your computer, such as your CI or your hosting's command-line tool — a separate step that asks you first. Deploy from your computer
- Document
- A Word file, a PowerPoint deck or a PDF that Ask makes from your sources. Documents and slides
- Expert
- Former name of a colleague.
- Learn
- Ysra as a tutor: notebooks from your course files, cards with a daily review, practice exams and topics. Learn
- Learn mode
- A switch in an Ask conversation that makes Ysra give hints before answers. Learn mode in Ask
- Location
- A colleague’s address and what to know on arriving. People who ask the way get a route link that opens in their own Maps app. Directions to you
- Mayz
- Ysra's code review: it reads and checks code and reports a verdict and findings. A review on its own usually costs 100–300 credits. Mayz reviews
- Memory
- Facts and preferences carried across Ask conversations, visible and deletable. Memory
- My files
- Your personal workspace. It is never shared. Workspaces and files
- Notebook
- One course in Learn, made from your course files, with a guide, cards and practice exams for each chapter. Study with a notebook
- Plan
- The ordered steps of a thread's work. Plan progress is not a verdict. Plans and criteria
- Plan (billing)
- What your account pays each month, and the credits it adds every month. Plans and billing
- Pre-existing failure
- A check that was already failing before the thread changed anything. Review and verification
- Preview
- The thread's project running so you can use it before delivering it. In Ysra's cloud: a site, an app or a phone app, which stops after 15 minutes with nobody looking (Previews). On your computer: your changes at a local address, before anything is committed (Try the change yourself).
- Project
- A large objective planned as milestones and tasks, integrated into one change. Projects
- Public colleague
- A colleague anyone with its link (or a chat bubble on your website) can ask, without an account. Its answers use its owner's credits, within the limits the owner sets. Formerly “public Expert”. Public link
- Receipt line
- The one line at the end of a Code task that says what Ysra ran to check
the work and how it went, such as “Ran:
npm test(passed).” or “Ran: nothing.” How a task ends - Repair
- A fix scoped to one concrete failure, starting from the exact reviewed version of the change. Review and verification
- Report
- The receipt for one change: the result, criteria, checks, browser check, credits used and delivery. Review the diff
- Routine
- Work a colleague (or, for older ones, Ysra) does on a schedule or when you run it, made from Ask, Team → Routines or Set up with Ysra; it asks before sending anything outside Ysra. Each has an on/off switch, and Pause, Archive and Delete on its page. Routines
- Routine card
- What appears under an Ask answer when a job could become a routine: when it runs, what it reads, what it does and what it asks first, with Start this routine. Start a routine from Ask
- Rule
- A standing instruction every Code thread reads first. Rules and instructions
- Run
- One execution of a routine, with its own state: Queued, Working, Waiting for you, Trying again, Done, Failed or Stopped. Runs and approvals
- Saved point
- A saved, exact version of a thread’s work, used to resume and to rewind. Up to 32 are kept per thread. Steering and saved points
- Session
- One goal worked to a result in one folder, as a Code thread in the desktop app or the CLI. Code
- Set up with Ysra
- A short, free talk about your company that proposes colleagues, a public link, routines, build ideas and documents to add; nothing is created until Start. 3 setups a day per person. Set up with Ysra
- Speed
- How hard Ask works on an answer: Auto (Ysra picks for each question), Quick or Thorough. Set per conversation and per colleague. Auto, Quick or Thorough
- Steering
- Redirecting a running Code thread without restarting it. Steering and saved points
- Task
- One change asked for in a Code thread, from Queued to an end state such as Your changes are ready or Didn't work. How a Code thread works
- Unproven
- A criterion that couldn't be checked — never counted as passed or failed. Review and verification
- View
- A chart, a diagram or a small interactive page inside an Ask answer, which you can save and open on its own page. Views
- Visitor questions
- Questions visitors left for a person on a public colleague, answered from Team → Visitor questions. Public link
- Worker
- Former name of a routine.
- Worker card
- Former name of a routine card.
- Workspace
- The space for your files, colleagues, memory, routines and plugins. A workspace can have members, each with a role. Workspaces and files, Members and roles
Related#
- Limits and costs — the numbers behind these terms.
- Troubleshooting — what to do when something stops.
- How a Code thread works — tasks and their states.
- How routines work — routines, runs and approvals.