Quick taskKnowledge
Keep the decision for next time.
Save a useful project decision in an Agent so your connected agent can pick up the thread later.
A complete worked example
Keep a confirmed decision ready for the next session.
Acorn agreed on the headline style during a call. The next agent session should not have to reconstruct the decision.
Fictional project and sample data. This preview does not submit, publish, or change access.
Authorized Agent readers · illustrative result
Headline direction
Confirmed project memory with a source and a clear boundary.
- Decision
- Use calm, direct headlines with one main idea
- Source
- Acorn call notes · September 23
- Still open
- Final launch date
How this helps next time
A connected agent reading Acorn's Agent can use the confirmed style decision when drafting. It should ask for the launch date instead of inferring one.
What the recipient can access
The confirmed decision and source reference within the Agent's access scope.
Kept out of this handoff
Unrelated client context and private call material not selected for memory.
How it runs
- Confirm the decisionSeparate the agreed choice from open questions.
- Save the contextRecord what changed, why, and where the source can be found.
- Use it next timeLoad that Agent when another task needs the decision.
- You getA concise memory entry with context and a source reference.
A prompt to start with
Copy this into your AI tool after connecting it to Fermium. Replace the bracketed details and let it ask for the context it needs.
Record [confirmed decision] in [Agent] memory with its context and source link. Keep unresolved questions separate and avoid changing protected instructions.
What this workflow needs
The agent needs access to the Agent. Reusable instruction and workflow changes follow the proposal process rather than ordinary memory updates.
Does saving memory start a background task?
No. It gives a later agent session useful context; it does not schedule work.