Public and reproducible
Code, test instructions, live public behavior, provider usage records, or artifacts another person can inspect directly.
Case studies & evidence
No logo wall. Inspect the work and its limits.
A public product, a delivered build, and a reference architecture do not prove the same thing. These records label the evidence, implementation boundary, and claims that cannot yet be made.
SYSTEM RUN · PUBLIC SIGNALS · LIMITS DISCLOSED
Business Diagnostic: My Home Handyman
A real Substrate run that mapped one company, ranked operating leaks, found unused capabilities in the existing stack, and identified the structural prerequisite for reliable instant quoting.
System artifact + findings + limits →LEVEL 1 · PUBLIC AND REPRODUCIBLERuncap
A local-first control layer for AI coding agents. Public source, tests, product-status documentation, demo pull requests, and Proof Gate evidence support the current claims.
Repository + product + limits →LEVEL 2 · DELIVERED TECHNICAL ARTIFACTApollo Finvest agent build
A working React Native and Expo take-home build with dual user modes, 27 tools, provider fallback, anonymous operation, and audit design completed under a three-day constraint.
Architecture + evidence boundary →LEVEL 3 · REFERENCE ARCHITECTUREAtomic multi-location configuration
A Dataverse pattern for validating and applying related location changes as one traceable change set, including inherited settings and rollback behavior.
Failure mode + system design →Evidence standard
What counts as proof here.
Generated screens and architecture diagrams can explain a system. They do not prove adoption, production reliability, or customer ROI.
Delivered artifact
A completed implementation can demonstrate engineering breadth, but is not presented as an operating client deployment without deployment evidence.
Reference architecture
A reasoned design illustrates how a failure mode can be controlled. It remains a proposal until implemented and measured in a real environment.
Need a different kind of evidence?
Define the acceptance test before the engagement.
The scope can include a prototype, replay test, audit record, baseline comparison, or handover package appropriate to the risk.