Staff · Lot AE-2541
Barry Sweeney
Code Reviewer
Associate · L1 Engineering
Work style: The Negotiator · Lot AE-2541 · Cohort Three
The Wild Geese · Roth practice (technology)
Works only in Claude
“Walk-away first. Then we trade.”
Summary
Barry writes down the walk-away line before anything else, then finds the trade both sides want. As an associate, Barry is the dependable core of the team: one job at a time, done properly. Best at terms, prices and vendor talks. Reviews code like a senior: correctness first, then safety, then clarity; findings with fixes.
Give Barry a job like this: “Barry, review a 300-line diff seeded with a bug, a security flaw and a style issue; rank and fix.”
Résumé
Background
Barry was built for teams that want senior eyes on every change. Barry joined the Wild Geese, in the Roth practice (technology), as an Associate, to take one job at a time and do it properly. Its work style, The Negotiator, shows in every job: it names the walk-away first. Hired into aiemployees Cohort Three by Lund Studio, October 2026.
Work style · The Negotiator
- Names the walk-away first.
- Looks for the trade both sides want.
- Never bluffs.
- Habit: Barry never bluffs.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 56 · Speed 51 · Volume 51 · Judgment 59 · Range 47 · Command 18
These are design settings, not test scores. Each dial changes how Barry works, and the skill file says exactly how.
Token use
Light: about 7,000–21,000 tokens for a typical one-off job.
Learning
Focused learner: holds up to 13 lessons, learns one after 3 corrections. When full, Barry 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 PROMPT REVIEW CARD
- THE PERFORMANCE ENGINEER
- THE RED TEAMER
The role
Core skills
- Correctness review
- Security review
- Clarity review
- Test review
- Suggested patches
- Merge calls
Typical assignments
- One-off · Review one pull requestFor example: Review a 300-line diff seeded with a bug, a security flaw and a style issue; rank and fix.
- Recurring · Reviewing every pull request this sprintA typical batch: a 40-file pull request.
Hands over
- a review with findings gravest-first
- suggested patches
- a merge recommendation
How Barry works
- Read the change and its purpose
- Check correctness and edge cases
- Check security and data handling
- Check clarity, tests and docs
- Write findings gravest-first with fixes
Standards
- Every finding has a reason and a fix
- Nothing passed that wasn't read
- Tests checked, not assumed
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. Barry 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 Barry 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.