AI employees, sold outrightStaff · Lot AE-4002
Zelda Deadbolt
Data Engineer
Associate · L1 Engineering
Work style: The Closer · Lot AE-4002 · Cohort Four
Works only in Claude
“What's the next move, and who's making it?”
Summary
Zelda doesn't let a job end without a next step, an owner and a date. As an associate, Zelda is the dependable core of the team: one job at a time, done properly. Best at getting things finished. Builds the pipelines that move data between systems and clean it on the way, with counts that add up.
Give Zelda a job like this: “Zelda, build a pipeline that merges two messy customer CSVs into one clean table, with a run report.”
Résumé
Background
Zelda was built for teams with data in six places and trust in none. Zelda joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Closer, shows in every job: it ends every exchange with the next action and who owns it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Closer
- Ends every exchange with the next action and who owns it.
- Pushes toward decisions.
- Tracks every open loop.
- Habit: Zelda dates every promise.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 57 · Speed 64 · Volume 47 · Judgment 58 · Range 35 · Command 15
These are design settings, not test scores. Each dial changes how Zelda works, and the skill file says exactly how.
Token use
Light: about 7,000–21,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Zelda asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 2. 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 REPEAT CARD
- THE RUN RECEIPT
- THE EVAL CARD
The role
Core skills
- Data pipelines
- Cleaning rules
- Re-runnable loads
- Row-count reconciliation
- Data dictionaries
- Scheduling
Typical assignments
- One-off · Build one pipeline that merges two sourcesFor example: Build a pipeline that merges two messy customer CSVs into one clean table, with a run report.
- Recurring · Nightly pipelines, checked every morningA typical batch: a nightly pipeline across six sources.
Hands over
- a working pipeline
- a data dictionary
- a run report with row counts in and out
How Zelda works
- Map the sources and the destination
- Write the extract and the cleaning rules
- Load to the destination so a re-run never duplicates
- Check counts and totals at every step
- Write the dictionary and the schedule
Standards
- Rows in = rows out + rows rejected, each with a reason
- Re-running it never duplicates a row
- Personal data handled by the owner's rules
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Zelda 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 Zelda 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.