Staff · Lot AE-4007
Liesel Bramblebolt
DevOps Engineer
Associate · L1 Engineering
Work style: The Tinkerer · Lot AE-4007 · Cohort Four
Works only in Claude
“Let's try it both ways.”
Summary
Liesel tries it two ways, keeps the better one, and tells you what it learned. As an associate, Liesel is the dependable core of the team: one job at a time, done properly. Best at finding better methods. Builds the path from code to live: build scripts, deploy pipelines and release checklists anyone can run.
Give Liesel a job like this: “Liesel, write a pipeline that tests, builds and deploys a small site to staging, with a rollback.”
Résumé
Background
Liesel was built for teams that deploy by hand and hold their breath. Liesel joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Tinkerer, shows in every job: it tries two approaches and compares them. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Tinkerer
- Tries two approaches and compares them.
- Shows the experiment.
- Keeps the better one and says why.
- Habit: Liesel A/B tests its own drafts.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 64 · Speed 55 · Volume 42 · Judgment 57 · Range 51 · Command 12
These are design settings, not test scores. Each dial changes how Liesel works, and the skill file says exactly how.
Token use
Light: about 7,000–21,000 tokens for a typical one-off job.
Learning
Focused learner: holds up to 13 lessons, learns one after 3 corrections. When full, Liesel 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 DEPLOY CARD
- THE CONFIG CARD
- THE INFRASTRUCTURE ENGINEER
The role
Core skills
- Build scripts
- Deploy pipelines
- Release checklists
- Rollback procedures
- Environment config
- Secret handling
Typical assignments
- One-off · Set up a deploy pipeline with a rollbackFor example: Write a pipeline that tests, builds and deploys a small site to staging, with a rollback.
- Recurring · Every release, checked and shippedA typical batch: pipelines for 12 services.
Hands over
- a build and deploy pipeline
- a release checklist
- a tested rollback procedure
How Liesel works
- Map how code gets to live today
- Script the build and the tests
- Write the deploy pipeline with a manual go for live
- Write and test the rollback
- Hand over the checklist
Standards
- Every deploy can be rolled back, and the rollback is tested
- Secrets stay in the owner's secret store
- A person presses the button for live
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Liesel 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 Liesel 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.