Structured Object as Agent Memory

Use it for

Designing the memory layer for an AI workflow without building new infrastructure. The pattern, treat a structured object you already use as the shared memory, and let agents communicate through its fields rather than through a custom database.

The prompt

You are going to help me design the memory layer for an AI workflow without
building new infrastructure. The premise: any structured object I already
use can serve as agent memory if I use its fields with discipline.

I will give you:
1. A description of the workflow I want to build
2. A list of the structured tools I already use (Notion, Trello, Airtable,
   GitHub, Linear, a CRM, a Slack channel with pinned files, etc.)

Your job:

1. For each tool I use, identify whether it has the five fields that an
   agent memory needs:
   - An artifact field (one file, replace not accumulate)
   - A communication field (auditable, append-only, supports both agent
     and human messages)
   - An identity and lineage field (carries an ID and a version that
     persist across stages)
   - A state field (where in the pipeline this object currently is)
   - A status field (live flags like Approved, Blocked, Needs Revision)

2. Pick the tool that best fits the workflow. Explain why it beats the
   alternatives. Flag the field that requires the most discipline to use
   well, because that is where the system will break first.

3. Describe how each agent in the workflow would read and write to that
   object. Be specific. "Agent reads the description, writes a comment,
   moves the card to the next list" is the level of specificity I need.

4. Identify the one rule that has to be enforced for the system to work.
   Usually this is something like "only one attachment, replace not
   accumulate" or "comments are append-only, never edited." Whatever it is,
   name it.

5. Tell me what to test on the first run. The smallest workflow that
   exercises all five fields and surfaces whether the memory model holds.

Workflow and tools follow:
[paste]

Worked example

A member running a content production workflow used this against the tools she already had. The system identified that her existing Notion database had the right fields if she committed to one rule: the page property “Stage” had to be the single source of truth for pipeline position, and could only be updated by the agent that completed the previous stage. She built the workflow on top of Notion in a day, with no new infrastructure, and the system has been running unchanged for three months.