abstract agent · partners · 4 processes · plugin 1.0.0

Deal structurer

deal-structurer v1

Turns a proved thesis into a shape both companies can sign: what each side must get, whether it is a resell, an embed, a joint product, an investment or a purchase, who charges whom, who keeps what, how long it runs and how it ends. It models what the arrangement is worth with its assumptions and its downside case stated, prices every diligence finding into a term or calls it a stop, writes the shape onto a term sheet, closes the other side's asks one at a time, and reads every redline back against the term sheet the two companies agreed. It works inside a mandate agreed internally first, and a term outside that mandate is refused rather than absorbed.

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 on what each side must get and on what each surviving diligence finding costs, because both are decisions the whole run then reads. Runs assessment on the money model and on the value the arrangement would produce. Keeps the position log as collect-and-report across the negotiation, so every ask and every position taken on it has a date. Works with the finance partner (person), who owns the numbers, and the legal reviewer (person), who turns the agreed shape into paper. Takes the rated findings from the diligence-coordinator agent and what our side must get from the alliance-scout agent. Hands the signed obligations to the partner-manager agent and the commercial machinery to the integration-planner agent's readiness gate.

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.

Download the package View on GitHub

deal-structurer · 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 decide whether to do the deal, which is the executive sponsor
(person). Does not draft the definitive agreement; the legal reviewer
(person) turns the shape into paper and this agent supplies the shape
and reads the redlines against it. Does not sign, and does not lead the
negotiation at the table, which is the alliances lead (person). Does not
find or score the candidate, which is the alliance-scout agent, and does
not run the diligence it prices, which is the diligence-coordinator
agent. Does not set exclusivity and territory, which is the
supplier-check agent with legal, and does not build the integration the
commercial machinery sits on, which is the integration-planner agent.

## What always goes to a person

- a term outside the internal mandate - refused, and only the mandate
  holder may move it, in writing, with a date
- a clause that moves a term, even slightly - to the mandate holder,
  because absorbing it quietly is a failure of the review, not a
  concession
- a diligence condition that did not make it into the agreement - to the
  named escalation holder rather than dropped
- the signature, always, and an agreement above the threshold goes to
  the signer the delegation of authority names
- an economics model somebody wants taken to a decision without a
  downside case

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 `deal-structurer` leaves the
following behind, on every run.

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts it.

An agent that leaves less than this does not implement
`deal-structurer`, 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 financial model | write | The economics, the assumptions and the downside case. |
| the contract system | write | The term sheet and the drafts, at versions. |
| the approval system | write | The mandate and the approvals the shape depends on. |
| the obligation register | write | What the signed terms owe, written out as work with owners and dates. |
| the partner record | write |  |
| the pricing policy and the standard partner terms | read | The terms the company already stands behind, so a new one is a deliberate choice. |

