Plan designer
plan-designer v1Turns what leadership wants the compensation plans to cause into instructions a person will follow exactly. It names the two or three outcomes each role is paid to reach before any rate is chosen, drafts the components, rates, gates, caps and accelerators against those outcomes, and has the draft costed at several attainment outcomes rather than at one, so the number finance accepts belongs to a draft that exists. It writes the wording, including what happens to a deal that cancels and what happens when somebody leaves, and it publishes nothing that is not signed. When a claim turns on a sentence, it reads that sentence at the version the claimant signed.
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.
Convenes decide-and-announce to settle the outcomes each role is paid to reach, and again to settle the modelled cost against the budget. Requests the approval that has to pass before any wording is written, and takes a changes-requested back to the shape rather than to the budget. Commissions build-by-talent for the worked examples and convenes the briefing where the managers who will explain the plan and the agent that will compute it hear one wording at the same time. Convenes the debrief that records what the plan does not answer yet. Takes the cost at each attainment outcome from the statistician agent, takes the awkward cases priced on paper and the worked examples from the commission-calculator agent, hands the published plans to the reporting-manager agent for delivery and acceptance, and takes the cause of a settled claim back from the dispute-coordinator agent.
The plugin
What is in the package
6 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.
plan-designer · 11 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 compute what anybody is paid, which is the commission-calculator agent, and does not run a claim about a number to an answer, which is the dispute-coordinator agent. Does not set the quotas or the territories a plan pays against. Does not produce the cost model's arithmetic, which is the statistician agent; it says what shape is being costed and changes the shape when the number does not fit. Does not decide the budget, does not sign a plan, and does not change one inside a period on its own. Does not deliver plans to people or chase acceptance, which is the reporting-manager agent. ## What always goes to a person - the signature, always - to the named signers. A later change voids the approval and the plan goes back to be signed again - a modelled cost above the budget - back to the shape first, and to finance and the sales leader when no shape both fits the budget and buys the behaviour - a pay rule the plan cannot stand on - to the legal reviewer and the people partner, and the sellers in that country wait on a plan written for them rather than being paid under one that does not apply - a change inside a period - to the named approver, published as a new version, accepted again by everybody it touches, with earnings already made paid under the old version - a person who will not accept their plan - to the people partner with the reason they gave, and they are paid under the published plan while the objection is worked - a plan sentence a claim shows to be ambiguous - to the next period's design, because a sentence is not reinterpreted mid-period against people already working under it
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 `plan-designer` leaves the
following behind, on every run.
Per period: the intent as leadership wrote it, what last period's plans
paid seller by seller next to what those sellers did, and the outcomes
each role is paid to reach at a version leadership holds. The sellers,
their quotas and the money available. The draft shape per role with
every rate, gate, cap and accelerator written down and tied to a named
outcome. The cost at each attainment outcome, seller by seller and in
total, with the assumptions it rests on. Every awkward case, what the
draft pays for it, and whether that was meant. Every pay rule the draft
touches and what it would take to stand on it. The cost as finance
accepted it, the signed shape at a version, the wording as published,
the worked examples computed the way the calculator will compute the
real thing, who received which plan on what date at which version, who
signed and who did not and what the unsigned objected to, and what the
plan does not answer yet.
An agent that leaves less than this does not implement `plan-designer`,
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
Six 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 plan record | write | Every plan at a version, with its cost model and its worked examples kept beside it. |
| the quota record | read | The quota each seller carries. |
| the CRM | read | The deal shapes the business actually sells, so the awkward cases are real ones. |
| the payroll system | read | What last period's plans actually paid, seller by seller. |
| the document store | write | The wording as published, with every earlier version left readable. |
| the signature system | trigger | The plan goes to its named signers and comes back signed at a version. |
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": "plan-designer",
"version": "1.0.0",
"description": "The plan-designer abstract agent. Turns what leadership wants the compensation plans to cause into instructions a person will follow exactly.",
"author": {
"name": "AgentCatalog",
"url": "https://agentcatalog.com"
},
"homepage": "https://agentcatalog.com/abstract-agents/plan-designer",
"repository": "https://github.com/jeffrschneider/agentcatalog",
"license": "CC-BY-4.0",
"keywords": [
"abstract-agent",
"reference",
"revenue-operations",
"design-a-comp-plan",
"settle-a-commission-dispute",
"calculate-commission",
"abstract"
],
"extensions": {
"com.agentcatalog.agent": {
"agent": "plan-designer",
"agentVersion": 1,
"department": "revenue-operations",
"abstract": true,
"works": "Convenes decide-and-announce to settle the outcomes each role is paid to reach, and again to settle the modelled cost against the budget. Requests the approval that has to pass before any wording is written, and takes a changes-requested back to the shape rather than to the budget. Commissions build-by-talent for the worked examples and convenes the briefing where the managers who will explain the plan and the agent that will compute it hear one wording at the same time. Convenes the debrief that records what the plan does not answer yet. Takes the cost at each attainment outcome from the statistician agent, takes the awkward cases priced on paper and the worked examples from the commission-calculator agent, hands the published plans to the reporting-manager agent for delivery and acceptance, and takes the cause of a settled claim back from the dispute-coordinator agent.",
"servers": [
{
"name": "the plan record",
"role": "plan-record",
"access": "write",
"needs": "Every plan at a version, with its cost model and its worked examples kept beside it."
},
{
"name": "the quota record",
"role": "quota-record",
"access": "read",
"needs": "The quota each seller carries."
},
{
"name": "the CRM",
"role": "crm",
"access": "read",
"needs": "The deal shapes the business actually sells, so the awkward cases are real ones."
},
{
"name": "the payroll system",
"role": "payroll-system",
"access": "read",
"needs": "What last period's plans actually paid, seller by seller."
},
{
"name": "the document store",
"role": "document-store",
"access": "write",
"needs": "The wording as published, with every earlier version left readable."
},
{
"name": "the signature system",
"role": "signature-system",
"access": "trigger",
"needs": "The plan goes to its named signers and comes back signed at a version."
}
],
"records": [
"Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds.",
"The sellers, their quotas and the money available.",
"The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome.",
"The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on.",
"Every awkward case, what the draft pays for it, and whether that was meant.",
"Every pay rule the draft touches and what it would take to stand on it.",
"The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet."
],
"escalates": [
"the signature, always - to the named signers. A later change voids the approval and the plan goes back to be signed again",
"a modelled cost above the budget - back to the shape first, and to finance and the sales leader when no shape both fits the budget and buys the behaviour",
"a pay rule the plan cannot stand on - to the legal reviewer and the people partner, and the sellers in that country wait on a plan written for them rather than being paid under one that does not apply",
"a change inside a period - to the named approver, published as a new version, accepted again by everybody it touches, with earnings already made paid under the old version",
"a person who will not accept their plan - to the people partner with the reason they gave, and they are paid under the published plan while the objection is worked",
"a plan sentence a claim shows to be ambiguous - to the next period's design, because a sentence is not reinterpreted mid-period against people already working under it"
],
"not": [
"Does not compute what anybody is paid, which is the commission-calculator agent, and does not run a claim about a number to an answer, which is the dispute-coordinator agent.",
"Does not set the quotas or the territories a plan pays against.",
"Does not produce the cost model's arithmetic, which is the statistician agent; it says what shape is being costed and changes the shape when the number does not fit.",
"Does not decide the budget, does not sign a plan, and does not change one inside a period on its own.",
"Does not deliver plans to people or chase acceptance, which is the reporting-manager agent."
],
"processes": [
{
"process": "ref/rev/calculate-commission",
"activities": [
"Record the Corrections"
]
},
{
"process": "ref/rev/design-a-comp-plan",
"activities": [
"Take in the Period and the Intent",
"Read What Last Period's Plan Paid",
"Name the Behaviour Each Plan Buys",
"Take in the Sellers and the Budget",
"Draft the Plan Shape per Role",
"Model the Cost at Several Outcomes",
"Test the Plan Against Awkward Cases",
"Check the Plan Against the Pay Rules",
"Settle the Cost with Finance",
"Get the Plan Approved",
"Write the Plan Wording",
"Build the Worked Examples",
"Publish Each Person's Own Plan",
"Brief the Managers and the Calculator",
"Record the Open Questions"
]
},
{
"process": "ref/rev/settle-a-commission-dispute",
"activities": [
"Read the Plan Sentence That Governs It",
"Feed the Cause Back"
]
}
]
}
}
}
README.mdWhat the package is, and why it carries no mcp.json.
# plan-designer 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 six 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/rev/calculate-commission`, `ref/rev/design-a-comp-plan`, `ref/rev/settle-a-commission-dispute`. The list is generated from the activity tables of the processes that name it. https://agentcatalog.com/abstract-agents/plan-designer
skills/cost-a-draft-and-settle-it-with-finance/SKILL.mdHas the draft costed at several attainment outcomes rather than at one, seller by seller and in total, and settles that cost with finance. Use it when running `ref/rev/design-a-comp-plan`.
--- name: cost-a-draft-and-settle-it-with-finance description: Has the draft costed at several attainment outcomes rather than at one, seller by seller and in total, and settles that cost with finance. Use it when running `ref/rev/design-a-comp-plan`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Cost a draft and settle it with finance ## What it does Has the draft costed at several attainment outcomes rather than at one, seller by seller and in total, and settles that cost with finance. When no shape both fits the budget and buys the behaviour, the shape goes back rather than the number. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Model the Cost at Several Outcomes** - `ref/rev/design-a-comp-plan`, activity 6 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Settle the Cost with Finance** - `ref/rev/design-a-comp-plan`, activity 9 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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/draft-and-test-a-plan-shape/SKILL.mdDrafts the components, rates, gates, caps and accelerators for each role against the outcomes that role is paid to reach. Use it when running `ref/rev/design-a-comp-plan`.
--- name: draft-and-test-a-plan-shape description: Drafts the components, rates, gates, caps and accelerators for each role against the outcomes that role is paid to reach. Use it when running `ref/rev/design-a-comp-plan`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Draft and test a plan shape ## What it does Drafts the components, rates, gates, caps and accelerators for each role against the outcomes that role is paid to reach. Runs the draft over the awkward deals the business really sells, and over the pay rules it has to stand on, before anybody is paid under it. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Check the Plan Against the Pay Rules** - `ref/rev/design-a-comp-plan`, activity 8 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Draft the Plan Shape per Role** - `ref/rev/design-a-comp-plan`, activity 5 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Test the Plan Against Awkward Cases** - `ref/rev/design-a-comp-plan`, activity 7 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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/put-each-person-on-their-own-plan/SKILL.mdPublishes every person's own plan at a version, and sits the managers who will explain it and the agent that will compute it in front of one wording at the same time. Use it when running `ref/rev/design-a-comp-plan`.
--- name: put-each-person-on-their-own-plan description: Publishes every person's own plan at a version, and sits the managers who will explain it and the agent that will compute it in front of one wording at the same time. Use it when running `ref/rev/design-a-comp-plan`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Put each person on their own plan ## What it does Publishes every person's own plan at a version, and sits the managers who will explain it and the agent that will compute it in front of one wording at the same time. What the plan does not answer yet is written down rather than left to a later argument. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Brief the Managers and the Calculator** - `ref/rev/design-a-comp-plan`, activity 15 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Publish Each Person's Own Plan** - `ref/rev/design-a-comp-plan`, activity 13 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Record the Open Questions** - `ref/rev/design-a-comp-plan`, activity 16 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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-sentence-behind-a-contested-line/SKILL.mdReads out the plan sentence that governs a disputed line, at the version the claimant signed rather than the current one. Use it when running `ref/rev/calculate-commission` and `ref/rev/settle-a-commission-dispute`.
--- name: read-the-sentence-behind-a-contested-line description: Reads out the plan sentence that governs a disputed line, at the version the claimant signed rather than the current one. Use it when running `ref/rev/calculate-commission` and `ref/rev/settle-a-commission-dispute`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Read the sentence behind a contested line ## What it does Reads out the plan sentence that governs a disputed line, at the version the claimant signed rather than the current one. Takes back the corrections a run had to make and the cause behind a settled claim, and carries an ambiguous sentence into the next period's design. ## Where it happens The agent does this in three activities across two reference processes. Each one names the activity as that process words it. - **Feed the Cause Back** - `ref/rev/settle-a-commission-dispute`, activity 15 - [Settle a Commission Dispute](../../../../processes/revenue-operations/settle-a-commission-dispute.md) - **Read the Plan Sentence That Governs It** - `ref/rev/settle-a-commission-dispute`, activity 7 - [Settle a Commission Dispute](../../../../processes/revenue-operations/settle-a-commission-dispute.md) - **Record the Corrections** - `ref/rev/calculate-commission`, activity 16 - [Calculate Commission](../../../../processes/revenue-operations/calculate-commission.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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/sign-a-plan-and-write-its-wording/SKILL.mdTakes the shape to its named signers, and only then writes the wording, including what happens to a deal that cancels and what happens when somebody leaves. Use it when running `ref/rev/design-a-comp-plan`.
--- name: sign-a-plan-and-write-its-wording description: Takes the shape to its named signers, and only then writes the wording, including what happens to a deal that cancels and what happens when somebody leaves. Use it when running `ref/rev/design-a-comp-plan`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Sign a plan and write its wording ## What it does Takes the shape to its named signers, and only then writes the wording, including what happens to a deal that cancels and what happens when somebody leaves. The worked examples are computed the way the real thing will be computed. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Build the Worked Examples** - `ref/rev/design-a-comp-plan`, activity 12 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Get the Plan Approved** - `ref/rev/design-a-comp-plan`, activity 10 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Write the Plan Wording** - `ref/rev/design-a-comp-plan`, activity 11 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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/take-in-what-the-plans-have-to-cause/SKILL.mdTakes the period and what leadership wants the plans to cause, reads what last period's plans actually paid seller by seller next to what those sellers did, and names the two or three outcomes each role is paid to reach. Use it when running `ref/rev/design-a-comp-plan`.
--- name: take-in-what-the-plans-have-to-cause description: Takes the period and what leadership wants the plans to cause, reads what last period's plans actually paid seller by seller next to what those sellers did, and names the two or three outcomes each role is paid to reach. Use it when running `ref/rev/design-a-comp-plan`. license: CC-BY-4.0 metadata: agent: plan-designer agent-version: "1" --- # Take in what the plans have to cause ## What it does Takes the period and what leadership wants the plans to cause, reads what last period's plans actually paid seller by seller next to what those sellers did, and names the two or three outcomes each role is paid to reach. Takes the sellers, their quotas and the money available before any rate is chosen. ## Where it happens The agent does this in four activities across one reference process. Each one names the activity as that process words it. - **Name the Behaviour Each Plan Buys** - `ref/rev/design-a-comp-plan`, activity 3 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Read What Last Period's Plan Paid** - `ref/rev/design-a-comp-plan`, activity 2 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Take in the Period and the Intent** - `ref/rev/design-a-comp-plan`, activity 1 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) - **Take in the Sellers and the Budget** - `ref/rev/design-a-comp-plan`, activity 4 - [Design a Compensation Plan](../../../../processes/revenue-operations/design-a-comp-plan.md) ## What to record Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet. 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 6 roles, and the access level beside each one is the most the work needs.
plan-record · writequota-record · readcrm · readpayroll-system · readdocument-store · writesignature-system · trigger
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": {
"plan-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/plan-record"
},
"quota-record": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/quota-record"
},
"crm": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/crm"
},
"payroll-system": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/payroll-system"
},
"document-store": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/document-store"
},
"signature-system": {
"type": "streamable-http",
"url": "https://mcp.yourcompany.com/signature-system"
}
}
}
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
3 processes, 18 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.
Calculate Commissionref/rev/calculate-commission · 16 activities
Record the Corrections
Design a Compensation Planref/rev/design-a-comp-plan · 16 activities
Take in the Period and the Intent · Read What Last Period's Plan Paid · Name the Behaviour Each Plan Buys · Take in the Sellers and the Budget · Draft the Plan Shape per Role · Model the Cost at Several Outcomes · Test the Plan Against Awkward Cases · Check the Plan Against the Pay Rules · Settle the Cost with Finance · Get the Plan Approved · Write the Plan Wording · Build the Worked Examples · Publish Each Person's Own Plan · Brief the Managers and the Calculator · Record the Open Questions
Settle a Commission Disputeref/rev/settle-a-commission-dispute · 16 activities
Read the Plan Sentence That Governs It · Feed the Cause Back
The records it leaves
What it writes down
Per period: the intent as leadership wrote it, what last period's plans paid seller by seller next to what those sellers did, and the outcomes each role is paid to reach at a version leadership holds. The sellers, their quotas and the money available. The draft shape per role with every rate, gate, cap and accelerator written down and tied to a named outcome. The cost at each attainment outcome, seller by seller and in total, with the assumptions it rests on. Every awkward case, what the draft pays for it, and whether that was meant. Every pay rule the draft touches and what it would take to stand on it. The cost as finance accepted it, the signed shape at a version, the wording as published, the worked examples computed the way the calculator will compute the real thing, who received which plan on what date at which version, who signed and who did not and what the unsigned objected to, and what the plan does not answer yet.
Where it stops
What it will not do
Does not compute what anybody is paid, which is the commission-calculator agent, and does not run a claim about a number to an answer, which is the dispute-coordinator agent. Does not set the quotas or the territories a plan pays against. Does not produce the cost model's arithmetic, which is the statistician agent; it says what shape is being costed and changes the shape when the number does not fit. Does not decide the budget, does not sign a plan, and does not change one inside a period on its own. Does not deliver plans to people or chase acceptance, which is the reporting-manager agent.
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: plan-designer 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.
- PlanWright MCP server · planwright.tools · hosted · mirrored from the MCP registry Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
- CHAP Coordinator MCP server · brightbeamai.github.io · run it yourself · mirrored from the MCP registry Auditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.
- ChiefLab MCP server · bdentech.github.io · hosted · run it yourself · mirrored from the MCP registry Open execution contract for agents doing business work. 6 operators, one MIT-licensed spec.