RELEASE ENGINEER / EVIDENCE INDEX

The record
behind the beta.

A clear view of what exists, where it can be inspected, and what it establishes. Technical checks, qualitative feedback and usage records answer different questions.

Inspectable sourceDated observationsExplicit boundaries
PUBLIC PRODUCT & SOURCE

Working software, inspectable engineering.

A live public-PR review interface with Claude as the core reasoning engine. Bounded retrieval, prompt-injection defenses, structured output validation and deterministic coverage safeguards are visible in the source.

SYNTHETIC OBSERVATIONS

Evaluation with failures in view.

Two manually dispatched complete 32-case synthetic Claude runs are documented. The October 7, 2026 candidate completed 32/32 cases with 0 infrastructure errors, with 22 PASS / 10 FAIL under the strict evaluator and one critical violation remaining.

These are dated synthetic observations, not real-world accuracy, customer traction, production reliability proof or external validation.

Metrics, failures, source runs & provenance ↗︎
QUALITATIVE FEEDBACK

Approved early developer feedback.

Three exact quotes supplied by the founder, with permission to publish the approved display names and roles. PR links were not approved. This is informal external beta feedback; it does not independently verify a finding or establish a unique developer count.

Read the approved quotes →
PINNED OBSERVATIONS

Public PR case studies.

Published observations identify a reviewed head SHA, participation source, human verification, outcome and limitations. Founder tests are explicitly distinguished from external tester observations.

Read the public observations →
MEASUREMENT METHOD

Live usage, without a vanity counter.

The server emits privacy-safe operational events when an analysis starts, succeeds or fails. A success means the server prepared a schema-valid report. It does not prove correctness, browser delivery, a unique developer or a customer.

No verified production count is published. A future count requires a preserved, complete production log window, deduplication and explicit exclusion or disclosure of operator testing.

Usage evidence methodology ↗︎
IDENTITY & BOUNDARIES

A founder, a public record, a way to contact us.

Founded by Ozan Kenan Güngör in October 2026, in Ankara, Türkiye. Bootstrapped and in early beta, with no external funding raised. These company facts are founder-supplied.