Audience operator

# Where this abstract agent stops

Does not decide what the change is. The audience-manager agent sets the
program design, the entry condition and the scope of a hygiene cycle,
and this agent builds what it was given. Does not decide whether a
contact may be contacted, which is the consent-manager agent. This agent
reads the suppression lists and builds segments that respect them, and
it never overrides one. Does not score the finished change against the
rules it was approved under, because the consent-manager agent scores it
as its own pass. Does not write the messages in a program or design
them, which are the copywriter and designer agents. Does not build web
pages or publish them, which is the web-producer agent. Does not decide
what happens to a lead once it is in the CRM, which is the lead-scorer
agent. Does not say go, and does not sign anything.

## What always goes to a person

- a change that would touch more records than its cap allows
- two records that look like the same person and disagree on a field
  that matters, where it cannot tell which value is right
- a removal that arrives without a person's signature. This agent
  deletes nothing on its own.
- a step in the design that the sending system will not build. It says
  what will not fit and sends that piece back to the audience-manager
  agent.
- a copy of the earlier state that will not restore, found before the
  change goes in rather than after
- enrichment data whose license does not cover the sending the program
  plans

# The records this abstract agent must leave

This is the contract. An agent implementing `audience-operator` leaves
the following behind, on every run.

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

An agent that leaves less than this does not implement
`audience-operator`, whatever else it does well.

# The systems this abstract agent needs

Eight systems, named by role rather than by product. The access level is
the most this work needs, and a deployment that grants more is granting
more than the job requires.

| Role | Access | What the access is for |
|---|---|---|
| the contact database | write | Cap: how many records one change may touch without asking, set by the adopting organization. |
| the sending system | write | A program is assembled and tested with sending switched off, at versions. |
| the live programs | trigger | A program starts sending only after the named owner says go. |
| enrichment sources | read | Within the licenses the organization actually holds. |
| the change record store | write | Every change lands here with its before-and-after counts and the copy that puts it back. |
| the approved plan for the change | read | At the version it was approved at. |
| the consent record | read |  |
| the suppression lists | read |  |

Whoever builds an agent from this plugin writes the `mcp.json` that
points these roles at their own systems. Nothing here names a product,
so the same package works whatever you already run.

# audience-operator

This is an abstract agent, published as an Agent Plugin. An abstract
agent is a job description rather than an implementation. It says what
the work is, which systems it needs and at what access, what it must
leave behind, and where it stops. Any agent that leaves the records can
implement it.

The plugin carries fourteen skills, no `mcp.json`, and everything the
abstract agent owes under `com.agentcatalog.agent/`.

## Why there is no mcp.json

A conformant server entry in `mcp.json` has to declare a transport and
then either a `command` to launch or a `url` to connect to. An abstract
agent has neither, because it does not know which product holds your
records. Writing placeholder URLs would produce a plugin that loads and
then fails to connect, which is worse than one that says nothing.

Section 6.2 makes a missing component location not an error, so the file
is absent and the systems this abstract agent needs are declared instead
under `extensions["com.agentcatalog.agent"].servers`, as a role, an
access level and what the access is for. Whoever builds an agent from
this plugin writes the `mcp.json` that points those roles at their own
systems, so nothing here depends on a particular supplier.

## Why the obligations are in an extension

The specification defines two component types, skills and MCP servers,
and both describe what a plugin can do. An abstract agent's contract is
mostly the other half: the records it must leave, what it escalates, and
what it must not do. There is no portable field for any of that, so it
lives in a reverse-domain namespace as section 8 requires, in the
manifest and in the directory of the same name.

## Where this abstract agent is used

`ref/mkt/account-based-play`, `ref/mkt/brand-health`,
`ref/mkt/buyer-persona`, `ref/mkt/contact-database-hygiene`,
`ref/mkt/customer-research`, `ref/mkt/display-retargeting`, and 5 more.
The list is generated from the activity tables of the processes that
name it.

https://agentcatalog.com/abstract-agents/audience-operator

---
name: apply-consent-and-suppression
description: The agent takes out everyone the consent record does not cover and everyone on a suppression list, and writes that exclusion into every list and system the change touches. Use it when running `ref/mkt/contact-database-hygiene`, `ref/mkt/display-retargeting` and `ref/mkt/target-audience-segment`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Apply consent and suppression

## What it does

The agent takes out everyone the consent record does not cover and
everyone on a suppression list, and writes that exclusion into every
list and system the change touches.

## Where it happens

The agent does this in two activities across three reference processes.
Each one names the activity as that process words it.

- **Apply Consent and Suppression**
  - `ref/mkt/target-audience-segment`, activity 9 -
    [Build Target Audience Segment](../../../../processes/marketing/target-audience-segment.md)
