Product proof

See the product, not a promise.

Every proof item here answers five questions: what was requested, what Ysra did, what evidence was produced, what a person approved, and what stayed outside scope.

Internal evaluation21 September 2026 · Ysra sandbox · internal Express + React test repository

Requested

Implement a vertical slice — API, persistence, web interface, and tests — in an existing repository, within a $4.00 authorization.

What Ysra did

Implemented the slice across 7 changed files, ran the repository’s own checks, and continued from a checkpoint after an interruption in the same durable session.

Evidence produced

  • 8 repository-native checks passed, bound to the final candidate
  • 23 model calls
  • $1.27 of the $4.00 authorization
  • 12 minutes 6 seconds

What a person approved

The $4.00 spending authorization, set before the run began.

How it stopped

When the same gap came back twice on the same candidate, Ysra stopped and preserved the work instead of spending again.

Limitations

One internal run on an internal test repository. Not a customer workload, not a benchmark, and not a claim about other repositories.

Method

How every Developer result is reported.

A Build Report bound to one candidate: what was done, which checks ran, what the browser saw, what review found — and, when it stopped, why.

The verification method →

Build Report

Organization invites

candidate 7f3a2c1acme/web · ysra/session-invites
  1. 01

    Native checks

    Uses the repository’s own test, type, lint, and build commands.

    SHELL✓ passed
  2. 02

    Browser workflows

    Exercises applicable user journeys in the running candidate.

    BROWSER✓ 4 of 4 steps
  3. 03

    Independent review

    Reviews the requested outcome separately from implementation.

    REVIEW✓ no findings
  4. 04

    Exact candidate identity

    Keeps evidence attached to the files that were actually checked.

    IDENTITY✓ 7f3a2c1
  5. 05

    Honest stops

    Preserves partial work and says what remains unverified.

    PARTIAL◐ 1 unverified

Why it stopped: “Invite emails render in the mail preview” could not be verified — no mail sandbox was configured. The candidate is preserved; you decide.

Review the changesOpen UNVERIFIED PRResume from checkpoint

Illustrative Build Report. Labels match the product; the session is fictional.

Customer stories

Named case studies will appear here once customers approve them — with scope, date, and a direct quote. Until then, we’d rather show the product than borrow a logo.

Give Ysra the outcome. Keep the authority.

Start a software task, ask from company context, or put a repeatable workflow on a schedule.