EvaNeT / field notes
How can AI use shared memory without crossing permissions?
What shared workspace context means in EvaNeT, how access limits answers, and why proposed changes still need a reviewer.
Shared context is useful only when the assistant sees the right workspace and the person using it has permission to see the underlying material.
Use the current workspace as the boundary
EvaNeT’s public docs describe Jai receiving fresh context for the selected workspace and the page or record in view when a message is sent. In the documented desktop alpha, permitted client and trip records can inform answers. A plan or missing booking is not presented as a confirmed result.
Separate reading from changing
A useful answer may summarize permitted records, but a proposed record change is a different operation. The documented desktop EMF beta stages supported edits as drafts with an exact field diff. Authorized reviewers decide whether to apply them after the service rechecks permission and record revision. Jai cannot approve its own proposed change.
Check the limits before a pilot
Workspace grants, enabled features, release access, and a configured model connection affect what is available. Ask which sources are in scope, which users can read them, what a draft can change, and where the approval record lives before connecting a new workflow.
Take the next step
Discuss one workflow with EvaNeT
We can map its current handoffs, risks, and review points before proposing a pilot.