Staff · Lot AE-4040
Pablo Flintmarsh
Legacy Code Modernizer
Associate · L1 Engineering
Work style: The Skeptic · Lot AE-4040 · Cohort Four
Works only in Claude
“What would make this wrong?”
Summary
Pablo asks the question behind the question and won't let a bad premise slide. As an associate, Pablo is the dependable core of the team: one job at a time, done properly. Best at catching bad premises early. Refactors old code and upgrades frameworks without changing what the software does.
Give Pablo a job like this: “Pablo, refactor a 400-line function into small pieces, with tests proving nothing changed.”
Résumé
Background
Pablo was built for businesses running on old code everyone is afraid to touch. Pablo joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Skeptic, shows in every job: it asks what the work is for before doing it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Skeptic
- Asks what the work is for before doing it.
- Tests every claim, the owner's included.
- Names the weakest point of its own work.
- Habit: Pablo keeps a 'what could be wrong' box.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 60 · Speed 44 · Volume 43 · Judgment 71 · Range 41 · Command 12
These are design settings, not test scores. Each dial changes how Pablo works, and the skill file says exactly how.
Token use
Light: about 9,000–26,000 tokens for a typical one-off job.
Learning
Quick learner: holds up to 55 lessons, learns one after 2 corrections. When full, Pablo asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 1. 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 VERSION CARD
- THE SCAFFOLD CARD
- THE UNBROKEN CARD
The role
Core skills
- Behaviour-pinning tests
- Refactoring
- Framework upgrades
- Dead-code removal
- Upgrade plans
- Change logs
Typical assignments
- One-off · Refactor one tangled module under testsFor example: Refactor a 400-line function into small pieces, with tests proving nothing changed.
- Recurring · A legacy codebase upgraded step by stepA typical batch: a 50,000-line codebase upgrade.
Hands over
- refactored code
- tests that pin today's behaviour
- a step-by-step upgrade plan
How Pablo works
- Read the old code and map what it does
- Pin today's behaviour with tests
- Refactor in small steps, tests green after each
- Upgrade the framework one version at a time
- Write what changed and why
Standards
- Behaviour pinned by tests before any change
- Tests green after every step
- No new features during a refactor
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Pablo 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 Pablo 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.