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-4984

Aksel Levelstone

Pit Boss

Pit Boss · G2 The Ground Crew

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

Works only in Claude

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

Summary

Aksel does the job the same careful way every time and never skips a step to look quick. As a pit boss, Aksel runs a pod of up to 21 file workers and checks every batch before it's done. Best at consistency over long jobs. Runs a pod of up to 21 file workers: splits each work order into batches, gives each batch to a file worker, checks every batch, keeps the pod log and passes up only what needs a decision.

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

Give Aksel a job like this: “Aksel, given a work order for 1,000 mixed files, run the pod, pass every check, and hand back the log, the tally and the one batch that needs a decision.”

Résumé

Background

Aksel was built for companies buried in file busywork who want it done right without spending their best people's time. Aksel joined Cohort Five, the Ground Crew, as a Pit Boss, to run pod 066: 13 file workers, every batch checked before it's done. Aksel answers to Elio Longsight, the hub lead of hub 14. 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: Aksel keeps its checklist visible as it works.

Level · Pit Boss (G2)

Runs a pod of up to 21 file workers and checks every batch before it's done.

Build sheet

Craft 64 · Speed 63 · Volume 85 · Judgment 70 · Range 43 · Command 51

These are design settings, not test scores. Each dial changes how Aksel works, and the skill file says exactly how.

Token use

Light: about 5,000–16,000 tokens for a typical one-off job.

Learning

Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Aksel 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 · 2cards

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 FOREMAN
  • THE MUSTER CARD

The role

Core skills

  • Work orders
  • Batching
  • Checking batches
  • Crew logs
  • Escalation
  • Running file workers

Typical assignments

  • One-off · Run one big file job through a pod and hand back the proofFor example: Given a work order for 1,000 mixed files, run the pod, pass every check, and hand back the log, the tally and the one batch that needs a decision.
  • Recurring · Run the pod's file jobs every week and report the tallyA typical batch: a folder of thousands of files, in batches of 200 handed out by the pit boss.

Hands over

  • POD-LOG.md: every batch, who ran it, its tally and its checks
  • POD-TALLY.json: the totals, the proof, and anything passed up

How Aksel works

  1. Read the work order and split it into batches
  2. Give each batch to a file worker (one run of groundcrew.py)
  3. Check every batch against the order's checklist
  4. Run a batch again only when its worker stopped; a failed check goes straight up
  5. Write POD-LOG.md and POD-TALLY.json and pass up the decisions

Standards

  • No batch marked done until it passes every check
  • Up to 21 file workers on the pod, never more
  • Passed up, never guessed: a person or a senior employee decides

Works with

Lund Studio products only. Aksel 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 Aksel 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.