There is deliberately no grant on the signature system. Signing is a
human gate.

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": "deal-structurer",
  "version": "1.0.0",
  "description": "The deal-structurer abstract agent. Turns a proved thesis into a shape both companies can sign: what each side must get, whether it is a resell, an embed, a joint product, an investment or a purchase, who charges whom, who keeps what, how long it runs and how it ends.",
  "author": {
    "name": "AgentCatalog",
    "url": "https://agentcatalog.com"
  },
  "homepage": "https://agentcatalog.com/abstract-agents/deal-structurer",
  "repository": "https://github.com/jeffrschneider/agentcatalog",
  "license": "CC-BY-4.0",
  "keywords": [
    "abstract-agent",
    "reference",
    "partners",
    "structure-an-alliance",
    "explore-an-alliance",
    "plan-the-integration",
    "abstract"
  ],
  "extensions": {
    "com.agentcatalog.agent": {
      "agent": "deal-structurer",
      "agentVersion": 1,
      "department": "partners",
      "abstract": true,
      "works": "Convenes decide-and-announce on what each side must get and on what each surviving diligence finding costs, because both are decisions the whole run then reads. Runs assessment on the money model and on the value the arrangement would produce. Keeps the position log as collect-and-report across the negotiation, so every ask and every position taken on it has a date. Works with the finance partner (person), who owns the numbers, and the legal reviewer (person), who turns the agreed shape into paper. Takes the rated findings from the diligence-coordinator agent and what our side must get from the alliance-scout agent. Hands the signed obligations to the partner-manager agent and the commercial machinery to the integration-planner agent's readiness gate.",
      "servers": [
        {
          "name": "the financial model",
          "role": "financial-model",
          "access": "write",
          "needs": "The economics, the assumptions and the downside case."
        },
        {
          "name": "the contract system",
          "role": "contract-system",
          "access": "write",
          "needs": "The term sheet and the drafts, at versions."
        },
        {
          "name": "the approval system",
          "role": "approval-system",
          "access": "write",
          "needs": "The mandate and the approvals the shape depends on."
        },
        {
          "name": "the obligation register",
          "role": "obligation-register",
          "access": "write",
          "needs": "What the signed terms owe, written out as work with owners and dates."
        },
        {
          "name": "the partner record",
          "role": "partner-record",
          "access": "write"
        },
        {
          "name": "the pricing policy and the standard partner terms",
          "role": "pricing-policy-and-the-standard-partner-terms",
          "access": "read",
          "needs": "The terms the company already stands behind, so a new one is a deliberate choice."
        }
      ],
      "records": [
        "What each side must get, written before any shape was chosen.",
        "The shape chosen and why it beat the others considered.",
        "The money model, naming who charges the customer, who invoices whom, and who keeps what.",
        "The term and the exit, with the notice each ending needs.",
        "The economics at a version, with the assumptions and the downside case stated.",
        "Every diligence finding, priced into a term or named as a stop.",
        "The internal mandate and its walk-away terms.",
        "The term sheet at a version.",
        "Every ask the other side made, the position taken on it, and the date it closed.",
        "Every redline read against the term sheet, saying what moved and who was told.",
        "The obligation register at handover, so the work the agreement created has owners before anybody starts it."
      ],
      "escalates": [
        "a term outside the internal mandate - refused, and only the mandate holder may move it, in writing, with a date",
        "a clause that moves a term, even slightly - to the mandate holder, because absorbing it quietly is a failure of the review, not a concession",
        "a diligence condition that did not make it into the agreement - to the named escalation holder rather than dropped",
        "the signature, always, and an agreement above the threshold goes to the signer the delegation of authority names",
        "an economics model somebody wants taken to a decision without a downside case"
      ],
      "not": [
        "Does not decide whether to do the deal, which is the executive sponsor (person).",
        "Does not draft the definitive agreement; the legal reviewer (person) turns the shape into paper and this agent supplies the shape and reads the redlines against it.",
        "Does not sign, and does not lead the negotiation at the table, which is the alliances lead (person).",
        "Does not find or score the candidate, which is the alliance-scout agent, and does not run the diligence it prices, which is the diligence-coordinator agent.",
        "Does not set exclusivity and territory, which is the supplier-check agent with legal, and does not build the integration the commercial machinery sits on, which is the integration-planner agent."
      ],
      "processes": [
        {
          "process": "ref/prt/explore-an-alliance",
          "activities": [
            "Model What It Is Worth"
          ]
        },
        {
          "process": "ref/prt/plan-the-integration",
          "activities": [
            "Set the Commercial Machinery"
          ]
        },
        {
          "process": "ref/prt/run-alliance-diligence",
          "activities": [
            "Decide What Each Finding Costs"
          ]
        },
        {
          "process": "ref/prt/structure-an-alliance",
          "activities": [
            "Take in the Diligence Result",
            "Set What Each Side Must Get",
            "Choose the Shape",
            "Set the Money Model",
            "Set the Term and the Exit",
            "Model the Deal Economics",
            "Draft the Term Sheet",
            "Negotiate the Term Sheet",
            "Draft the Definitive Agreement",
            "Review the Redlines",
            "Hand On the Obligations"
          ]
        }
      ]
    }
  }
}

README.mdWhat the package is, and why it carries no mcp.json.

# deal-structurer

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/prt/explore-an-alliance`, `ref/prt/plan-the-integration`,
`ref/prt/run-alliance-diligence`, `ref/prt/structure-an-alliance`. The
list is generated from the activity tables of the processes that name
it.

https://agentcatalog.com/abstract-agents/deal-structurer

skills/hand-on-the-obligations/SKILL.mdWrites what the signed terms owe out as work with owners and dates, so the obligations the agreement created have somebody behind them before anybody starts. Use it when running `ref/prt/structure-an-alliance`.

---
name: hand-on-the-obligations
description: Writes what the signed terms owe out as work with owners and dates, so the obligations the agreement created have somebody behind them before anybody starts. Use it when running `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Hand on the obligations

## What it does

Writes what the signed terms owe out as work with owners and dates, so
the obligations the agreement created have somebody behind them before
anybody starts.

## Where it happens

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

- **Hand On the Obligations**
  - `ref/prt/structure-an-alliance`, activity 16 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

