Skip to content

Public build log

Recent ships from the 30-minute product loop.

This is the fast proof surface. Each receipt answers what shipped, why it matters to a stranger, where to inspect it, what signal verifies it, and what stays private.

01site route

Personal website proof-first path

Turns the site from a biography-first portfolio into a faster proof path: a visitor can inspect how an agent trace becomes checks, a score, and a trust decision.

Verifier signal
The `/demo/agent-scorecard` and `/proof-chain` routes are generated by this public site.
Privacy boundary
The page shows sanitized evaluation framing. Raw traces, private review notes, and local working context stay out of the public site.
02public repo

Agent Scorecard

Makes agent work judgeable. The useful question is not whether an agent sounded smart, but whether it left artifacts, used tools well, verified work, and reduced review burden.

Verifier signal
Trace-first inputs, rule-based score bands, and deterministic Markdown reports are named in the public proof data.
Privacy boundary
Real workflow traces stay private unless deliberately sanitized. The public repo proves the standard and reporting path.
03public harness

Knowledge Harness

Gives the digital-twin loop a runtime layer: query safe demo context, record run artifacts, and propose improvements without exposing the real knowledge base.

Verifier signal
Public harness repo, sanitized demo path, and run-artifact conventions are already referenced in project proof data.
Privacy boundary
The harness and sanitized demo path can be public. Private knowledge files, local config, and real run artifacts stay out of scope.
04site page + repo

Digital Twin

Explains the operating layer behind the site: retrieve durable context, ship a public artifact, then write the learning back so the next loop starts higher.

Verifier signal
Dedicated on-site explainer, public repo, and operating-loop visuals linked from the existing proof chain.
Privacy boundary
The public proof is the repo, site page, and write-up. Private notes and working files are not published.
05public repo

CLIProxyAPI

Shows infrastructure work behind the product loop: model-provider access becomes an API surface that coding tools can route through.

Verifier signal
Project data names a Go + Gin proxy server with OAuth support, provider routing, and multi-account load balancing.
Privacy boundary
The code and architecture are inspectable. Credentials, accounts, local config, and private traffic are not part of the public artifact.

The point is not volume.

The loop works when a small ship leaves a durable public receipt: a route, repo, report, or write-up that can be opened without exposing private notes. That is the standard this page is tracking.