MyJackfruit

Help
Browse topics · Standards an agent follows

Standards an agent follows

← Standards an agent follows

Why does Kai-Zen stop and ask, or follow a standard?

Short answer

Kai-Zen follows its standards: it asks only what they leave to you, stops before acts they keep for you, and decides the rest itself.

Deeper

Also asked:

Why does Kai-Zen stop and wait for me? It asks once, at the start, about what only you know, and then stops only before acts it never does without you, such as putting work live, ending a record, giving access, spending over the budget or changing a Value you set.

Why does an agent follow its standard instead of just doing what I say? Its standard is its way of working. Kai-Zen never does what a standard forbids: it looks for a way that keeps the standard and still does the job; if there is none, it stops that part and says which standard and what is left.

What may an agent do in my vaults without asking me? In GilbApp's chat it works as you, with your access: it lists vaults, finds and reads records, creates records and links, and can delete records you may write to. It cannot delete a vault or give or take away anyone's access; Jackfruit ends a record only when you ask for that record.

Why did the agent stop and ask me something? Its standard keeps that choice for you: a fact only you know, or an act it never does without you, such as putting work live or giving access. It stops only that part, asks one question, and goes on with the rest.

The agent says it is not allowed to do something. Why? A standard forbids it or keeps it for a person's yes. Kai-Zen then looks for a way that keeps the standard; if there is none, it stops that part and says which standard. Agent.Coder, Agent.Tester and Agent.Concept set a standard aside only when a person allows it.

A standard is a written procedure, rule set, form or other guide that people and agents follow as they work. An agent is your AI following one written procedure, its standing instructions, for one kind of work. Kai-Zen holds all the work to the standards of its group, the work it hands to the other agents too. When the standards disagree or fall short, it follows its rules for stopping, below.

Kai-Zen asks all its questions in one message, at the start of the work, and only about what only you know or may decide: your purpose, facts about you, money you will spend, and a change of direction. Anything else it would need from you on the way, it chooses itself, writes down as an assumption, and lists for you at the end. What it can decide itself, such as the method, the tools, the estimates, a Value's Status (where it stands now), Tolerable (the survival limit) and Goal (the number you plan to reach), it decides and tells you in one line; you may change it later. A Value is a perceived benefit, measured as a number.

After your reply it does not stop to ask again, except before acts it never does without you: putting work live, a production cutover (a change to the live system run in stages), changing a live concept in GilbVeda, GilbPlatform's shared list of concepts, ending a record or deleting a vault, giving access to a vault, spending more than the budget, changing a Value you set, or changing a standard. Then it stops only that part, asks one question in the same form, and goes on with the rest. These acts stop it whatever you said before.

Most of these acts have a rule of their own that names whose yes it needs. Jackfruit, the vault agent, ends a record only when the person asks for that record, and names it first; it never deletes a vault. It gives or takes away someone's access to a vault only when the vault's owner says so. An agent changes a Value you set, or a level you set on it such as its Tolerable or Goal, only with a yes from you or from the person who asked for the work, and changes a standard only with the go of a person who may write in the vault the standard is kept in. A production cutover starts only on the owner's own instruction. Spending over the budget stops it until you say whether to go on. A live concept in GilbVeda is changed only by Agent.Concept, the agent that finds and makes GilbVeda's terms; it first reads where the concept is used. The answer on how Kai-Zen puts a change live tells when it asks before a release.

Kai-Zen never does what a standard forbids. It looks for a way that keeps the standard and still gets the job done; only if there is none, it stops that part alone, and says which standard and what is left.

When two standards disagree, or one is missing, Kai-Zen does not ask you: it chooses the reading that best serves the Values and goes on. It writes that down as a finding: a note kept with the project, in its folder or its vault, titled FINDING- with the date, what it is about and the project, marked as an open finding, holding three lines: where, what was chosen, and why. The finding names Agent.Standard, the agent that writes and changes standards, as its owner. Kai-Zen tells you where the note is and does not wait for an answer.

