Case study 14 of 15
A Portfolio That Can Be Inspected
This site is a product experiment: a RAG-backed career dossier instead of a static resume page.
Business challenge
Traditional portfolios hide context, decisions, and evidence behind static pages. A visitor can see titles and slogans, but cannot ask why a move was made or what a project actually involved.
Architecture approach
Local dossier data — work history, projects, and writing — is retrieved into an ask-the-dossier interface. Answers are meant to be inspectable and source-scoped, not a black-box biography.
How the work moved from request to production
- Business need
- Intake & risk classification
- Select reusable pattern
- Build / configure
- Review & validate
- Deploy / enable
- Monitor usage, risk, cost, value
Governance considerations
The public site only exposes what is already meant to be public. Retrieval is scoped to local dossier data; company-specific and private details stay off the HTML unless they already belong on the public record.
Results
A working interactive portfolio — this site — where the career can be queried instead of only read. No engagement metrics are claimed; the point is the interaction model.
Lesson learned
A portfolio is more useful when it behaves like software: you can ask it something specific and see what it is grounded in.
Discussion questions
- What should a visitor be able to ask that a PDF cannot answer?
- How do you keep retrieval honest when the source set is your own career?
- When does a personal site need the same inspectability bar as a product?