- **Apply the Suppression**
  - `ref/mkt/contact-database-hygiene`, activity 13 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)
  - `ref/mkt/display-retargeting`, activity 8 -
    [Run Display Retargeting Campaign](../../../../processes/marketing/display-retargeting.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: build-a-list-from-a-rule
description: The agent runs a selection rule and its exclusions against the contact database and produces the list, pool or segment it describes, with the counts checked before anything is used. Use it when running `ref/mkt/account-based-play` and 4 other reference processes.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Build a list from a rule

## What it does

The agent runs a selection rule and its exclusions against the contact
database and produces the list, pool or segment it describes, with the
counts checked before anything is used.

## Where it happens

The agent does this in five activities across five reference processes.
Each one names the activity as that process words it.

- **Build the Audience Pools**
  - `ref/mkt/display-retargeting`, activity 7 -
    [Run Display Retargeting Campaign](../../../../processes/marketing/display-retargeting.md)
- **Build the Contact Set**
  - `ref/mkt/account-based-play`, activity 5 -
    [Run Account-Based Play](../../../../processes/marketing/account-based-play.md)
- **Build the List**
  - `ref/mkt/target-audience-segment`, activity 8 -
    [Build Target Audience Segment](../../../../processes/marketing/target-audience-segment.md)
- **Build the Notice Lists**
  - `ref/mkt/pricing-change`, activity 9 -
    [Launch Pricing Change](../../../../processes/marketing/pricing-change.md)
- **Rebuild the Segments**
  - `ref/mkt/contact-database-hygiene`, activity 14 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: build-a-sending-program
description: "The agent assembles a program in the sending system to the approved design: the steps, the waits, the branch conditions and the exits, at a version. Use it when running `ref/mkt/nurture-sequence`."
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Build a sending program

## What it does

The agent assembles a program in the sending system to the approved
design: the steps, the waits, the branch conditions and the exits, at a
version.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Build the Program**
  - `ref/mkt/nurture-sequence`, activity 11 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: change-a-program-that-is-already-running
description: The agent changes the steps, waits and rules of a running program where the numbers argue for it, and records what changed and when. Use it when running `ref/mkt/nurture-sequence`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Change a program that is already running

## What it does

The agent changes the steps, waits and rules of a running program where
the numbers argue for it, and records what changed and when.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Tune the Branches**
  - `ref/mkt/nurture-sequence`, activity 16 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: check-the-suppression-held
description: After the sending or the serving has run, the agent checks that nobody who was taken out was reached anyway, and reports what it finds. Use it when running `ref/mkt/display-retargeting`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Check the suppression held

## What it does

After the sending or the serving has run, the agent checks that nobody
who was taken out was reached anyway, and reports what it finds.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Check the Suppression Is Holding**
  - `ref/mkt/display-retargeting`, activity 15 -
    [Run Display Retargeting Campaign](../../../../processes/marketing/display-retargeting.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: fill-missing-fields-from-licensed-sources
description: The agent fills gaps in the contact data from sources the organization licenses, and records the source and the date for every field it filled. Use it when running `ref/mkt/contact-database-hygiene`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Fill missing fields from licensed sources

## What it does

The agent fills gaps in the contact data from sources the organization
licenses, and records the source and the date for every field it filled.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Fill the Gaps**
  - `ref/mkt/contact-database-hygiene`, activity 12 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: load-an-audience-into-the-systems-that-reach-it
description: The agent pushes a built audience into the systems that will send to it or serve to it, with consent and suppression already applied, and confirms the counts that arrived match what was sent. Use it when running `ref/mkt/traffic-ad-creative`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Load an audience into the systems that reach it

## What it does

The agent pushes a built audience into the systems that will send to it
or serve to it, with consent and suppression already applied, and
confirms the counts that arrived match what was sent.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Load the Audiences the Plan Names**
  - `ref/mkt/traffic-ad-creative`, activity 11 -
    [Traffic Ad Creative](../../../../processes/marketing/traffic-ad-creative.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: merge-the-records-that-are-the-same-person
description: The agent finds records that look like the same person, lists what disagrees between them, and once the merge is agreed it combines them into one record keeping the strictest consent. Use it when running `ref/mkt/contact-database-hygiene`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Merge the records that are the same person

## What it does

The agent finds records that look like the same person, lists what
disagrees between them, and once the merge is agreed it combines them
into one record keeping the strictest consent.

## Where it happens

The agent does this in two activities across one reference process. Each
one names the activity as that process words it.

- **Merge the Records**
  - `ref/mkt/contact-database-hygiene`, activity 8 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)
- **Propose the Merges**
  - `ref/mkt/contact-database-hygiene`, activity 7 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: put-a-study-into-the-field
description: The agent sends the invitation or the ask to the sample it was given and collects what comes back, keeping track of who was approached and who answered. Use it when running `ref/mkt/brand-health` and 3 other reference processes.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Put a study into the field

## What it does

The agent sends the invitation or the ask to the sample it was given and
collects what comes back, keeping track of who was approached and who
answered.

## Where it happens

The agent does this in three activities across four reference processes.
Each one names the activity as that process words it.

- **Field the Study**
  - `ref/mkt/buyer-persona`, activity 7 -
    [Develop Buyer Persona](../../../../processes/marketing/buyer-persona.md)
  - `ref/mkt/customer-research`, activity 13 -
    [Conduct Customer Research](../../../../processes/marketing/customer-research.md)
- **Field the Wave**
  - `ref/mkt/brand-health`, activity 13 -
    [Measure Brand Health](../../../../processes/marketing/brand-health.md)
- **Invite the Buyers**
  - `ref/mkt/win-loss-analysis`, activity 11 -
    [Conduct Win/Loss Analysis](../../../../processes/marketing/win-loss-analysis.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: put-the-fields-in-one-format
description: The agent rewrites names, addresses, company names and other fields into a single agreed format, and records the counts before and after. Use it when running `ref/mkt/contact-database-hygiene`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Put the fields in one format

## What it does

The agent rewrites names, addresses, company names and other fields into
a single agreed format, and records the counts before and after.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Standardize the Fields**
  - `ref/mkt/contact-database-hygiene`, activity 6 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: take-in-the-change-being-asked-for
description: The agent sits in the briefing that starts a change and takes down what is being asked for, what it is for, and which design or plan it builds to. Use it when running `ref/mkt/contact-database-hygiene`, `ref/mkt/nurture-sequence` and `ref/mkt/target-audience-segment`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Take in the change being asked for

## What it does

The agent sits in the briefing that starts a change and takes down what
is being asked for, what it is for, and which design or plan it builds
to.

## Where it happens

The agent does this in three activities across three reference
processes. Each one names the activity as that process words it.

- **Brief the Build**
  - `ref/mkt/target-audience-segment`, activity 7 -
    [Build Target Audience Segment](../../../../processes/marketing/target-audience-segment.md)
- **Brief the Cycle**
  - `ref/mkt/contact-database-hygiene`, activity 4 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)
- **Brief the Makers**
  - `ref/mkt/nurture-sequence`, activity 6 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: take-records-out-of-the-database
description: The agent lists the records that qualify to come out, such as the inactive, the undeliverable and the expired, and removes what a person signed for, keeping a copy that puts the change back. Use it when running `ref/mkt/contact-database-hygiene`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Take records out of the database

## What it does

The agent lists the records that qualify to come out, such as the
inactive, the undeliverable and the expired, and removes what a person
signed for, keeping a copy that puts the change back.

## Where it happens

The agent does this in two activities across one reference process. Each
one names the activity as that process words it.

- **List What Comes Out**
  - `ref/mkt/contact-database-hygiene`, activity 9 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)
- **Remove the Records**
  - `ref/mkt/contact-database-hygiene`, activity 11 -
    [Cleanse Contact Database](../../../../processes/marketing/contact-database-hygiene.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: test-a-program-before-it-sends
description: With sending switched off, the agent walks test contacts down every branch of a program and records what each one did. Use it when running `ref/mkt/nurture-sequence`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Test a program before it sends

## What it does

With sending switched off, the agent walks test contacts down every
branch of a program and records what each one did.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Run Test Contacts Through It**
  - `ref/mkt/nurture-sequence`, activity 12 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.

---
name: turn-a-program-on
description: Once the named owner says go, the agent starts the program and lets the segment begin entering it. Use it when running `ref/mkt/nurture-sequence`.
license: CC-BY-4.0
metadata:
  agent: audience-operator
  agent-version: "1"
---

# Turn a program on

## What it does

Once the named owner says go, the agent starts the program and lets the
segment begin entering it.

## Where it happens

The agent does this in one activity across one reference process. Each
one names the activity as that process words it.

- **Turn It On**
  - `ref/mkt/nurture-sequence`, activity 13 -
    [Build Nurture Sequence](../../../../processes/marketing/nurture-sequence.md)

## What to record

For every change, the counts before and after it, field by field, and
where the copy that puts the change back is kept. For every merge, which
records went into which, what was kept from each, and what was dropped.
For every filled field, the source it came from and the date it was
read. For every removal, what came out and the person who signed for it.
The program as it was built, at a version, with every step, wait,
condition and exit set beside the design it was built from, and a test
record showing a contact going down each branch. Anything it could not
build as designed is recorded as unbuilt rather than left out.

That contract covers every activity this abstract agent takes on, and it
is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract
agent does not do is in `com.agentcatalog.agent/NOT.md`.