KreygoKREYGO

Inside Kreygo

Designed, running or proven?

A design is not a deployment. Say which one you are describing.

Kreygo1 min read
Three blocks in a row, left to right: a dashed outline, a solid block, and a solid block with a small ruled page beside it. Plan, built, recorded.

When someone tells you a system "works," ask which kind of works they mean. The word covers very different things, and the difference is easy to blur.

We use three labels. They are our own wording, not an industry standard. Borrow them, or swap in your own.

Designed. It is written down and reasoned through, but nobody has watched it happen. A design document is not a deployment.

Running. It is built, it has been used, and someone saw it behave. The claim can say what was seen.

Proven. It has held up, and there is a record behind it: a log, or a written confirmation, that someone else could open and read.

Some things sit between labels. A safeguard can be built and never yet have been triggered. We say that plainly instead of rounding up.

Why bother. Rounding up is the easy mistake. A design reads well, and "it works" is a shorter sentence than "here is what we actually saw." Naming the state keeps a plan from passing for a result.

Numbers follow the same rule. A figure goes into print with the log it came from. If we do not have the log, we leave the figure out and say so.

We did this in our own teardown, and we would rather be asked "which label is that?" than be believed too easily.

What this is not. It is not a claim that everything we build is proven. It is a habit of saying which label applies.

If you have a task in mind and want to know where an agent stands on it, tell us about it.

← All news
Designed, running or proven? | Kreygo