reynforce

How do I keep the product claims my agents repeat up to date?

Last updated

Give each line one owner and a date by which they will check it again, and make an overdue line unusable until they do. Then the list stays current because going out of date has a consequence, not because somebody remembers.

A product sheet goes out of date as a whole, and nobody notices which sentence went wrong. The certification was renewed, the integration was retired, the uptime figure was from last year — and every agent reading it repeats all three with the same confidence as the day it was written.

One line at a time, with a name on it

What happens when nobody checks

The line reads as overdue the moment its date passes. Nothing has to happen for that: it is worked out from the date, not set by anybody. Every permission that depended on the line switches off with it, and an agent asked about it says it will confirm. The agent did nothing wrong; the information went out of date, and the record says which.

When an owner confirms a line unchanged, its date moves and nothing else does. When they change the wording, it becomes a new version — and promises made under the old one still point at the old wording.

The part we have not measured

Writing a list like this down is an afternoon, measured once. Whether owners keep re-confirming their lines month after month has not been tested with anybody. It is the open half of the question, and the reminder before the date is our guess at what makes it work.

Where the list comes from

Your own pages and documents, split into lines and proposed rather than accepted: somebody still has to stand behind each one. Proposing well — splitting a sentence that says two things, flagging always and never, telling a document's date from the date it was checked — matters more than the typing.

/agent-promise-register.md is what the list is. /findings-register-test.md is the afternoon, measured.