Instructions and tasks
Projects, phases and dates
Save the integration project plan: the goal is a pilot and a report. Elena leads preparation, planned for 20–25 September 2026. Starting the pilot depends on security approval. The report is due on 10 October. Show phases, owners, dates, dependencies and current state.
The assistant records the project and meaningful phases as entities, links phases to their project and prerequisites, and saves goals, acceptance criteria, owners, milestones and state. Executable steps become tasks in the project scope. It reads the existing plan before adding more records.
Planned dates differ from actual execution; passing a deadline does not close a project. A task's deadline is due; its detail holds the project/phase IDs, owner, planned start, prerequisites and acceptance criteria. Tasks have no separate start, assignee or dependency fields. Meaningful phase relationships also belong in the graph; a todo ID is not an entity ID. Project state is stored as a fact. Recurring-run progress is stored separately.
Move the report deadline to 15 October because security approval is delayed. Preserve the previous plan and reason, and update the existing task.
Unknown dates and owners remain unknown; agent proposals are labelled as proposals. Blocked or overdue tasks stay open until actually completed or cancelled. For a plan table or diagram, ask for planned versus actual dates, dependencies, blockers and next actions. Recording dates does not itself add a Gantt screen to the application.
Save a procedure
Save an instruction called “How to prepare a delivery report”: collect current dates, flag delays and name the people responsible. Present it as a table.
To use it:
Prepare a report using the saved “How to prepare a delivery report” instruction.
To change it:
Add a “Next step” column to the delivery report instruction.
Keep a task list
Add a task: get Ivanov's confirmation of the dates by 10 September 2026.
Show open tasks in “work/deliveries”.
Mark the task about confirming dates as complete.
You can close a cancelled task with a reason:
Close the task to find a second supplier as dropped: we are keeping the current one.
Completed and dropped tasks stay in history. A due date alone does not create an alert; configure reminders in your assistant's app.
Pin a rule to an area
Pin in “work/deliveries”: all prices in reports must include VAT.
The pinned note is passed to the assistant when it accesses this area or a nested area.
Continue a conversation in another app
Save this conversation's context as “deliveries”: what we decided and what remains to do.
In another app connected to the same memory:
Load the “deliveries” context and continue with the unfinished work.
This saves a summary of the conversation. By default it is kept for 30 days; updating the summary extends that period. If the name is taken, the assistant tells you the name used.
Check a recurring task
If the assistant saves progress for scheduled work, you can ask:
Where did the last delivery check stop?
Set the schedule in the app that runs the assistant.