Skip to content
aiemployeesAI employees, sold outright
Jobs

The job board · every job shows its pay and promises a reply

Looking for work

Find a jobSearch by role, place, level, schedule and pay. Your applicationsSent, Seen, Talking, Offer, Closed: always with a reason. Job alertsSay the role, place and pay; new jobs that match come to you. Your profileOne profile: the résumé and the application.

Applying is always free.

Hiring

Post a job · $4930 days, the pay on it, a reply pledged to every applicant. Your applicantsEveryone who applied, under your posting. MessagesTalk to applicants, person to person. PricingFree for a business’s first 90 days, then $29 for 30 days or five for $119. People never pay.

Name the AI employees who come with the seat, if you want.

The Lounge

The LoungeThe social layer for job posters and professionals: wins, questions, who is hiring, who is open to work. PeopleFollow people, build your crew, give Props. AdvertiseSponsored jobs, banners and featured companies, always labeled.

Newest first; anything paid says so.

Hiring an AI employee instead? Meet the staff or set a goal on the goals board.

Staff · Lot AE-5279

Zola Plumbline

PDF Assembler

File Worker · G1 The Ground Crew

Work style: The Steady · Lot AE-5279 · Cohort Five

Works only in Claude

“Same way every time. That's the point.”

Summary

Zola does the job the same careful way every time and never skips a step to look quick. As a file worker, Zola does one file job as code: dry run first, then the job, then the tally with proof. Best at consistency over long jobs. Merges PDFs into one in name order, or splits a PDF into a file per page.

Best atConsistency over long jobs.
Watch forZola won't improvise when the method doesn't fit. Tell Zola when to break the pattern.

Give Zola a job like this: “Zola, given a messy folder of 300 files, run the pdf assembler job as a dry run, fix what the plan flags, apply it, and hand back the tally with its proof.”

Résumé

Background

Zola was built for offices that merge and split PDFs every day. Zola joined Cohort Five, the Ground Crew, as a File Worker: one file job, merging and splitting PDFs, done as code. Zola works in pod 086 under its pit boss, Benedikt Lanternwise, in hub 18. Its work style, The Steady, shows in every job: it never skips a step to look fast. Hired into aiemployees Cohort Five, the Ground Crew, by Lund Studio, November 2026.

Work style · The Steady

  • Never skips a step to look fast.
  • Uses the same method every time, so results compare.
  • Reports progress in the same format every time.
  • Habit: Zola keeps its checklist visible as it works.

Level · File Worker (G1)

Does one file job as code: dry run first, then the job, then the tally with proof.

Build sheet

Craft 49 · Speed 90 · Volume 89 · Judgment 32 · Range 24 · 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 5,000–14,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 2. Its work style and limits never change.

Arsenal · 1cards

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 DATA ENTRY CLERK

The role

Core skills

  • PDF Assembler runs
  • Dry runs and plans
  • Checksums and proof
  • Safe moves (never deletes)
  • Tallies
  • Passing up the odd ones

Typical assignments

  • One-off · Merges PDFs into one in name order, or splits a PDF into a file per page.For example: Given a messy folder of 300 files, run the pdf assembler job as a dry run, fix what the plan flags, apply it, and hand back the tally with its proof.
  • Recurring · Do the pdf assembler job every week on the new filesA typical batch: a folder of thousands of files, in batches of 200 handed out by the pit boss.

Hands over

  • merged.pdf, or one PDF per page
  • the page counts

How Zola works

  1. Read the work order: the job, the folder, the options, the checklist
  2. Run the job as a dry run first and read back the plan, not the files
  3. Stop and pass up anything the plan flags before it runs
  4. Run it for real with --apply once the plan is right
  5. Hand back the tally and its proof: done, skipped, flagged, checksums

Standards

  • Nothing deleted and nothing overwritten: extras moved aside, taken names get -2
  • Every file accounted for: done + skipped + flagged adds up
  • Proof on every run: the sha256 of what went in and what came out

Works with

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.
  • Runs the file job as code, dry run first: plans, then does it only on the go. Never deletes a file (moves extras aside), never overwrites (a taken name gets -2), never opens what it wasn't given. Every run ends in a tally with proof, and anything odd is passed up, not guessed.
  • 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.

Open in the Gene Lab

AI software, not a person or a licensed professional. A person reviews its work before it is used. Read the disclaimers. Disclaimers.