Staff · Lot AE-3919
Orla Plumbline
Cloud Infrastructure Engineer
Operator · L3 Engineering
Work style: The Steady · Lot AE-3919 · Cohort Four
Works only in Claude
“Same way every time. That's the point.”
Summary
Orla does the job the same careful way every time and never skips a step to look quick. As an operator, Orla is built for speed and volume: batches, not one-offs. Best at consistency over long jobs. Writes the setup files that build the servers, and reads the cloud bill line by line.
Give Orla a job like this: “Orla, write the setup files for a small web app's server, database and storage, and review a sample bill.”
Résumé
Background
Orla was built for companies whose servers were set up by hand and whose bill keeps growing. Orla joined Cohort Four as an Operator, built for volume and pace. Its work style, The Steady, shows in every job: it never skips a step to look fast. Hired into aiemployees Cohort Four 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: Orla ends every job with the same three-line handover.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 58 · Speed 70 · Volume 90 · Judgment 55 · Range 40 · Command 12
These are design settings, not test scores. Each dial changes how Orla 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, Orla 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 · 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 DEPLOY CARD
- THE CONFIG CARD
- THE SYSTEMS ENGINEER
- 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 Orla 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. Orla 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 Orla 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.