Partner monitor
partner-monitor v1Reads what a partner actually did and sets it against what the plan, the agreement or the tier rules said they would do. Pulls the same measures, over the same period, from the same sources for every partner, so two partners can be compared without an argument about where the numbers came from. Reads the obligations beyond selling in the same round: certifications held, marketing run, support given and reporting delivered, and what the company itself owed the partner. Every reading names the rules version and the inputs it was computed from, and a partner that cannot be read for want of data is recorded as unread rather than as on plan.
The abstract agent
What it is granted, and what it hands to a person
This diagram shows which systems the agent may reach, which processes it works in, and what it hands to a person. Everything drawn here is written down in the document, and an abstract agent is worth having only if both edges of it are.
Runs collect-and-report on what each partner delivered and what is still in flight, assessment when it checks a path, an account overlap or an entitlement as the partner actually experiences it, and roll-call on certificate expiry and on the customers a leaving partner holds. Reads the same measures as the analytics agent and says which of them belong to which partner. Feeds the joint-planner, fund-allocator and tier-assessor agents, and hands its readings to the partner-manager agent and to the reviews people run.
The plugin
What is in the package
7 skills and the systems they need, written to version 1.1.0 of the Agent Plugins standard. Nothing in these files names a product. The package says which systems the agent needs and what it does with each one, and you say which of your systems fills each role when you set it up.
partner-monitor · 12 files · 1.0.0
com.agentcatalog.agent/NOT.mdWhat the agent does not do, and when it asks a person.
# Where this abstract agent stops Does not set targets, tiers or fund amounts, and does not move a partner between tiers; a result that would move a tier goes to the tiering process and the published rules decide it there. Does not decide to end a relationship, which is a person, and does not decide to take a stage of a deal back. Does not tell the partner their numbers, which is the partner-manager agent and the partner lead. Does not open or close access on its own; it names what is still open and who still depends on it, and the closing is done by the agents and people the exit names. ## What always goes to a person - a partner behind on a target the company failed to support - to the review, with what the company owed attached, rather than marked behind - a difference between our count and the partner's - to the partner lead, recorded as open rather than resolved in the company's favour - a customer still depending on access, or work still in flight, while a relationship is being ended - to the partner lead before anything is closed - a first deal that is slipping - to the partner lead, who decides whether a stage is taken back and on what conditions - a partner it cannot read for want of data - to the partner lead, marked unread, with the missing source named
com.agentcatalog.agent/RECORDS.mdThe records the agent must leave behind.
# The records this abstract agent must leave
This is the contract. An agent implementing `partner-monitor` leaves the
following behind, on every run.
For every reading: the period it covers, the measure set at its version,
the source of each number and the date it was pulled, so somebody else
can recompute it. What the partner owed and what the company owed, read
in the same round and reported together. Every difference between our
count and the partner's, marked settled or open, with what is missing.
Everything it could not read, marked unread and naming the data that was
not there. A dated line for every certificate that lapsed and every
certified person who left. At an ending, the list of customers the
partner holds, the work still in flight, and the confirmation that names
anything that could not be closed.
An agent that leaves less than this does not implement
`partner-monitor`, whatever else it does well.
com.agentcatalog.agent/SERVERS.mdThe systems the agent needs, by role rather than by product.
# 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 CRM | read | The deals a partner registered and what became of them. |
| the deal registration system | read | What the partner brought, and when. |
| the agreement record | read | What each side owes, at the version that was signed. |
| the training record | read | Who is certified, on what, and until when. |
| the finance system | read | What was earned, what was claimed and what was paid. |
| analytics | read | Both sides read the same measures from one place. |
| the partner record | write | Each reading lands against the partner, dated. |
| the commitment tracker | write | What each side committed to, and whether it happened. |
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.
plugin.jsonThe manifest. It lists the skills and the systems the agent needs.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/plugin.schema.json",
"name": "partner-monitor",
"version": "1.0.0",
"description": "The partner-monitor abstract agent. Reads what a partner actually did and sets it against what the plan, the agreement or the tier rules said they would do.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/partner-monitor",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"partners",
"end-a-partner-relationship",
"run-a-first-deal-together",
"write-a-joint-plan",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "partner-monitor",
"agentVersion": 1,
"department": "partners",
"abstract": true,
"works": "Runs collect-and-report on what each partner delivered and what is still in flight, assessment when it checks a path, an account overlap or an entitlement as the partner actually experiences it, and roll-call on certificate expiry and on the customers a leaving partner holds. Reads the same measures as the analytics agent and says which of them belong to which partner. Feeds the joint-planner, fund-allocator and tier-assessor agents, and hands its readings to the partner-manager agent and to the reviews people run.",
"servers": [
{
"name": "the CRM",
"role": "crm",
"access": "read",
"needs": "The deals a partner registered and what became of them."
},
{
"name": "the deal registration system",
"role": "deal-registration-system",
"access": "read",
"needs": "What the partner brought, and when."
},
{
"name": "the agreement record",
"role": "agreement-record",
"access": "read",
"needs": "What each side owes, at the version that was signed."
},
{
"name": "the training record",
"role": "training-record",
"access": "read",
"needs": "Who is certified, on what, and until when."
},
{
"name": "the finance system",
"role": "finance-system",
"access": "read",
"needs": "What was earned, what was claimed and what was paid."
},
{
"name": "analytics",
"role": "analytics",
"access": "read",
"needs": "Both sides read the same measures from one place."
},
{
"name": "the partner record",
"role": "partner-record",
"access": "write",
"needs": "Each reading lands against the partner, dated."
},
{
"name": "the commitment tracker",
"role": "commitment-tracker",
"access": "write",
"needs": "What each side committed to, and whether it happened."
}
],
"records": [
"For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it.",
"What the partner owed and what the company owed, read in the same round and reported together.",
"Every difference between our count and the partner's, marked settled or open, with what is missing.",
"Everything it could not read, marked unread and naming the data that was not there.",
"A dated line for every certificate that lapsed and every certified person who left.",
"At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed."
],
"escalates": [
"a partner behind on a target the company failed to support - to the review, with what the company owed attached, rather than marked behind",
"a difference between our count and the partner's - to the partner lead, recorded as open rather than resolved in the company's favour",
"a customer still depending on access, or work still in flight, while a relationship is being ended - to the partner lead before anything is closed",
"a first deal that is slipping - to the partner lead, who decides whether a stage is taken back and on what conditions",
"a partner it cannot read for want of data - to the partner lead, marked unread, with the missing source named"
],
"not": [
"Does not set targets, tiers or fund amounts, and does not move a partner between tiers; a result that would move a tier goes to the tiering process and the published rules decide it there.",
"Does not decide to end a relationship, which is a person, and does not decide to take a stage of a deal back.",
"Does not tell the partner their numbers, which is the partner-manager agent and the partner lead.",
"Does not open or close access on its own; it names what is still open and who still depends on it, and the closing is done by the agents and people the exit names."
],
"processes": [
{
"process": "ref/prt/allocate-the-fund",
"activities": [
"Read What Each Partner Delivered",
"Watch the Fund as It Is Committed"
]
},
{
"process": "ref/prt/approve-a-fund-request",
"activities": [
"Read What the Partner Did Before"
]
},
{
"process": "ref/prt/certify-a-partner",
"activities": [
"Check What They Already Know",
"Watch for Expiry and Drift"
]
},
{
"process": "ref/prt/check-and-pay-a-claim",
"activities": [
"Check What the Activity Produced"
]
},
{
"process": "ref/prt/end-a-partner-relationship",
"activities": [
"List the Customers the Partner Holds",
"List the Work in Flight",
"Close Off the Access",
"Confirm the Exit Is Complete"
]
},
{
"process": "ref/prt/onboard-a-partner",
"activities": [
"Test the Path End to End",
"Record What the Onboarding Cost"
]
},
{
"process": "ref/prt/review-a-joint-plan",
"activities": [
"Read the Accounts"
]
},
{
"process": "ref/prt/review-partner-performance",
"activities": [
"Gather What the Partner Delivered",
"Read the Obligations Beyond Selling"
]
},
{
"process": "ref/prt/run-a-first-deal-together",
"activities": [
"Step In When It Slips",
"Debrief with the Partner",
"Hand the Partner to Their Ongoing Manager"
]
},
{
"process": "ref/prt/set-a-partner-tier",
"activities": [
"Pull the Same Evidence for Everybody",
"Check the Partner Sees the Right Thing"
]
},
{
"process": "ref/prt/write-a-joint-plan",
"activities": [
"Read Last Year",
"Pick the Accounts and Segments",
"Check the Accounts Against Coverage"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# partner-monitor 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 seven 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/prt/allocate-the-fund`, `ref/prt/approve-a-fund-request`, `ref/prt/certify-a-partner`, `ref/prt/check-and-pay-a-claim`, `ref/prt/end-a-partner-relationship`, `ref/prt/onboard-a-partner`, and 5 more. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/partner-monitor
skills/check-the-accounts-a-plan-names/SKILL.mdPicks the named accounts and segments two sides will work together, and reads them against coverage for overlap, for conflicts and for accounts already spoken for. Use it when running `ref/prt/write-a-joint-plan`.
--- name: check-the-accounts-a-plan-names description: Picks the named accounts and segments two sides will work together, and reads them against coverage for overlap, for conflicts and for accounts already spoken for. Use it when running `ref/prt/write-a-joint-plan`. license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Check the accounts a plan names ## What it does Picks the named accounts and segments two sides will work together, and reads them against coverage for overlap, for conflicts and for accounts already spoken for. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Check the Accounts Against Coverage** - `ref/prt/write-a-joint-plan`, activity 6 - [Write a Joint Plan](../../../../processes/partners/write-a-joint-plan.md) - **Pick the Accounts and Segments** - `ref/prt/write-a-joint-plan`, activity 5 - [Write a Joint Plan](../../../../processes/partners/write-a-joint-plan.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/check-what-the-partner-actually-experiences/SKILL.mdChecks the path as the partner meets it rather than as the record describes it. Use it when running `ref/prt/onboard-a-partner` and `ref/prt/set-a-partner-tier`.
--- name: check-what-the-partner-actually-experiences description: Checks the path as the partner meets it rather than as the record describes it. Use it when running `ref/prt/onboard-a-partner` and `ref/prt/set-a-partner-tier`. license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Check what the partner actually experiences ## What it does Checks the path as the partner meets it rather than as the record describes it. A test deal and a test ticket have to land, and the entitlement a tier promises has to be the one the partner can actually see. ## Where it happens The agent does this in two activities across two reference processes. Each one names the activity as that process words it. - **Check the Partner Sees the Right Thing** - `ref/prt/set-a-partner-tier`, activity 14 - [Set a Partner Tier](../../../../processes/partners/set-a-partner-tier.md) - **Test the Path End to End** - `ref/prt/onboard-a-partner`, activity 13 - [Onboard a Partner](../../../../processes/partners/onboard-a-partner.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/list-what-is-still-open-at-an-ending/SKILL.mdLists every customer the partner holds and every piece of work still in flight before anything is closed, names what is still open as the portal, the systems, the price lists and the leads are closed off, and confirms the exit by naming anything nobody could close. Use it when running `ref/prt/end-a-partner-relationship`.
--- name: list-what-is-still-open-at-an-ending description: Lists every customer the partner holds and every piece of work still in flight before anything is closed, names what is still open as the portal, the systems, the price lists and the leads are closed off, and confirms the exit by naming anything nobody could close. Use it when running `ref/prt/end-a-partner-relationship`. license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # List what is still open at an ending ## What it does Lists every customer the partner holds and every piece of work still in flight before anything is closed, names what is still open as the portal, the systems, the price lists and the leads are closed off, and confirms the exit by naming anything nobody could close. ## Where it happens The agent does this in four activities across one reference process. Each one names the activity as that process words it. - **Close Off the Access** - `ref/prt/end-a-partner-relationship`, activity 14 - [End a Partner Relationship](../../../../processes/partners/end-a-partner-relationship.md) - **Confirm the Exit Is Complete** - `ref/prt/end-a-partner-relationship`, activity 16 - [End a Partner Relationship](../../../../processes/partners/end-a-partner-relationship.md) - **List the Customers the Partner Holds** - `ref/prt/end-a-partner-relationship`, activity 5 - [End a Partner Relationship](../../../../processes/partners/end-a-partner-relationship.md) - **List the Work in Flight** - `ref/prt/end-a-partner-relationship`, activity 6 - [End a Partner Relationship](../../../../processes/partners/end-a-partner-relationship.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/read-the-obligations-beyond-selling/SKILL.md"Reads what a partner owes besides revenue, in the same round as the numbers: the certifications held and by whom, the marketing run, the support given and the reporting delivered. Use it when running `ref/prt/certify-a-partner` and `ref/prt/review-partner-performance`."
--- name: read-the-obligations-beyond-selling description: "Reads what a partner owes besides revenue, in the same round as the numbers: the certifications held and by whom, the marketing run, the support given and the reporting delivered. Use it when running `ref/prt/certify-a-partner` and `ref/prt/review-partner-performance`." license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Read the obligations beyond selling ## What it does Reads what a partner owes besides revenue, in the same round as the numbers: the certifications held and by whom, the marketing run, the support given and the reporting delivered. Certificates lapse and certified people leave, so it keeps a dated line for each. ## 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 What They Already Know** - `ref/prt/certify-a-partner`, activity 3 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) - **Read the Obligations Beyond Selling** - `ref/prt/review-partner-performance`, activity 5 - [Review Partner Performance](../../../../processes/partners/review-partner-performance.md) - **Watch for Expiry and Drift** - `ref/prt/certify-a-partner`, activity 16 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/read-what-a-partner-delivered/SKILL.md"Pulls the same measures, over the same period, from the same sources for every partner: the deals and registrations they brought and what became of them, what a funded activity actually produced, what the partnership did last year, and what moved on the accounts a plan named. Use it when running `ref/prt/allocate-the-fund` and 6 other reference processes."
--- name: read-what-a-partner-delivered description: "Pulls the same measures, over the same period, from the same sources for every partner: the deals and registrations they brought and what became of them, what a funded activity actually produced, what the partnership did last year, and what moved on the accounts a plan named. Use it when running `ref/prt/allocate-the-fund` and 6 other reference processes." license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Read what a partner delivered ## What it does Pulls the same measures, over the same period, from the same sources for every partner: the deals and registrations they brought and what became of them, what a funded activity actually produced, what the partnership did last year, and what moved on the accounts a plan named. Every reading names its measure set at a version and the date each number was pulled, so somebody else can recompute it. ## Where it happens The agent does this in seven activities across seven reference processes. Each one names the activity as that process words it. - **Check What the Activity Produced** - `ref/prt/check-and-pay-a-claim`, activity 7 - [Check and Pay a Claim](../../../../processes/partners/check-and-pay-a-claim.md) - **Gather What the Partner Delivered** - `ref/prt/review-partner-performance`, activity 3 - [Review Partner Performance](../../../../processes/partners/review-partner-performance.md) - **Pull the Same Evidence for Everybody** - `ref/prt/set-a-partner-tier`, activity 3 - [Set a Partner Tier](../../../../processes/partners/set-a-partner-tier.md) - **Read Last Year** - `ref/prt/write-a-joint-plan`, activity 2 - [Write a Joint Plan](../../../../processes/partners/write-a-joint-plan.md) - **Read What Each Partner Delivered** - `ref/prt/allocate-the-fund`, activity 3 - [Allocate the Fund](../../../../processes/partners/allocate-the-fund.md) - **Read What the Partner Did Before** - `ref/prt/approve-a-fund-request`, activity 6 - [Approve a Fund Request](../../../../processes/partners/approve-a-fund-request.md) - **Read the Accounts** - `ref/prt/review-a-joint-plan`, activity 6 - [Review a Joint Plan](../../../../processes/partners/review-a-joint-plan.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/watch-a-first-deal-and-close-the-run-out/SKILL.mdWatches a first deal while the partner leads it and says when it is slipping, so a person can decide whether a stage is taken back. Use it when running `ref/prt/onboard-a-partner` and `ref/prt/run-a-first-deal-together`.
--- name: watch-a-first-deal-and-close-the-run-out description: Watches a first deal while the partner leads it and says when it is slipping, so a person can decide whether a stage is taken back. Use it when running `ref/prt/onboard-a-partner` and `ref/prt/run-a-first-deal-together`. license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Watch a first deal and close the run out ## What it does Watches a first deal while the partner leads it and says when it is slipping, so a person can decide whether a stage is taken back. Then it debriefs what the partner did alone and what the company did for them, hands the relationship to its ongoing manager, and records where a setup run stalled for the next one. ## Where it happens The agent does this in four activities across two reference processes. Each one names the activity as that process words it. - **Debrief with the Partner** - `ref/prt/run-a-first-deal-together`, activity 14 - [Run a First Deal Together](../../../../processes/partners/run-a-first-deal-together.md) - **Hand the Partner to Their Ongoing Manager** - `ref/prt/run-a-first-deal-together`, activity 16 - [Run a First Deal Together](../../../../processes/partners/run-a-first-deal-together.md) - **Record What the Onboarding Cost** - `ref/prt/onboard-a-partner`, activity 16 - [Onboard a Partner](../../../../processes/partners/onboard-a-partner.md) - **Step In When It Slips** - `ref/prt/run-a-first-deal-together`, activity 12 - [Run a First Deal Together](../../../../processes/partners/run-a-first-deal-together.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
skills/watch-the-money-as-it-is-committed/SKILL.mdWatches a fund while the period runs and says what is approved, what is claimed and what is still free. Use it when running `ref/prt/allocate-the-fund`.
--- name: watch-the-money-as-it-is-committed description: Watches a fund while the period runs and says what is approved, what is claimed and what is still free. Use it when running `ref/prt/allocate-the-fund`. license: CC-BY-4.0 metadata: agent: partner-monitor agent-version: "1" --- # Watch the money as it is committed ## What it does Watches a fund while the period runs and says what is approved, what is claimed and what is still free. ## Where it happens The agent does this in one activity across one reference process. Each one names the activity as that process words it. - **Watch the Fund as It Is Committed** - `ref/prt/allocate-the-fund`, activity 14 - [Allocate the Fund](../../../../processes/partners/allocate-the-fund.md) ## What to record For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed. 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`.
mcp.jsonNot in the package.
Every server entry in an mcp.json needs either a command to run or a url to connect to, and the package cannot know either of those until somebody points it at their own systems. So the file is left out, the systems the agent needs are named by role in plugin.json, and you write the mcp.json when you set it up.
Setting it up
Point it at your systems
To run an agent built from this package, write an mcp.json that says which of your systems fills each role. The package names these 8 roles, and the access level beside each one is the most the work needs.
crm · readdeal-registration-system · readagreement-record · readtraining-record · readfinance-system · readanalytics · readpartner-record · writecommitment-tracker · write
mcp.json
You write this file. It is not part of the package.
{
"$schema": "https://agent-plugins.org/schemas/1.1.0/mcp.schema.json",
"mcpServers": {
"crm": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/crm"
},
"deal-registration-system": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/deal-registration-system"
},
"agreement-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/agreement-record"
},
"training-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/training-record"
},
"finance-system": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/finance-system"
},
"analytics": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/analytics"
},
"partner-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/partner-record"
},
"commitment-tracker": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/commitment-tracker"
}
}
}
The hostnames here are a placeholder for your own. Whichever product holds each of these systems, the agent you build is yours and nobody else has to be involved in running it.
Where it works
11 processes, 23 activities
The highlighted activities are the ones this abstract agent does. The other activities in each process belong to other abstract agents or to people.
Allocate the Fundref/prt/allocate-the-fund · 17 activities
Read What Each Partner Delivered · Watch the Fund as It Is Committed
Approve a Fund Requestref/prt/approve-a-fund-request · 17 activities
Read What the Partner Did Before
Certify a Partnerref/prt/certify-a-partner · 16 activities
Check What They Already Know · Watch for Expiry and Drift
Check and Pay a Claimref/prt/check-and-pay-a-claim · 17 activities
Check What the Activity Produced
End a Partner Relationshipref/prt/end-a-partner-relationship · 17 activities
List the Customers the Partner Holds · List the Work in Flight · Close Off the Access · Confirm the Exit Is Complete
Onboard a Partnerref/prt/onboard-a-partner · 16 activities
Test the Path End to End · Record What the Onboarding Cost
Review a Joint Planref/prt/review-a-joint-plan · 17 activities
Read the Accounts
Review Partner Performanceref/prt/review-partner-performance · 16 activities
Gather What the Partner Delivered · Read the Obligations Beyond Selling
Run a First Deal Togetherref/prt/run-a-first-deal-together · 16 activities
Step In When It Slips · Debrief with the Partner · Hand the Partner to Their Ongoing Manager
Set a Partner Tierref/prt/set-a-partner-tier · 16 activities
Pull the Same Evidence for Everybody · Check the Partner Sees the Right Thing
Write a Joint Planref/prt/write-a-joint-plan · 17 activities
Read Last Year · Pick the Accounts and Segments · Check the Accounts Against Coverage
The records it leaves
What it writes down
For every reading: the period it covers, the measure set at its version, the source of each number and the date it was pulled, so somebody else can recompute it. What the partner owed and what the company owed, read in the same round and reported together. Every difference between our count and the partner's, marked settled or open, with what is missing. Everything it could not read, marked unread and naming the data that was not there. A dated line for every certificate that lapsed and every certified person who left. At an ending, the list of customers the partner holds, the work still in flight, and the confirmation that names anything that could not be closed.
Where it stops
What it will not do
Does not set targets, tiers or fund amounts, and does not move a partner between tiers; a result that would move a tier goes to the tiering process and the published rules decide it there. Does not decide to end a relationship, which is a person, and does not decide to take a stage of a deal back. Does not tell the partner their numbers, which is the partner-manager agent and the partner lead. Does not open or close access on its own; it names what is still open and who still depends on it, and the closing is done by the agents and people the exit names.
These limits are written into the job on purpose, so that everyone adopting the process knows which decisions stay with a person.
Agents built from this plugin
Who has built one, and how far each one got
Nobody has built one yet. The catalog says so rather than leaving the section off, because an empty list is a fact about the document.
declare it
implements: partner-monitor v1
One line in your agent's manifest. The catalog checks it against the records your runs actually leave.
A guess, not a claim
The closest things in the catalog, by description
Nobody above has claimed any of these. This is the nearest match by wording between the job written above and what publishers wrote about their own listings, closest first, and wording is not evidence: some of these will be wrong, and a job with nothing suitable still gets whatever was nearest. The publishers have never heard of this abstract agent and have promised nothing about it. What a claim looks like is in the table above, and it is signed.
Might be reached for
Not workers. These are capability that whatever does the job would use, which is a different relationship and kept in its own column for that reason.
- Pax8 MCP MCP server · servosity.github.io · run it yourself · mirrored from the MCP registry Every Pax8 Partner API endpoint, plus an offline store that reconciles billing, tracks MRR, and
- monitoring MCP server · openhelm.ai · hosted · mirrored from the MCP registry Site & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions.
- Advisors AI Store Readiness Check MCP server · advisorsai.ai · hosted · mirrored from the MCP registry One read-only public-page readiness check with a signed, recheckable evidence receipt.