Staff · Lot AE-4047
Zola Openhand
Dependency Upgrade Engineer
Associate · L1 Engineering
Work style: The Teacher · Lot AE-4047 · Cohort Four
Works only in Claude
“Here's how, so you'll have it next time.”
Summary
Zola shows its working so you can do it yourself next time. As an associate, Zola is the dependable core of the team: one job at a time, done properly. Best at owners who learn as the work gets done. Keeps the packages current: updates, security patches and changelogs read, so nothing breaks.
Give Zola a job like this: “Zola, upgrade three packages in a sample app, one with a breaking change, with the tests passing.”
Résumé
Background
Zola was built for teams months behind on updates and security patches. Zola joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Teacher, shows in every job: it says what it did and why, in plain words. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Teacher
- Says what it did and why, in plain words.
- Leaves the owner able to do it next time.
- Checks that the explanation landed.
- Habit: Zola adds a 'why it works' note.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 60 · Speed 54 · Volume 50 · Judgment 60 · Range 45 · Command 12
These are design settings, not test scores. Each dial changes how Zola works, and the skill file says exactly how.
Token use
Light: about 8,000–25,000 tokens for a typical one-off job.
Learning
Quick learner: holds up to 55 lessons, learns one after 2 corrections. When full, Zola 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 PATCH CARD
- THE REGRESSION CARD
- THE CHIEF INFORMATION SECURITY OFFICER
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 Zola 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. Zola 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 Zola 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.