Missions
Ayven keeps working on long-running concerns after the conversation ends: monitoring changes, tracking strategic questions and improving processes over weeks and months.
Approval before changes
Ayven asks your approval before she writes a document or files, assigns or moves a ticket, unless you have set that type of change to approve automatically. Deletions always wait for a person.
Human input when needed
When Ayven gets stuck or needs direction, she asks:
- Blocker detected: the mission pauses and notifies you
- Question routed: a specific request goes in chat to the person who holds the answer, you or a teammate
- Response captured: your answer feeds back into the mission
- Work resumes: she continues automatically with the new context
Mission lifecycle
| State | Meaning |
|---|---|
Open | Actively working: research, documentation, actions in progress. |
Paused | Blocked waiting for input, or circuit-broken after repeated failures. |
Closed | Goal achieved — but it may reopen if conditions change. |
How to use it
Give @Ayven a concern that outlives one conversation — "keep an eye on the onboarding funnel", "track the open questions from the platform review" — and she opens a mission for it. She reports progress, asks when she's blocked, and closes it when the goal is met.