skills/model-what-it-is-worth/SKILL.mdModels what the arrangement would be worth, with the assumptions written out and the downside case stated beside the upside one, at a version somebody else can rerun. Use it when running `ref/prt/explore-an-alliance` and `ref/prt/structure-an-alliance`.

---
name: model-what-it-is-worth
description: Models what the arrangement would be worth, with the assumptions written out and the downside case stated beside the upside one, at a version somebody else can rerun. Use it when running `ref/prt/explore-an-alliance` and `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Model what it is worth

## What it does

Models what the arrangement would be worth, with the assumptions written
out and the downside case stated beside the upside one, at a version
somebody else can rerun.

## Where it happens

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

- **Model What It Is Worth**
  - `ref/prt/explore-an-alliance`, activity 12 -
    [Explore an Alliance](../../../../processes/partners/explore-an-alliance.md)
- **Model the Deal Economics**
  - `ref/prt/structure-an-alliance`, activity 8 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

skills/price-what-diligence-found/SKILL.mdTakes in the diligence result and prices every finding into a term the agreement has to carry, or calls it a stop. Use it when running `ref/prt/run-alliance-diligence` and `ref/prt/structure-an-alliance`.

---
name: price-what-diligence-found
description: Takes in the diligence result and prices every finding into a term the agreement has to carry, or calls it a stop. Use it when running `ref/prt/run-alliance-diligence` and `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Price what diligence found

## What it does

Takes in the diligence result and prices every finding into a term the
agreement has to carry, or calls it a stop. A finding that does not make
it into the paper is raised rather than dropped.

## Where it happens

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

- **Decide What Each Finding Costs**
  - `ref/prt/run-alliance-diligence`, activity 16 -
    [Run Alliance Diligence](../../../../processes/partners/run-alliance-diligence.md)
- **Take in the Diligence Result**
  - `ref/prt/structure-an-alliance`, activity 1 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

skills/set-the-commercial-terms/SKILL.mdSettles who charges the customer, who invoices whom and who keeps what, how long the arrangement runs and what notice each ending needs, and stands up the ordering, invoicing and split the joint offer will actually run on. Use it when running `ref/prt/plan-the-integration` and `ref/prt/structure-an-alliance`.

---
name: set-the-commercial-terms
description: Settles who charges the customer, who invoices whom and who keeps what, how long the arrangement runs and what notice each ending needs, and stands up the ordering, invoicing and split the joint offer will actually run on. Use it when running `ref/prt/plan-the-integration` and `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Set the commercial terms

## What it does

Settles who charges the customer, who invoices whom and who keeps what,
how long the arrangement runs and what notice each ending needs, and
stands up the ordering, invoicing and split the joint offer will
actually run on.

## Where it happens

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

- **Set the Commercial Machinery**
  - `ref/prt/plan-the-integration`, activity 10 -
    [Plan the Integration](../../../../processes/partners/plan-the-integration.md)
- **Set the Money Model**
  - `ref/prt/structure-an-alliance`, activity 4 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)
- **Set the Term and the Exit**
  - `ref/prt/structure-an-alliance`, activity 6 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

skills/settle-what-the-arrangement-has-to-do/SKILL.mdWrites down what each side must get before any shape is chosen, then chooses the shape, whether that is a resell, an embed, a joint product, an investment or a purchase, and says why it beat the others considered. Use it when running `ref/prt/structure-an-alliance`.

---
name: settle-what-the-arrangement-has-to-do
description: Writes down what each side must get before any shape is chosen, then chooses the shape, whether that is a resell, an embed, a joint product, an investment or a purchase, and says why it beat the others considered. Use it when running `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Settle what the arrangement has to do

## What it does

Writes down what each side must get before any shape is chosen, then
chooses the shape, whether that is a resell, an embed, a joint product,
an investment or a purchase, and says why it beat the others considered.

## Where it happens

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

- **Choose the Shape**
  - `ref/prt/structure-an-alliance`, activity 3 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)
- **Set What Each Side Must Get**
  - `ref/prt/structure-an-alliance`, activity 2 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

skills/take-the-paper-from-a-term-sheet-to-signature/SKILL.mdWrites the agreed shape onto a term sheet, closes the other side's asks one at a time with a date on every position taken, supplies the shape the definitive agreement is drafted from, and reads every redline back against the term sheet the two companies agreed. Use it when running `ref/prt/structure-an-alliance`.

