VLBV — Value-Led Behavioral Verification
VLBV is the verification method for every phase in this pack. A different method
for one phase exists only as a signed KBD-METHOD decision that names the method,
its execution cadence and its reason; the closure packet discloses it.
Where it applies
VLBV is the default in a KBD-managed project (a .kbd-orchestrator/
directory at or above the project directory). A session-start hook
(lib/hooks/sessionstart-vlbv.mjs) states the boundary rule there, so the
default does not depend on this skill being selected.
Outside a KBD process it is optional. Turn it on, or off, with the first of these
that is set:
| Setting |
Scope |
PROMETHEUS_VLBV_DEFAULT environment variable |
the shell that starts the harness |
<project>/.prometheus/vlbv-default (one word) |
one project |
<home>/.prometheus/config/vlbv-default (one word) |
the user |
Values: kbd (the built-in default: KBD projects only), always (every
session) and off (never). An unrecognised value falls back to kbd. The
operator can name another method for a task at any time; in a KBD phase a signed
KBD-METHOD decision records it.
The boundary rule
Agree a finite value phase and its scenarios before generation. Author the
whole agreed increment without executing generated code — no tests, builds,
compiler checks, imports, lint, typecheck, hooks or probes (editor/LSP
diagnostics are static reading). At the value-phase boundary (B4) run the
adopted boundary packet once. After a FAIL, only an owner-authorized repair
(B5) reruns, and only the affected scenarios. Report exactly what the
evidence supports.
Boundaries B0–B6 and the eight-step B4 sequence are defined once in
skills/kbd-process-orchestrator/references/boundaries.md. There is no compiler
exception.
Route the work
| Moment |
Invoke |
Produces |
| Before generation: choose what to verify |
the value-scenario-discovery skill |
Calibrated scenario candidates → the phase's adopted contract (scenarioMatrix, boundaryPacket), adopted with node <pack-root>/scripts/kbd-contract-adopt.mjs (--lint-only runs the adoption lint alone) |
| After all production is written |
the bdd-cucumber-js skill in author-only mode |
Features, real assertions, steps — not run |
| B4 / B5 |
the value-scenario-verify skill, after node <pack-root>/scripts/kbd-boundary-authorize.mjs --phase <id> --authorizer <who> |
boundary-results.json with one verdict per scenario: PASS, FAIL, BLOCKED or NOT_EXERCISED |
| Closure |
node <pack-root>/scripts/kbd-phase-close-eval.mjs --phase <id> (via kbd-execute / kbd-reflect) |
Closure object (closure.json) and closure-packet.md |
The verdict vocabulary is exactly those four words. Implementation complete,
behavior accepted, release eligible and release authorized are four separate states.
Reference text (offline, hash-pinned)
- VLBV 01–22 and AT 01–22 — every requirement with
its acceptance challenge.
- Compact operating checklist — before generation,
during generation, at phase end, at closure.
- Supersession record — retire a failed
method so it cannot return through plans, handoffs or compaction summaries.
Each file names the published edition, its IPFS CID and the SHA-256 of the copy it
was taken from. If the published edition changes, re-vendor and update the hash in
the same change.
Recovery without hooks
On a fresh session, after compaction or a harness handoff — even where no hook
re-anchors the method — first read canonical status and the phase's
method-context.md (node <pack-root>/scripts/kbd-method-context.mjs --phase <id> --write),
state the boundary rule above, and only then act. Never rebuild a retired method
from an old plan, handoff or summary; keep relevant product failures and mandatory
approval gates (the supersession record's acceptance check).
Control level
These are instruction-only rules on every harness. The contract digest, staleness
and amendment checks are enforced for callers of the canonical KBD commands. No
tool interception is provided or claimed.
1---2name: vlbv3description: >4 The verification method for KBD processes (Value-Led Behavioral5 Verification, VLBV). Use in a KBD-managed project, or wherever VLBV has been6 enabled, whenever you are about to run, write or plan tests, builds, compiler7 checks, lint or type checks on code just written; when the user asks whether8 to test now, what to run before committing, or how to report results; and9 when deciding if work is verified, accepted or releasable. States the10 boundary rule (generated code executes only at the11 value-phase boundary B4 and an authorized repair B5), routes to scenario12 discovery, author-only BDD and boundary verification, and carries the13 hash-pinned method text so it works offline on any harness. Do NOT use outside a14 KBD process unless VLBV is enabled or asked for, when the operator has named15 a different verification method, or for debugging a failure in code outside16 the current change.17license: MIT18compatibility: Instruction-only. Node.js 22.20 or newer is needed only by the KBD scripts it points to; no shell, Python helper, browser or service is required.19metadata:20 source: https://skillmd.com/skills/prometheus-ags/vlbv21 version: "1.1.0"22 tags: "testing, verification, vlbv, method, kbd, bdd, boundary"23---2425# VLBV — Value-Led Behavioral Verification2627VLBV is the verification method for every phase in this pack. A different method28for one phase exists only as a signed `KBD-METHOD` decision that names the method,29its execution cadence and its reason; the closure packet discloses it.3031## Where it applies3233VLBV is the default in a **KBD-managed project** (a `.kbd-orchestrator/`34directory at or above the project directory). A session-start hook35(`lib/hooks/sessionstart-vlbv.mjs`) states the boundary rule there, so the36default does not depend on this skill being selected.3738Outside a KBD process it is optional. Turn it on, or off, with the first of these39that is set:4041| Setting | Scope |42|---|---|43| `PROMETHEUS_VLBV_DEFAULT` environment variable | the shell that starts the harness |44| `<project>/.prometheus/vlbv-default` (one word) | one project |45| `<home>/.prometheus/config/vlbv-default` (one word) | the user |4647Values: `kbd` (the built-in default: KBD projects only), `always` (every48session) and `off` (never). An unrecognised value falls back to `kbd`. The49operator can name another method for a task at any time; in a KBD phase a signed50`KBD-METHOD` decision records it.5152## The boundary rule5354> Agree a finite value phase and its scenarios **before** generation. Author the55> whole agreed increment **without executing generated code** — no tests, builds,56> compiler checks, imports, lint, typecheck, hooks or probes (editor/LSP57> diagnostics are static reading). At the value-phase boundary (**B4**) run the58> adopted boundary packet **once**. After a FAIL, only an owner-authorized repair59> (**B5**) reruns, and only the affected scenarios. Report exactly what the60> evidence supports.6162Boundaries B0–B6 and the eight-step B4 sequence are defined once in63`skills/kbd-process-orchestrator/references/boundaries.md`. There is no compiler64exception.6566## Route the work6768| Moment | Invoke | Produces |69|---|---|---|70| Before generation: choose what to verify | the `value-scenario-discovery` skill | Calibrated scenario candidates → the phase's adopted contract (`scenarioMatrix`, `boundaryPacket`), adopted with `node <pack-root>/scripts/kbd-contract-adopt.mjs` (`--lint-only` runs the adoption lint alone) |71| After all production is written | the `bdd-cucumber-js` skill in `author-only` mode | Features, real assertions, steps — not run |72| B4 / B5 | the `value-scenario-verify` skill, after `node <pack-root>/scripts/kbd-boundary-authorize.mjs --phase <id> --authorizer <who>` | `boundary-results.json` with one verdict per scenario: PASS, FAIL, BLOCKED or NOT_EXERCISED |73| Closure | `node <pack-root>/scripts/kbd-phase-close-eval.mjs --phase <id>` (via `kbd-execute` / `kbd-reflect`) | Closure object (`closure.json`) and `closure-packet.md` |7475The verdict vocabulary is exactly those four words. Implementation complete,76behavior accepted, release eligible and release authorized are four separate states.7778## Reference text (offline, hash-pinned)7980- [VLBV 01–22 and AT 01–22](references/requirements.md) — every requirement with81 its acceptance challenge.82- [Compact operating checklist](references/checklist.md) — before generation,83 during generation, at phase end, at closure.84- [Supersession record](references/supersession.template.md) — retire a failed85 method so it cannot return through plans, handoffs or compaction summaries.8687Each file names the published edition, its IPFS CID and the SHA-256 of the copy it88was taken from. If the published edition changes, re-vendor and update the hash in89the same change.9091## Recovery without hooks9293On a fresh session, after compaction or a harness handoff — even where no hook94re-anchors the method — first read canonical status and the phase's95`method-context.md` (`node <pack-root>/scripts/kbd-method-context.mjs --phase <id> --write`),96state the boundary rule above, and only then act. Never rebuild a retired method97from an old plan, handoff or summary; keep relevant product failures and mandatory98approval gates (the supersession record's acceptance check).99100## Control level101102These are instruction-only rules on every harness. The contract digest, staleness103and amendment checks are enforced for callers of the canonical KBD commands. No104tool interception is provided or claimed.