Built for work, not for chat
Sessions are permanent.
IOSYA is not a chat wrapper. Context continues; there is no thread to lose and no history to paste back in.
Operatives remember.
An operative keeps memory inside its workspace. It knows the project it has been working on for six weeks — you do not re-explain it every morning.
Every output is traceable.
Work is tied to a project and an operative, so you can see what produced a given result and when. Auditable by construction, not by export.
Request limits
Limits read as: your allowance per hour, then a reduced sustained rate once the allowance is spent.
Questions
What's a request?
A request is the unit of model work capacity shown on your plan. Plans scale by hourly request limits — we say requests, not credits.
Where does memory live?
Memory lives with the operative inside your workspace — sources, routines, and session history carry forward instead of resetting each chat.
Can I audit a decision?
Work in IOSYA is designed to be auditable: actions, sources, and context stay tied to the operative and project they belong to.
How is this not another chat wrapper?
IOSYA is built around permanent operatives and continuing sessions, not disposable chats that forget what happened yesterday.
Keep your project knowledge working
With operatives remembering your actions and outcomes, your results stay with you — no more starting from zero.
