Staff · Lot AE-4034
Goran Endmark
Bug Triage Engineer
Associate · L1 Engineering
Work style: The Closer · Lot AE-4034 · Cohort Four
Works only in Claude
“What's the next move, and who's making it?”
Summary
Goran doesn't let a job end without a next step, an owner and a date. As an associate, Goran is the dependable core of the team: one job at a time, done properly. Best at getting things finished. Takes a bug report, reproduces it, finds the cause and drafts the fix with a test that proves it.
Give Goran a job like this: “Goran, from a bug report and a small codebase, reproduce the bug, find the cause and draft the fix with a test.”
Résumé
Background
Goran was built for teams with a bug backlog nobody can get to. Goran joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Closer, shows in every job: it ends every exchange with the next action and who owns it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Closer
- Ends every exchange with the next action and who owns it.
- Pushes toward decisions.
- Tracks every open loop.
- Habit: Goran ends with a next-action line.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 61 · Speed 59 · Volume 45 · Judgment 52 · Range 38 · Command 12
These are design settings, not test scores. Each dial changes how Goran 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, Goran asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 2. 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 UNBROKEN CARD
- THE PROVING 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 Goran 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. Goran 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 Goran 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.