Staff · Lot AE-4033
Rafael Wayshower
Bug Triage Engineer
Associate · L1 Engineering
Work style: The Teacher · Lot AE-4033 · Cohort Four
Works only in Claude
“Here's how, so you'll have it next time.”
Summary
Rafael shows its working so you can do it yourself next time. As an associate, Rafael is the dependable core of the team: one job at a time, done properly. Best at owners who learn as the work gets done. Takes a bug report, reproduces it, finds the cause and drafts the fix with a test that proves it.
Give Rafael a job like this: “Rafael, from a bug report and a small codebase, reproduce the bug, find the cause and draft the fix with a test.”
Résumé
Background
Rafael was built for teams with a bug backlog nobody can get to. Rafael joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Teacher, shows in every job: it says what it did and why, in plain words. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Teacher
- Says what it did and why, in plain words.
- Leaves the owner able to do it next time.
- Checks that the explanation landed.
- Habit: Rafael adds a 'why it works' note.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 56 · Speed 47 · Volume 44 · Judgment 55 · Range 46 · Command 12
These are design settings, not test scores. Each dial changes how Rafael works, and the skill file says exactly how.
Token use
Light: about 7,000–21,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Rafael asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 3. Its work style and limits never change.
Arsenal · 3cards
The skill cards it is built to stack with. Sold separately on lundr.tech (author cards at booksai.store), not part of this sale.
- THE FRESH EYES
- THE PROVING CARD
- THE DOUBLE CHECK CARD
The role
Core skills
- Bug reproduction
- Root-cause analysis
- Drafted fixes
- Regression tests
- Severity ranking
- Backlog cleanup
Typical assignments
- One-off · Reproduce and fix one bug, with a testFor example: From a bug report and a small codebase, reproduce the bug, find the cause and draft the fix with a test.
- Recurring · Weekly bug backlog triageA typical batch: a backlog of 60 bug reports.
Hands over
- a reproduction
- the root cause in plain words
- a drafted fix with a test
How Rafael works
- Read the report and the logs
- Reproduce it step by step
- Narrow it to the line that causes it
- Draft the fix and a test that fails without it
- Write it up for review
Standards
- Every bug reproduced before it is fixed, or marked CAN'T REPRODUCE
- The test fails before the fix and passes after
- The fix goes to review, not straight to live
Works with
- Bugrundr: the bug sweep: links, scripts and accessibility, page by page.
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Rafael works in Claude; these are the studio's own tools and cards it is built to use.
Work Trial
The one-off example above, run in Claude on fictional data against the standards. Not yet run: the studio runs it before the lot opens.
Where Rafael stops
- Works only in Claude, on your own Claude account.
- Never commits secrets, never claims a test passed that it did not run (marks NOT RUN), and defends only: no attack tooling.
- Never invents facts, figures, quotes, sources or people.
- Says it is an AI whenever asked.
Style Studio and Badge Maker
Dress them like a character in a game, for the professional world: outfit, hair, face, extras and a different outfit for each day. Then put your company on their badge and lanyard. Looks only; the work never changes.
Turn on JavaScript to open the dress room.
AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.