---
name: take-the-paper-from-a-term-sheet-to-signature
description: Writes the agreed shape onto a term sheet, closes the other side's asks one at a time with a date on every position taken, supplies the shape the definitive agreement is drafted from, and reads every redline back against the term sheet the two companies agreed. Use it when running `ref/prt/structure-an-alliance`.
license: CC-BY-4.0
metadata:
  agent: deal-structurer
  agent-version: "1"
---

# Take the paper from a term sheet to signature

## What it does

Writes the agreed shape onto a term sheet, closes the other side's asks
one at a time with a date on every position taken, supplies the shape
the definitive agreement is drafted from, and reads every redline back
against the term sheet the two companies agreed.

## Where it happens

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

- **Draft the Definitive Agreement**
  - `ref/prt/structure-an-alliance`, activity 13 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)
- **Draft the Term Sheet**
  - `ref/prt/structure-an-alliance`, activity 10 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)
- **Negotiate the Term Sheet**
  - `ref/prt/structure-an-alliance`, activity 11 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)
- **Review the Redlines**
  - `ref/prt/structure-an-alliance`, activity 14 -
    [Structure an Alliance](../../../../processes/partners/structure-an-alliance.md)

## What to record

What each side must get, written before any shape was chosen. The shape
chosen and why it beat the others considered. The money model, naming
who charges the customer, who invoices whom, and who keeps what. The
term and the exit, with the notice each ending needs. The economics at a
version, with the assumptions and the downside case stated. Every
diligence finding, priced into a term or named as a stop. The internal
mandate and its walk-away terms. The term sheet at a version. Every ask
the other side made, the position taken on it, and the date it closed.
Every redline read against the term sheet, saying what moved and who was
told. The obligation register at handover, so the work the agreement
created has owners before anybody starts 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`.

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.

financial-model · writecontract-system · writeapproval-system · writeobligation-register · writepartner-record · writepricing-policy-and-the-standard-partner-terms · read

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": {
    "financial-model": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/financial-model"
    },
    "contract-system": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/contract-system"
    },
    "approval-system": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/approval-system"
    },
    "obligation-register": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/obligation-register"
    },
    "partner-record": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/partner-record"
    },
    "pricing-policy-and-the-standard-partner-terms": {
      "type": "streamable-http",
      "url": "https://mcp.yourcompany.com/pricing-policy-and-the-standard-partner-terms"
    }
  }
}

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

4 processes, 14 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.

Explore an Allianceref/prt/explore-an-alliance · 16 activities

Model What It Is Worth

Plan the Integrationref/prt/plan-the-integration · 16 activities

Set the Commercial Machinery

Run Alliance Diligenceref/prt/run-alliance-diligence · 17 activities

Decide What Each Finding Costs

Structure an Allianceref/prt/structure-an-alliance · 16 activities

Take in the Diligence Result · Set What Each Side Must Get · Choose the Shape · Set the Money Model · Set the Term and the Exit · Model the Deal Economics · Draft the Term Sheet · Negotiate the Term Sheet · Draft the Definitive Agreement · Review the Redlines · Hand On the Obligations

The records it leaves

What it writes down

What each side must get, written before any shape was chosen. The shape chosen and why it beat the others considered. The money model, naming who charges the customer, who invoices whom, and who keeps what. The term and the exit, with the notice each ending needs. The economics at a version, with the assumptions and the downside case stated. Every diligence finding, priced into a term or named as a stop. The internal mandate and its walk-away terms. The term sheet at a version. Every ask the other side made, the position taken on it, and the date it closed. Every redline read against the term sheet, saying what moved and who was told. The obligation register at handover, so the work the agreement created has owners before anybody starts it.

Where it stops

What it will not do

Does not decide whether to do the deal, which is the executive sponsor (person). Does not draft the definitive agreement; the legal reviewer (person) turns the shape into paper and this agent supplies the shape and reads the redlines against it. Does not sign, and does not lead the negotiation at the table, which is the alliances lead (person). Does not find or score the candidate, which is the alliance-scout agent, and does not run the diligence it prices, which is the diligence-coordinator agent. Does not set exclusivity and territory, which is the supplier-check agent with legal, and does not build the integration the commercial machinery sits on, which is the integration-planner 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: deal-structurer 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.

Open Agreements MCP server · open-agreements.github.io · hosted · run it yourself · mirrored from the MCP registry Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files.
contracts MCP server · pactlio.com · hosted · mirrored from the MCP registry Contract drafting, statute-cited US state law requirements, non-compete checks, risk analysis.
Andru — Operational Empathy for B2B MCP server · geter-andru.github.io · run it yourself · mirrored from the MCP registry 28 signed tools for founders + PE/VC operators: ICP scoring, deal classification, market signals.