Planning input

What it does

Answers what the department can take on and what it should, which means reading each request against the positioning and the audience, saying what each agent has free in the period, and saying what state the library and the contact base are already in.

Where it happens

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

• Check the Requests against the Standards
  • ref/mkt/prioritize-initiatives, activity 8 - Prioritize Marketing Initiatives
• Take Stock of What the Department Holds
  • ref/mkt/annual-marketing-plan, activity 3 - Build Annual Marketing Plan
• Work out What Is Free
  • ref/mkt/prioritize-initiatives, activity 5 - Prioritize Marketing Initiatives

What to record

Each program at a version, naming the entry condition, every step, every wait, the condition on every branch, and every exit. The hygiene cycle's scope at a version, saying which records it covers and what it has to fix in them. The rule that settles which program takes a contact who qualifies for two, with the date it was decided and who decided it. A dated account of the database between cycles: how many records there are, how many are complete enough to use, and how many may be contacted. The CONVENED and DONE records of everything it convenes. The go record for a program, naming the version that started sending and who said go. The standing readout at the cadence the process sets, and the decision it made after reading it.

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.