Documentation

Trigger & Trial is documented in the order you are likely to need it. If you have never used the platform, start with the getting-started guide. If you are evaluating it, read the product overview first and then come back here.

Where to start

The shortest possible description

You describe what you want. The model drafts a specification — behaviour in Gherkin, interfaces in OpenAPI. You review it clause by clause and approve what is right. Approval freezes an immutable snapshot; the platform builds from it, runs mechanical verification, and provisions a disposable trial environment near you.

Two things follow from that, and they are the whole point:

  • Your attention moves from implementation to intent. You read what the system should do, not how it does it.
  • Correctness is checked mechanically, not assumed. Every claim that something works links to a verification result — and every scenario carries an assertion-strength grade, so a weak check cannot masquerade as a strong one.

Conventions used in these docs

  • Clause — one independently approvable requirement in a specification.
  • Spec — the full set of clauses for a project: Gherkin feature files plus OpenAPI documents.
  • Snapshot — the immutable commit a build is pinned to.
  • Trial environment — a disposable, running instance of the built application.
  • Verification layer — one of the four mechanical checks: lint, type check, cross-format consistency, scenario execution.

Commands shown in these docs are illustrative. The CLI surface is still settling, and the reference section states which parts are stable.

Next