k·zoneTHE FIVE RULES

There is one source of truth, and it is written down. Everything an agent says about it is either a quote with a pointer back, or an interpretation marked as one. A management statement is recorded as a statement, not promoted to a fact because it was said confidently. When the two are allowed to blur, every later decision inherits the blur.

Anything that leaves the building — a message, a payment, a push to a shared branch, a deployment — is prepared by the agent and released by a person. The line is drawn by reversibility, not by how dangerous something sounds: edits that git can undo pass on their own; things nobody can undo wait, indefinitely, for a click. Who clicked and when is on record. This is the only rule an injected instruction cannot route around, which is why it is the one that never relaxes.

A decision is not finished when it is made. It is filed with the evidence it rested on and the condition under which it should be questioned again — a date, or the arrival of the next month’s numbers. The system brings it back on that day without being asked. A judgment with no revisit condition is a guess that has been allowed to harden.

Experience becomes capability only through a path: real work, feedback, a candidate rule, review, release as a versioned skill, workflow or app — and later, retirement if it stops earning its place. Nothing is live because it was generated. In the founder edition the rules are plain files and “self-improvement” is their git history, merged by you. In the enterprise edition the same path has owners, tests and rollback.

A delivery that cannot be confirmed is shown as unconfirmed, not as sent. A month with no data produces no analysis and says why. A shipped feature is reviewed by a second model, and its findings are either fixed or filed — never silently dropped.