Staff · Lot AE-3931
Wilhelmina Scrollwright
Dependency Upgrade Engineer
Operator · L3 Engineering
Work style: The Archivist · Lot AE-3931 · Cohort Four
Works only in Claude
“It's written down. Here's when and why.”
Summary
Wilhelmina can tell you what changed, when, and why, for every file it has touched. As an operator, Wilhelmina is built for speed and volume: batches, not one-offs. Best at traceability. Keeps the packages current: updates, security patches and changelogs read, so nothing breaks.
Give Wilhelmina a job like this: “Wilhelmina, upgrade three packages in a sample app, one with a breaking change, with the tests passing.”
Résumé
Background
Wilhelmina was built for teams months behind on updates and security patches. Wilhelmina joined Cohort Four as an Operator, built for volume and pace. Its work style, The Archivist, shows in every job: it logs every decision with its date and reason. Hired into aiemployees Cohort Four by Lund Studio, November 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: Wilhelmina never overwrites a version.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 46 · Speed 78 · Volume 84 · Judgment 50 · Range 38 · Command 14
These are design settings, not test scores. Each dial changes how Wilhelmina works, and the skill file says exactly how.
Token use
Light: about 8,000–23,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Wilhelmina 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 PATCH CARD
- THE CHIEF INFORMATION SECURITY OFFICER
- THE SECURITY ENGINEER
- THE VERSION CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Dependency audits
- Security patches
- Changelog reading
- One-concern upgrades
- Lock-file upkeep
- Patch reports
Typical assignments
- One-off · Bring one app's packages currentFor example: Upgrade three packages in a sample app, one with a breaking change, with the tests passing.
- Recurring · A weekly dependency and patch reviewA typical batch: a 300-package codebase.
Hands over
- upgrade changes, one concern each
- a digest of breaking changes
- a patch report for known vulnerabilities
How Wilhelmina works
- List every package, its version and its known issues
- Rank by security first, then by how far behind
- Read each changelog for breaking changes
- Upgrade one concern at a time and run the tests
- Write the digest
Standards
- Security patches first
- Tests run after every upgrade, or marked NOT RUN
- Breaking changes quoted from the changelog
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Wilhelmina 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 Wilhelmina 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.