When something it needs is missing, Kai-Zen finds it or works it out itself. A fact or a preference that only you have is asked in the one message at the start, or else chosen and written down as an assumption. A gap that a builder or a tester finds in a spec, a requirement written in your plan, is handled as the answer on what happens when a spec has a gap shows.

When Kai-Zen reports, it says what is done, what is not, and why. When Agent.Coder, which builds apps, Agent.Tester, which tests them, or Agent.Concept gives finished work back, it names the standards it followed and any it set aside, with the person who allowed that; an agent cannot allow it. The answer on reading what an agent hands back tells more. Kai-Zen also asks you to check a change live, and at the end of the work it asks for one approval of the whole result; the answer on answering Kai-Zen's questions lists what that approval holds.

GilbApp does not check these rules: they are the Kai-Zen method's, and Kai-Zen follows them. In GilbApp's chat, if a line above the box says The agent is answering WITHOUT its standing instructions, or with only part of its standing instructions, the agent is answering without all of its written procedure, and the line says why, such as that the standards vault, the vault that keeps the agents' procedures, could not be read. Its answer may then not follow that agent's way of working.

This answer is written for a computer screen.

Source: Standards read 2026-11-10, all 200 (StopRules once exit 2 on a timeout, re-run 200): Kai-Zen (K kai-zen-06gd2d286dz8s9b6ey63f9e49r) steps Standards ("Hold all work to the standards in this group. When they conflict or fall short, follow Kai-Zen.StopRules"), Ask; Kai-Zen.StopRules (K 06ge6b3yenrp31y91eqw01bkwm) Refuse ("Never do what a standard forbids. Find a way that keeps the standard and still gets the job done. Only if there is none, stop that part alone, and say which standard and what is left"), Conflict ("If two standards disagree, or one is missing, choose the reading that best serves the Values and go on. Do not ask"), Finding ("FINDING-<date>-<what>-<project>, marked: finding, owner Agent.Standard, status open ... three lines: where, what you chose, and why. Tell the requester where it is; do not wait for an answer"), Missing, Owed; Kai-Zen.AskRules (K 06gdm7dyd5syda52jap5tm8qmm) Decide, MustAsk, One, Assume, Stop (These always stop the part they touch, whatever the requester said), EndApproval; Jackfruit.End ("End a record only when the person asks for that record. Name it before you end it. Never delete a vault"); Jackfruit.Access (only on the vault owner's go); Kai-Zen.ValueRules.HumanSet (changed by an AI agent only with a yes from that person or the requester); GilbPlatform.StandardRules.Owner ("Whoever holds write access to the vault a standard lives in may change it. An agent changes a standard only with that person's go"); Agent.Architect.Cutover (only on the owner's own instruction); Kai-Zen.Return (K 06gj2sxn41x8v45wk68s4v7t2c) Report, Standards ("Name any standard you set aside and the person who allowed it. An agent cannot allow it"); Kai-Zen.HumanCheck.Ask. GilbApp af0f04ee (version.json read 2026-11-10), read in place: lib/base/agentChat.ts:128, :132, :138, :142 (the standing-instructions lines); Kai-Zen.Cycle.Next ("If the spend so far is over Budget ... stop and ask the requester whether to go on"); Rule_Code_gilbveda-ontology-master (J 06gf1st31sy6zcfapj73r9ckdm) RuleBvmasterSoleMinter ("Only Agent.Concept writes ontology ... the mint route, the change route and the signed ontology inbox"), RuleBvmasterUsageFirst (Before you change a live term, read its usage record); Kai-Zen.ValueRules.HumanSet ("A Value or level a human set ... is changed by an AI agent only with a yes ... A human's words fix the wording and the numbers, not the level": the level is a number on the Value, not its level of the plan); Kai-Zen.Return (Standards) and the RulesExecuted steps of Agent.Coder, Agent.Tester and Agent.Concept (When you hand back, run Kai-Zen.Return; Kai-Zen and Jackfruit have no such step); Agent.Standard.Role (You write and change standards) Also: Kai-Zen.AskRules.Stop. Live answer What can my AI see and do in my vault, and does it remember? (what the chat does in your vaults).

Checked against GilbApp d529620.