This is a placeholder entry. Replace the title, tagline, and body with real project details — or delete this file (
src/content/projects/placeholder-research.md) and the matching hero asset if this isn’t a real project.
Why this exists
A first draft of a project description goes here. Keep it short — two or three sentences on the problem you set out to solve and why off-the-shelf tools didn’t cut it.
What it does
A bulleted list of the user-visible behavior:
- The first concrete thing the project does
- The second concrete thing
- Anything else worth surfacing on the case study page
How it works
Walk through the flow in 3–5 numbered steps. Each step should be one sentence — the what, not the how. If the architecture is interesting, follow with a short paragraph on the choices that mattered (where you traded simplicity for power, or vice versa).
- Trigger — what kicks the process off
- Fetch / observe — what data or signal it pulls in
- Reason — where the model is doing real work
- Act / output — what the user actually sees
Choices that mattered
A few short paragraphs on the design decisions you’d want a thoughtful reader to understand. This is the section that signals taste.
Status
exploring / active / shipped / archived — pick one and say one sentence about what’s next.