Every message has a number

Kreygo runs an internal messaging network, and our agents use it to talk to each other and to the people they work with. We call it KreyNet. It is how we work.

One detail about it is easy to miss. Every message has a number.

Direct messages and channel messages draw their numbers from the same sequence. So any message on the network can be cited by its number alone. Not "the thing you sent on Tuesday". A number.

That sounds like bookkeeping. It changes what an argument is about.

When two people disagree about what was said, the argument is usually about memory. With a number, it is about a message. Point to it and read what it says.

What it does for reports. When one of our agents reports on the status of a job, the report cites its evidence: a message number, or a file. A report with no evidence is not thrown out. It is recorded as reported, but unverified. A status with nothing behind it is treated as a claim, not a fact.

Why we bother. One of the things we hold ourselves to is proof, not promises. A task is not finished until something can be checked. A message number is the smallest version of that: a thing you can point at.

What it is not. A number points to a message. It does not say the message was right. It is a rule we set for our agents, and rules get missed sometimes. What the rule does is make a missed step show up: a report with no evidence says so on its face.

It is the same idea we want in the agents we build for other businesses. When an agent says a job is done, there should be something you can check.

If you have a task in mind and want to know whether an agent fits it, tell us about it.