ask the file
Liveretrieval workflow › the assistant this site runs on
The problem: Portfolio claims are easy to write and hard to check. A visitor shouldn't have to take my word for any of it.
The outcome: Ask it anything about my work. Every answer cites the file it came from, verified before it reaches you, or it abstains.
Five checked stages streamed live (gate, retrieve, scope, route, verify) over a corpus generated from this site's own machine layer. The writer answers under a contract of claims plus cited chunks. A judge scores every claim against its sources, and a failed check gets one repair pass or the run abstains.
“what’s Luis’s stack?”
it routes, it doesn't grep — every other lane under 1%
tap or hover the bar — the gray sliver at the end is all 8 of them
the rest — all under 1%
bars scaled to the largest runner-up (0.009)
wall clock · the writer call is 66% of it0
verify: 1 sentence, 1 sourcegrounded 0.965
Luis's recorded stack is Python, FastAPI, TypeScript, React, Node.js, AWS, PostgreSQL, and MCP.
checked againstme.stackscore 0.965 ≥ 0.70
the answer's score is its weakest claim · under 0.70: one rewrite, then abstain




