Approve proposed Agent Memories
The nightly memory cycle is a review queue, not an automatic policy change. Clerked looks at repeatable corrections from recent invoice and email work, turns a high-confidence pattern into a proposed memory, and places the proposal in Tasks. Your decision determines whether the guidance becomes active.
Review the proposal
- Click Tasks in the left sidebar.
- Open the memory-review task. It opens the dedicated review view beside its source invoice when that source is available.
- Read the proposed guidance and its evidence, then open Additional details when you need more context.
- Check the source record, the affected field or line, and the evidence. Look for the before-and-after values, citations, vendor context, and the exception that keeps the rule from applying too broadly.
- Choose the action that matches your decision:
- Create this memory activates a new rule.
- Update this memory accepts a proposed change to an active rule.
- Reject this memory discards a proposal that is not a reusable policy.
After approval, the memory is materialized into the agent's active list. The proposal remains tied to the reviewer and its evidence so another admin can understand the decision later.
Edit before approving
If you have memory-management permission, choose Edit memory in the full proposal details and correct the wording. Keep the original evidence intact. The edited text must still preserve any linked vendor, account, or PO references that the proposal used. Submit the edited version with the primary approval action.
If the proposal is about a single vendor, check its anchor before approving. A global rule may be too broad even when the source correction was correct. Read Memory scope before choosing.
What happens after a decision
- An approved proposal becomes Active in the relevant agent's Memories section.
- A rejected proposal does not guide later processing.
- A proposal that is still being materialized shows its in-progress state; let the workflow finish before making a second decision.
- The decision and source evidence remain visible through the proposal or audit history. See Memory audit log.
The nightly cycle learns from reviewer corrections, but it does not replace validation rules or approval policies. A memory can guide extraction and coding; it cannot bypass a blocking validation check or change who must approve a record.
Task labels, evidence fields, source record types, and available actions depend on your permissions, company schema, and agent configuration. A company may receive no proposal on a night when there is no repeatable pattern to review.