Understand the kinds of work Ysra does and where each runs, the loop every code change goes through, what always asks you first, and how to check where a job stands.

On this page

Ysra is one assistant that answers questions, changes code, helps you study, checks work and does jobs on a schedule. Every job keeps the same shape — your outcome, your boundary, visible work, evidence, and your decision — so you always know where it stands and who decides next. Read this page first if you're new to Ysra; each kind of work has its own page for the details.

The rule#

Nothing leaves your control without your yes. Ysra may read and work inside the boundary you set; committing, pushing, deploying, publishing and sending anything in your name wait for you, every time. And a job is called done only on evidence: a check that couldn't run is a failure, never a pass.

Kinds of work#

You want to Ysra Where it runs States explained in
Know something Answers from your files, tools and the web, with sources Ysra Ask
See it, or send it A chart or an interactive View in the answer; a Word document, a deck or a PDF Ysra Views · Documents and slides
Study a course or a topic Learn: notebooks from your course files, cards, practice exams and a tutor Ysra Learn
Have a helper answer for you, or for customers A colleague answers from its own documents Ysra; a public colleague on your website Colleagues
Change code or build an app A Code task: plans, changes, checks, repairs Your computer, or Ysra's cloud How a Code thread works
See it running A preview: a site, an app, or a phone app Ysra's cloud Previews
Check code before it ships A Mayz review Your computer, or Ysra's cloud Mayz reviews
Have a job done every week A Routine Ysra How routines work
Put it online Publish (a static site) or Deploy (your own hosting) Ysra, or your provider Publish or Deploy
Run commands on your servers Machines and runbooks Your machines Machines

The loop every change goes through#

Every change goes through the same steps, from the first read to the result, and the same rules hold at each one.

THE WORK WHEN SOMETHING FAILS Your outcome Understand and plan Edit your folder Run your checks Independent review Fix exactly what failed then the checks run again Candidate with evidence passed, or with the gaps named Stop and explain when repairs make no progress pass fail real defect pass no progress
Checks and review feed failures back into a narrow fix; when repairs stop helping, Ysra stops and explains.
Stage What happens What stops it going wrong
Understand Reads the project: structure, conventions, how it installs, tests and builds. Your request becomes acceptance criteria. Untrusted code isn't run just to find out.
Plan A visible plan that updates as Ysra learns. You can approve, revise or stop it.
Change Edits only inside the folder or project you opened. Ysra keeps its own record outside it, so undo is exact.
Check Your project's own commands run against the exact change: install, lint, type-check, test, build. A command that can't run is a failure. Tests that already failed before are reported apart.
Review A separate review, which didn't write the code, checks each criterion against the evidence. Interactive behaviour counts only when exercised in a real browser.
Repair Fixes scoped to what failed; only the checks the fix could affect run again. A repair that no longer changes the result ends the repairs.
Stop When repairs stop helping, Ysra keeps the work and says what blocks it. It ends Didn't work and says what failed, never a false success.

What always asks you first#

Action Asks first?
Reading and changing files inside your folder Depends on the thread's access: Auto works through, Asks first asks, Read only changes nothing. See Access modes
Anything outside the folder or this computer Yes, every time
Commit, push, deploy, publish Yes, every time
Paid work in a new Code thread Yes, once per thread
A routine sending an email or a message Yes, the exact text, every run
Destructive commands Yes, every time
STAYS ON YOUR COMPUTER REACHES YSRA Your folder and Git history worked on where they are The parts read for a task and the output of commands it ran Keys, sign-ins, secret files never read What you ask and the replies Where your machines are hosts, addresses, users A machine's name and mode nothing about how to reach it Every approval decided on your computer A record of the work paths and checksums, not contents as needed name only
What Ysra may do on its own, and what waits for you.

What is true on every job#

Promise What it means
Evidence is tied to the exact change A check or screenshot attaches to one version of the work; evidence for an earlier version never approves a later one.
Progress is saved as it happens Saved points along the way; an interruption resumes where it stopped, and you can rewind exactly.
Running out of credits loses nothing Work pauses before its next paid step and keeps everything; add credits and say continue. See Limits and costs.
Done is not delivered A finished change isn't published: committing, pushing and deploying each wait for you.

How to check where a job stands#

Kind of work Where to look
A Code task The thread: its state, plan, checks and their results
A routine Its runs, and Waiting for you for approvals
Credits Usage: what each thread, routine and colleague used
A public colleague Its conversations and its limits
YsraDocs