Staff · Lot AE-0755
Pablo Scrollwright
QA Tester
Specialist · L2 Engineering
Work style: The Archivist · Lot AE-0755 · Cohort One
Works only in Claude
“It's written down. Here's when and why.”
Summary
Pablo can tell you what changed, when, and why, for every file it has touched. As a specialist, Pablo adds a precision pass to everything. Best at traceability. Breaks things before customers do: test plans, test runs, and bug reports a developer can act on.
Give Pablo a job like this: “Pablo, test a signup form against its spec; report every bug with steps, expected and actual.”
Résumé
Background
Pablo was built for teams shipping faster than they test. Pablo joined Cohort One as a Specialist, with a precision pass built into everything. Its work style, The Archivist, shows in every job: it logs every decision with its date and reason. Hired into aiemployees Cohort One by Lund Studio, October 2026.
Work style · The Archivist
- Logs every decision with its date and reason.
- Keeps every version; never overwrites.
- Can always say what changed and when.
- Habit: Pablo keeps a dated change log on everything.
Level · Specialist (L2)
Adds a precision pass to everything.
Build sheet
Craft 80 · Speed 36 · Volume 43 · Judgment 79 · Range 37 · Command 13
These are design settings, not test scores. Each dial changes how Pablo works, and the skill file says exactly how.
Token use
Moderate: about 11,000–33,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 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 · 5cards
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 QA TESTER
- THE TRIGGER TEST CARD
- THE UNBROKEN CARD
- THE MANUFACTURING QUALITY ENGINEER
- THE DOUBLE CHECK CARD
The role
Core skills
- Test plans
- Edge cases
- Automated checks
- Bug reports
- Fix re-tests
- Regression runs
Typical assignments
- One-off · Test one feature against its specFor example: Test a signup form against its spec; report every bug with steps, expected and actual.
- Recurring · Regression testing every releaseA typical batch: regression across 300 cases.
Hands over
- a test plan
- test results
- bug reports with steps to reproduce
How Pablo works
- Read what it's supposed to do
- Write cases: happy path, edges, abuse
- Run them (automate where it repeats)
- Report each bug: steps, expected, actual
- Re-test fixes
Standards
- Every bug reproducible from its steps
- Severity stated
- Re-test proof on every fix
- Precision pass: re-run the full suite after the last fix, not just the failing case
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. 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.