change-terms
Records the terms the change runs under before any customer is sorted: the approved new prices, the grandfathering rules that hold a customer at an old price, and the notice period each customer is ow
SKILL.mdplugins/price-transition/skills/change-terms/SKILL.md
GitHubChange terms
What it does
Records the terms the change runs under before any customer is sorted: the approved new prices, the grandfathering rules that hold a customer at an old price, and the notice period each customer is owed.
Where it happens
The agent does this in one activity across one reference process. Each one names the activity as that process words it.
- Set the Terms of the Change
ref/mkt/pricing-change, activity 3 - Launch Pricing Change
What to record
The register at a version, giving for each customer what they pay now, what the new prices make them pay, the amount and the share of the change, the grandfathering rule that caught them and the date that rule runs out, the notice they are owed, and the earliest date their change may take effect. A dated line for every notice served, naming the customer, the version of the wording that went, the date it went, the route it went by, and the date its waiting time runs out. A dated line for every price change released, naming the customer, the date the new price takes effect, and the notice record that cleared it. A customer it could not sort is recorded as unsorted, with what is missing, rather than being left out of the register. A change it is holding back is recorded as held, with the reason and the number of days it has been held.
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.