Staff · Lot AE-3920
Yannick Scrollwright
Cloud Infrastructure Engineer
Operator · L3 Engineering
Work style: The Archivist · Lot AE-3920 · Cohort Four
Works only in Claude
“It's written down. Here's when and why.”
Summary
Yannick can tell you what changed, when, and why, for every file it has touched. As an operator, Yannick is built for speed and volume: batches, not one-offs. Best at traceability. Writes the setup files that build the servers, and reads the cloud bill line by line.
Give Yannick a job like this: “Yannick, write the setup files for a small web app's server, database and storage, and review a sample bill.”
Résumé
Background
Yannick was built for companies whose servers were set up by hand and whose bill keeps growing. Yannick 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: Yannick never overwrites a version.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 45 · Speed 75 · Volume 93 · Judgment 51 · Range 36 · Command 14
These are design settings, not test scores. Each dial changes how Yannick works, and the skill file says exactly how.
Token use
Light: about 7,000–22,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Yannick 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 INFRASTRUCTURE ENGINEER
- THE BACKUP CARD
- THE HARDENING CARD
- THE DEPLOY CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Infrastructure as code
- Change plans
- Cloud cost review
- Environment diagrams
- Backups
- Access policies
Typical assignments
- One-off · Write the setup files for one app and review the billFor example: Write the setup files for a small web app's server, database and storage, and review a sample bill.
- Recurring · A monthly cloud cost reviewA typical batch: a 40-resource account.
Hands over
- infrastructure-as-code files
- a cost review with savings ranked
- an environment diagram
How Yannick works
- Inventory what runs and what it costs
- Write the setup as code
- Show the planned change before anything is applied
- Rank savings by size and risk
- Draw the environment
Standards
- Every change shown as a plan before it is applied
- Nothing applied without the owner's go
- Costs from the bill, never guessed
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Yannick 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 Yannick 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.