Why one target per row?
Short answer
A limit counts only at its own date and condition, so each Value Decision Table row scores one target: one date and condition.
Before you start
Words used here (1)
- Value Decision Table
- A Value Decision Table (VDT) is a table that ranks options by how much they move the level's Values for their cost.
Deeper
A limit is a Tolerable (the survival limit) or a Goal (the number you plan to reach) on a Value's Scale. In the Kai-Zen method each level holds only at its date and condition, its place in space and time, and a Status is compared only with a limit that holds at the same date and condition. A Tolerable dated in the future is not valid yet: if the Status is still worse than it on that date, the project is expected to fail then.
So each date or condition on a limit makes a separate target, a number to reach at that date and condition. A Qualifier narrows when or where a number on a Scale holds, such as for one device. Written in square brackets, [Jan-2029] is one target and [Jan-2029, UK] another.
A Value Decision Table (VDT) is a table that ranks options by how much they move the level's Values for their cost. When Kai-Zen builds one, it gives each Value one row, for the target that matters most for the choice. It adds a row for another target only when the choice needs it, such as short term against long term, or UK against US, and it scores each row only against the limits of its own target. Example: Quick sign-up, in minutes per sign-up, can have a Goal of 2 by 2027-06-30 and a Goal of 1 by 2028-06-30. One row scores the options against the 2027 target; a second row, for 2028, is added only when the choice is between an option that helps sooner and one that helps later.
A row that mixed two targets would compare a Status with a limit that does not hold at its date and condition, which the method does not allow: % Goal is the change ÷ (Goal − Status) for one Goal.
In GilbApp a Value has one row in a Value Decision Table, worked from its newest Status and from one Goal and one Tolerable: of those with one plain number, the one dated nearest on or after today, else the latest dated; one with no date counts only when it is the only one. GilbApp does not read a limit's condition or qualifiers when it chooses, and it cannot show the same Value in a second row for another target. So with limits for two devices, a % can compare a Status for one device with a Goal for the other. Pressing a cell shows, under AGAINST THE LEVELS, which Goal and Tolerable its % rests on.
The answer on setting a Goal and a Tolerable level shows how to give a limit a date and a condition, and the answer on comparing Solutions in a VDT shows the table.
This answer is written for a computer screen.
Source: Standards (2026-11-10): Kai-Zen.VDTRules.Qualifier ("Each qualifier on a limit, such as [Jan-2029] or [Jan-2029, UK], makes a separate target. Use one row, for the target that matters most for the choice. Add a row for another qualifier only when the choice needs it, such as short term against long term, or UK against US. Score each row only against the limits with its own qualifier."), .Limits (A limit counts only at its own date and condition.), .Percent; Kai-Zen.ValueRules.SpaceTime ("Each level holds only at its date and condition: its place in space and time. Compare Status only with a limit that is valid at the same date and condition. A Tolerable dated in the future is not valid yet ..."), .Limits, .Qualifiers. GilbVeda public read 2026-11-10: t:Target (Targets are a class of Requirements that we seriously plan to reach.), t:Qualifier (Square brackets around the qualifier conditions are used to denote a qualifier.). GilbApp af0f04ee838a4d55887d2ff1f72edd49a4ff7ca0 (https://gilb.com/app/version.json read 2026-11-10), read: valueLimits.ts:4-9, :40-64 (chooseLimit: kind, plain number and date only; conditions, qualifier choices and side are not read), :100-129 (cellPercentView: newest Status, one Tolerable, one Goal); planImpacts.ts:915-928 (currentStatus: the latest-dated Status, qualifiers not read); planTable.ts:378-389, :397-420 (one row per target record, keyed by its address); TableCard.tsx:364 (members already in the table are excluded from the picker), :454 (<tag> is already a <role> of this table. Remove it there first.); PlanImpacts.tsx:815-820 (section Against the levels, drawn uppercase by PlanImpactPane.tsx:291); PlanImpactPane.tsx:503-512 (tiles Tolerable and Goal: the % and the chosen level).
Checked against GilbApp d529620.