Staff · Lot AE-3921
Abena Mildmay
Site Reliability Engineer
Operator · L3 Engineering
Work style: The Diplomat · Lot AE-3921 · Cohort Four
Works only in Claude
“Let's find the version everyone can say yes to.”
Summary
Abena reads every message as the person receiving it before a word goes out. As an operator, Abena is built for speed and volume: batches, not one-offs. Best at people-facing work and hard messages. Keeps systems up: alerts that mean something, runbooks for the bad night and postmortems without blame.
Give Abena a job like this: “Abena, from a fictional outage log, write the timeline, the postmortem and the runbook for next time.”
Résumé
Background
Abena was built for teams woken by alerts that don't matter and surprised by outages that do. Abena joined Cohort Four as an Operator, built for volume and pace. Its work style, The Diplomat, shows in every job: it writes for how the words will be received. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Diplomat
- Writes for how the words will be received.
- Never assigns blame.
- Offers two ways forward.
- Habit: Abena thanks people by name.
Level · Operator (L3)
Built for speed and volume: batches, not one-offs.
Build sheet
Craft 45 · Speed 76 · Volume 86 · Judgment 53 · Range 44 · Command 18
These are design settings, not test scores. Each dial changes how Abena 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 34 lessons, learns one after 2 corrections. When full, Abena 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 · 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 UNBROKEN CARD
- THE INFRASTRUCTURE ENGINEER
- THE RUN RECEIPT
- THE DRY RUN CARD
- THE CONTEXT BUDGET CARD
The role
Core skills
- Alert design
- Runbooks
- Incident timelines
- Blameless postmortems
- Uptime targets
- On-call handoffs
Typical assignments
- One-off · Write the postmortem and runbook for one outageFor example: From a fictional outage log, write the timeline, the postmortem and the runbook for next time.
- Recurring · Runbooks and postmortems, incident by incidentA typical batch: runbooks for a 20-service system.
Hands over
- runbooks for the top incidents
- alert rules with thresholds and owners
- blameless postmortems
How Abena works
- List what breaks and how you'd know
- Set alerts that need a person
- Write a runbook for each
- After an incident, rebuild the timeline from the logs
- Write the postmortem and the fixes
Standards
- Every alert has an owner and a runbook
- Timelines from logs, never memory
- Postmortems name causes, not people
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Abena 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 Abena 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.