MyJackfruit

Help
Browse topics · Working with Kai-Zen

Working with Kai-Zen

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

What happens when a spec has a gap?

Short answer

When a builder or tester reports a gap, Kai-Zen finds the answer in the specs or writes the fix, and hands the spec back.

Before you start

Words used here (1)
Kai-Zen
Kai-Zen is the planning agent: it finds out what you want, chooses the way, hands the work to other agents and reports back.
Deeper

Also asked:

What does Kai-Zen do when something in my plan is missing? It checks whether the answer already follows from the specs; if not, it writes the fix itself and notes that. A fact only you have is chosen as an assumption, written on the card, and listed in its report for your approval.

A spec is a requirement written in your plan, such as a Value, a perceived benefit measured as a number, or a Function, what a system does. A spec has a gap when it is missing, unclear, or in conflict with another spec. The builder is the agent that builds a step of the project: Agent.Coder for an app on GilbPlatform, or the place the project names; the tester is the agent that tests it, Agent.Tester for an app on GilbPlatform. An agent is your AI following one written procedure, its standing instructions, for one kind of work. Agent.Coder and Agent.Tester both read Kai-Zen's rules for a spec with a gap, and when the builder reports one during a round of delivery, Kai-Zen takes it up.

First Kai-Zen checks whether the answer already follows from the specs. If it does, it says where, and hands back. Otherwise it writes the fix itself, from the project's Values, its architecture, which is how its parts fit together, and the standards, each a written procedure, rule set, form or other guide that people and agents follow as they work, and it notes that it wrote the fix. Then it hands the fixed spec back; the builder reads it again and goes on.

Kai-Zen does not stop to ask you about the gap, except for the acts below. When the fix needs a fact or a choice that only you have, Kai-Zen chooses it with a Value Kick-out Table (VKT), which picks one of several options, writes it on the card as an assumption, with the AI agent as its source, and lists it in the report of that round of delivery. It lists it again when it asks for your one approval of the whole result at the end; reply there with what you want changed.

Only the acts Kai-Zen always stops and asks you about first stop the fix, such as a change to a Value you set yourself or a change to a standard. Then it stops only that part, asks one question, and goes on with the rest; the answer on answering Kai-Zen's questions lists those acts and shows how to reply.

When Agent.Tester meets a spec that is unclear while it tests, it uses its own judgment, writes what it assumed under Assumptions in its saved test report, and goes on testing.

A gap in a standard, not in a spec, is handled another way: Kai-Zen chooses the reading that best serves the Values, goes on without asking, and writes a finding, a note kept with the project saying where, what it chose and why, for Agent.Standard, the agent that writes and changes standards. The answer on why Kai-Zen stops and asks, or follows a standard, explains it.

GilbApp has no control that reports a gap in a spec. When the project is kept in a vault, the fixed spec is a card you can open in Plan, and an assumption Kai-Zen writes on a card shows on that card under the part called Assumption.

This answer is written for a computer screen.

Source: Standards read 2026-11-10: Kai-Zen.SpecGap (K 06ge5345zht616n3wmpbvnpx18): Entry.Reported ("A builder or tester reports a spec that is missing, unclear, or in conflict with another."), Check (If the answer already follows from the specs, say where, and hand back.), Fix ("write the fix yourself from the Values, the architecture and the standards, and note that you wrote it"), Ask ("assume it per Kai-Zen.AskRules.Assume and list it in the cycle's report. Ask only what Kai-Zen.AskRules.Stop names."), Return (Hand the fixed spec back. The builder reads it again and goes on.); Kai-Zen.AskRules (Assume: "choose it with Kai-Zen.VKT. Write it on the card as an Assumption, with source AiAgent, and list it for the end approval. Go on."; Stop: the list incl. a change to a human-set Value and a change to a standard, Stop only that part and go on with the rest. Ask per Kai-Zen.AskRules.Form.; EndApproval: every assumption ... Change what the requester sends back); Kai-Zen.Cycle.Build (If the builder reports a spec gap, run Kai-Zen.SpecGap.; builder for the kind: a GilbPlatform app to Agent.Coder, anything else to the place the project names), .Check (the builder's tester ... (Agent.Tester for a GilbPlatform app)); Agent.Coder.Tier1 item 3 and Agent.Tester.Standards (Kai-Zen.SpecGap: when the spec is missing, unclear or in conflict); Agent.Tester.Autonomy ("spec ambiguities ... apply your best judgment, state the assumption in the QA report under an Assumptions section, and continue"), .Task (the report is saved); Kai-Zen.StopRules.Conflict ("If two standards disagree, or one is missing, choose the reading that best serves the Values and go on. Do not ask."), .Finding (owner Agent.Standard), .Missing. GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (version.json read 2026-11-10), the code shows only a code comment (lib/base/shareState.ts:32), no control; lib/base/planParts.ts:17-33 and components/records/PlanDescriptionParts.tsx:1860-1866 (the part Assumption, + Assumption), components/help/DescriptionHelp.tsx:194 (sit together under one part called Assumption).

Checked against GilbApp d529620.