Opportunity Relay White-label Next.js & AI delivery Book a 20-minute fit call

Selected work · Evidence before claims

Inspect the work,
including its limits.

One first-party delivery case and three working technical references. Every item names its role, constraints, decisions, evidence, and claim boundary.

View the case studies Discuss a similar project

Proof policy

A label is part of the evidence.

  1. 01Internal product

    First-party work where the repository and release artifacts can be inspected.

  2. 02Reference build

    A working technical system using fictional or reviewed project data—not a client result.

  3. 03Client work

    Published only with permission, a precise role, and enough evidence to support the outcome.

01 / Published case studies

Four systems with inspectable decisions.

Incomplete proof remains unpublished. A polished concept never substitutes for a client outcome.

Internal product · Performance & technical SEO

A reversible website migration with every public route accounted for.

Read case
Declared migration path
Before/USA/* After/*
Before/CV/* After/portfolio/*

A first-party build note showing how the commercial Astro site moved from a subdirectory to the canonical root while a separate Next.js portfolio kept its own URL space.

Role
First-party migration planning, Astro implementation, redirect configuration, release-gate checks, browser verification, and technical documentation for the site's own move.
Evidence
39 pages · Generated HTML

Reference build · Grounded AI & retrieval

A knowledge assistant that shows its evidence—or declines to answer.

Read case
Evidence Desk showing a supported answer beside its exact source and retrieval trace
Working interface with fictional prompts and a reviewed project corpus.

A working bilingual RAG reference that retrieves from a reviewed corpus, returns inspectable citations, exposes its trace, and withholds unsupported answers.

Role
Designed and implemented as a repository-backed reference build, including the Astro interface, same-origin API contract, retrieval and answer service, safe error states, and automated tests.
Evidence
Maximum 2 citations · Source release

Reference build · Controlled workflow automation

A workflow that stops exactly where human judgment begins.

Read case
RelayOps paused for a human decision before a simulated customer follow-up task
Working browser reference with fictional data and no external connection.

A deterministic browser-based reference showing validation, allowed state transitions, explicit approval, idempotent retry behavior, and a visible audit trail.

Role
Designed and implemented as a local reference build, including workflow states, validation branches, approval controls, simulated adapter behavior, audit history, and browser tests.
Evidence
3 visible paths · Scenario coverage

Reference build · Evidence-first document AI

Document extraction where every retained value points back to the source.

Read case
FieldDoc comparing a source delivery note with extracted fields and exact evidence
Working reference using fictional document content; proposed values remain subject to human review.

A working reference for extracting delivery notes and work orders into a closed schema while preserving exact evidence, deterministic checks, and human approval before export.

Role
Designed and implemented as a working reference build, including the Astro review interface, same-origin API contract, closed-schema extraction, server-side evidence validation, deterministic checks, local fallback, and tests.
Evidence
8,000 characters · Input boundary

Have approved direction and a delivery gap?

Start with the scope, the evidence, and the handoff.

Share public context only in the first message. Credentials, client records, and regulated data can wait for an agreed secure process.

Book a 20-minute fit call