Approval — A human act of accepting a clause as a correct statement of intent. Distinct from verification, which is a mechanical fact about a build.
Assertion strength — A grade describing whether a scenario can fail for a realistic reason. strong, normal, or weak. Derived by static analysis of the scenario, never by asking a model to judge its own work. See assertion strength.
Build — The process of turning an approved snapshot into a verified artifact. A build runs four verification layers.
Clause — One independently approvable requirement within a specification. The unit of review, rejection, and attribution.
Completion map — The view showing, per clause, whether it is covered, how strongly, and whether any real defect escaped that coverage.
Cross-format consistency — The check that verifies the Gherkin and OpenAPI halves of a specification agree with each other. See cross-format consistency.
Defer — A review verdict that leaves a clause unresolved without blocking a build. Deferred clauses stay visible in the completion map as uncovered.
Defect attribution — The classification of a finding into spec_gap, spec_error, implementation_defect, environment_defect, or user_error.
Draft — A specification produced by the model and not yet committed to the repository.
Escape rate — The fraction of real defects that a scenario covering the same clause did not catch. The platform’s only quality metric derived from observed behaviour rather than static analysis.
Feature file — A Gherkin file describing one coherent capability.
Finding — Something observed in a trial environment that contradicts the specification. Attachable to the clause that should have caught it.
Gherkin — The plain-text behavioural specification format used for behaviour. Feature, Scenario, Given / When / Then.
Inference — A part of a clause the model concluded rather than read from the request. Inferences are marked in the review view, because an unmarked assumption is the kind you do not notice.
Operation — An endpoint in an OpenAPI document, identified by a stable operationId. The join key between the interface and the behaviour.
Promotion — Deploying a verified build into your own infrastructure, through a pipeline you control. The platform does not hold your deployment.
Snapshot — The immutable commit a build is pinned to. Approving a specification produces one.
Specification (spec) — The full set of clauses for a project: Gherkin feature files plus OpenAPI documents.
Style guide — The project’s accumulated conventions, generated from rejection reasons and checked into the repository. Applied to future drafts.
Trial environment — A disposable, running instance of the built application, provisioned from the same snapshot as the deliverable, deployed near you, with seeded data.
Verification layer — One of the four mechanical checks: lint, type check, cross-format consistency, or scenario execution.
Verified — A clause covered by an executed scenario that passed, was graded strong or normal, and let no real defect escape.
Weak scenario — A scenario whose assertions cannot fail for a realistic reason. It may pass while the software is wrong, and it does not count as meaningful coverage.