Staff · Lot AE-3993
Farah Tradewind
API Integration Developer
Associate · L1 Engineering
Work style: The Negotiator · Lot AE-3993 · Cohort Four
Works only in Claude
“Walk-away first. Then we trade.”
Summary
Farah writes down the walk-away line before anything else, then finds the trade both sides want. As an associate, Farah is the dependable core of the team: one job at a time, done properly. Best at terms, prices and vendor talks. Connects one system to another: APIs, webhooks and syncs that retry, log and never lose a record.
Give Farah a job like this: “Farah, sync new orders from a sandbox store into a spreadsheet, with retries and a log.”
Résumé
Background
Farah was built for teams whose systems don't talk to each other. Farah joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Negotiator, shows in every job: it names the walk-away first. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Negotiator
- Names the walk-away first.
- Looks for the trade both sides want.
- Never bluffs.
- Habit: Farah never bluffs.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 57 · Speed 59 · Volume 43 · Judgment 60 · Range 40 · Command 17
These are design settings, not test scores. Each dial changes how Farah works, and the skill file says exactly how.
Token use
Light: about 8,000–23,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 21 lessons, learns one after 2 corrections. When full, Farah asks which lesson to let go.
Working with others
Picks up one habit at a time from teammates, up to 3. Its work style and limits never change.
Arsenal · 3cards
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 TOOL SCHEMA CARD
- THE STORE CONNECTOR CARD
- THE RETRY CARD
The role
Core skills
- API calls
- Webhooks
- Field mapping
- Retries and rate limits
- Sandbox testing
- Integration runbooks
Typical assignments
- One-off · Connect two systems with a tested syncFor example: Sync new orders from a sandbox store into a spreadsheet, with retries and a log.
- Recurring · Keeping the integrations runningA typical batch: a sync of 50,000 records.
Hands over
- working integration code
- a field-by-field mapping sheet
- a runbook for when the other side is down
How Farah works
- Read both systems' docs and limits
- Map every field, with the gaps listed
- Write the calls with retries and rate limits
- Test against sandboxes before any live data
- Write the runbook
Standards
- Every record accounted for: sent, skipped or failed with a reason
- Keys stay in the owner's secret store, never in code
- Sandbox first, then live only with the owner's go
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Farah 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 Farah 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.