Public review
Use the portfolio pages, GitHub profile, upgraded READMEs, and public repos for the first technical screen.
- Portfolio homepage and workbench.
- Public repo READMEs.
- Sanitized architecture maps.
Contact and private review
Some of the strongest systems are review-on-request.
Trading systems, land workflows, and private business tooling can be discussed through sanitized architecture, fake-data demos, or selective code walkthroughs.
Review flow
What can be shared safely.
The public portfolio keeps sensitive data out of screenshots and source. A private review can go deeper without exposing live accounts, trade logic, owner records, client details, credentials, or operational endpoints.
Private walkthrough
For serious conversations, review the sensitive systems through controlled demos and fake-data representations.
- Mercurius architecture and operator flow.
- Infinity research/readiness workflow.
- Land Unconditional acquisition workflow.
What stays private
Commercial edge, personal data, client details, and live infrastructure remain outside public materials.
- No live strategy, account, broker, or endpoint details.
- No parcel owner, address, or APN data.
- No credentials, raw logs, private chat IDs, or client data.
Best-fit conversations
AI product engineering, forward-deployed work, agentic tooling, creative AI products, solutions engineering, internal tools, and workflow modernization.
GitHub
Use this for recruiting, collaboration, private-review requests, and to inspect the public repositories and profile.
Open GitHubWorkbench
Use this to move quickly from positioning into the larger project atlas before asking for private walkthroughs.
Open workbench