What Vraelis has shipped.

Six arrival surfaces painted the retired cream palette on a graphite ground. Sign in measured 1.0:1. The team invite page, both error screens, the console bar's pre-measurement fallback and the product's mobile drawer were the others, the last of which opened as a cream sheet over the graphite console with its active-page marker in green, which in this product means a verification held.

Every in-page anchor landed 97px past the section it named, because the scrollport's reserved space and the target's own offset add rather than replace. There is one offset now, measured from the real bar. And a window shorter than 768px cut the third layer off a pinned scene instead of compressing it, so pinning stops below that height.

Vraelis declines to charge when it cannot build a check that would prove the claim. That refusal ran on the public API and on guarantee preparation, and nowhere else, so the two paths a person actually takes, a launch from the console and a targeted rerun, never reached it. It now runs above every credit hold and above the free pass, so nothing is spent before the decision to refuse is made.

A contract that never stated an outcome cannot be gated, because there is nothing to gate it against. Those launches are recorded as ungated rather than counted as having passed, so the size of what is left is measurable instead of arguable.

Repairs read from a table that nothing inserts into, so the tab and its page rendered an empty state on every account that has ever existed. Both are hidden until something writes it, which is one flag the day something does. Nothing was deleted.

The ledger has held two units since passes were priced, and the lifecycle mailer summed both into one number. An account holding nothing but dead rows was told its balance was waiting for it.

The low-balance email also fired at a threshold from a retired pricing model, which was three per cent of a single launch. It now fires at the moment the balance can no longer buy one pass, which is the same moment the product itself refuses.

An adversarial sweep of the live guarantee found that eight of eleven approved plans could not tell a working application from a broken one. A rejected sign-in was recorded as a successful one, because the check looked for a session-shaped cookie and an anonymous visitor already carries several. An unsaved form satisfied the assertion that it had saved. A flow that never ran was dropped from the verdict instead of failing it, and an empty one passed.

Every one of those is now closed, and the last surface that translated a partial-coverage rerun into a green Verified was corrected to say Blocked, which is what the API, the CI gate and the webhooks had been saying about the same run all along.

A verification pointed at a mistyped hostname used to queue, drive a real browser at nothing, return Blocked, and keep the charge. The product took payment to report that a URL was wrong. The hostname is now resolved before a run is admitted, above the hold and above the free pass, so a typo costs nothing rather than costing the one free run an account is given.

It asks only whether the name resolves. A real deployment is allowed to answer 404 or 401, and everything ambiguous is let through, including a timeout, because refusing a real customer over a slow second is worse than the charge it would have prevented.

Pay as you go no longer needs a subscription behind it. The price and the balance had been held in different units, so a customer could top up, watch the balance rise, relaunch, and be refused again forever by a product that could not see the money it had just taken.

The four plans differed only by three numbers, and not one of them mentioned a guarantee. Nobody wants forty verifications; they want checkout to keep granting access and sign-in to keep working. A plan now leads with how many guarantees it keeps proven, and the capacity that pays for that is stated underneath rather than sold as the product.

There is an enterprise tier, and cancelling is a real path with a record rather than a button with nothing behind it.

One line puts a vraelis command on the PATH, on macOS, Linux and Windows. It signs in and stores a key, says which credential is winning when a machine holds more than one, and exits 0, 1 or 2 for Verified, Failed and Blocked, so a deploy can be gated on the exit code alone. The installer is served as plain text so it can be read before it is run.

The public site was replaced and the console was given the same treatment on a graphite ground, so the walk from a marketing page to sign-in to the product no longer crosses three visual identities. Six pages were added, including the limitations and current-capability surfaces this company would rather a reader found on its own site than worked out later.

Authorship and review became separate recorded facts. A requirement the system wrote is marked machine-authored and awaiting review, and there is no state in which it approves itself. Submitting a claim without an approved plan returns the plan for review and runs nothing.

Running discovery again against an approved contract now refuses, rather than quietly rewriting the meaning an earlier verification was measured against.

A verification now has one read-only result page: the claim, the decision, the evidence, and the provenance, in a single canonical route. A decision is translated through one place, so what a person reads and what a machine reads never disagree.

External systems can now receive a verification.completed event when a run finishes, with the canonical decision and a reference to its evidence. The production delivery path was proven end to end against a real run.

A dry run now mints an immutable plan. A person approves that exact plan, and a paid execution consumes exactly what was reviewed, nothing more. The standard a completion is judged by is fixed before the work is judged, and the building agent cannot change it.

The complete loop closed end to end against a live application: a claim failed against its requirement, a repair was submitted, and the repair was independently verified, with the earlier failed record preserved rather than overwritten.

The core surface became a single primitive: submit a claimed outcome and a deployment, receive an evidence-backed decision of Verified, Failed, or Blocked. Everything else in the product is built on that one honest answer.

The verification engine is one capability inside a broader direction: following an agent's activity continuously, ingesting live plans and changes, and making autonomy decisions from an agent's track record.