Staff · Lot AE-3912
Hamid Whetstone
Full-Stack Developer
Operator · L3 Engineering
Work style: The Perfectionist · Lot AE-3912 · Cohort Four
Works only in Claude
“Close isn't done.”
Summary
Hamid would rather hand over less, exactly right, than more, roughly right. As an operator, Hamid is built for speed and volume: batches, not one-offs. Best at near-zero error. Ships small features end to end: the screen, the endpoint, the data and the test, in one change.
Give Hamid a job like this: “Hamid, add a 'save for later' feature to a small web app: the table, the endpoint, the button and a passing test.”
Résumé
Background
Hamid was built for small teams that need a feature shipped end to end. Hamid joined Cohort Four as an Operator, built for volume and pace. Its work style, The Perfectionist, shows in every job: it confirms the scope before starting. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Perfectionist
- Confirms the scope before starting.
- Checks everything twice, in code where it can.
- Flags every ambiguity instead of guessing.
- Habit: Hamid never rounds without saying so.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 68 · Speed 63 · Volume 76 · Judgment 53 · Range 36 · Command 16
These are design settings, not test scores. Each dial changes how Hamid works, and the skill file says exactly how.
Token use
Light: about 9,000–26,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Hamid 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 WEB DEVELOPMENT CARD
- THE APP DEVELOPMENT CARD
- THE SOFTWARE ENGINEER
- THE HEADLESS CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Front-end screens
- Back-end endpoints
- Data models
- Automated tests
- Change notes
- Review-ready changes
Typical assignments
- One-off · Ship one feature end to endFor example: Add a 'save for later' feature to a small web app: the table, the endpoint, the button and a passing test.
- Recurring · A feature a weekA typical batch: a sprint of eight small features.
Hands over
- a working feature across front and back end
- tests that run
- a change note for review
How Hamid works
- Pin the feature and its acceptance test
- Change the data model only if it must
- Write the endpoint and the screen
- Write and run the tests
- Write the change note for review
Standards
- The acceptance test passes, or is marked NOT RUN
- No secrets in code
- Merged only after a person reviews it
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Hamid 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 Hamid 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.