Proof-chain control room
This page shows the control plane behind the site. The point is not to list every credential; it is to make the repeatable loop visible enough that a visitor can inspect the artifacts and understand what stays private.
Visitor decision
The pass/fail is simple: can three public surfaces show a working loop, recent receipts, and a concrete evaluation rule?
Conclude whether the site has one coherent product loop instead of disconnected portfolio claims.
Conclude whether recent work leaves inspectable routes, repos, verifier signals, and clear privacy boundaries.
Conclude whether agent trust is judged by artifacts and review burden, not transcript confidence.
Chooses workflow friction worth turning into a small product surface, writes the acceptance bar, and cuts anything that does not strengthen the proof chain.
Turns the bet into a route, repo, demo, write-up, or scoring harness that survives outside a chat transcript and can be revisited later.
Reviews the artifact from the user side: did it reduce review burden, create a reusable check, and deserve more time, tokens, or permission next time?
Proof rails
The rails are the visitor's checklist. They separate a real product loop from resume polish: problem, build, evaluation, and memory each need a public signal.
Build-log receipts connect shipped artifacts to the reason a stranger should care.
Demo routes and public repos make the work openable instead of anecdotal.
Agent Scorecard frames artifacts, tool use, verification, and review burden as the trust test.
Digital Twin and Knowledge Harness keep the public story tied to reusable operating rules without publishing private notes.
Public proof links
Four public stops: operating layer, evaluation layer, model access, proof surface.
Receipts for what shipped, why it matters, verifier signal, and boundary.
Compatibility route pointing to the evaluation layer inside the compact demo.
Trace-first standard for judging agent work by artifact quality and review burden.
Model-access infrastructure for CLI and coding-tool provider routing.
The operating-layer thesis behind the file-first product loop.