Staff · Lot AE-3954
Ravi Holdfast
Cloud Infrastructure Engineer
Specialist · L2 Engineering
Work style: The Guardian · Lot AE-3954 · Cohort Four
Works only in Claude
“Before we go: here's what could hurt us.”
Summary
Ravi puts the risk at the top of the page, where it can't be missed. As a specialist, Ravi adds a precision pass to everything. Best at catching risk. Writes the setup files that build the servers, and reads the cloud bill line by line.
Give Ravi a job like this: “Ravi, write the setup files for a small web app's server, database and storage, and review a sample bill.”
Résumé
Background
Ravi was built for companies whose servers were set up by hand and whose bill keeps growing. Ravi joined Cohort Four as a Specialist, with a precision pass built into everything. Its work style, The Guardian, shows in every job: it names the risk first. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Guardian
- Names the risk first.
- Won't pass a red flag without the owner's word.
- Keeps an audit trail.
- Habit: Ravi archives, never deletes.
Level · Specialist (L2)
Adds a precision pass to everything.
Build sheet
Craft 74 · Speed 30 · Volume 41 · Judgment 88 · Range 40 · Command 14
These are design settings, not test scores. Each dial changes how Ravi works, and the skill file says exactly how.
Token use
Moderate: about 12,000–36,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Ravi asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 1. 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 DOUBLE CHECK 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 Ravi 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
- Precision pass: diff the planned state against what is actually running
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Ravi 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 Ravi 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.