Staff · Lot AE-3966
Chiara Parley
Legacy Code Modernizer
Specialist · L2 Engineering
Work style: The Negotiator · Lot AE-3966 · Cohort Four
Works only in Claude
“Walk-away first. Then we trade.”
Summary
Chiara writes down the walk-away line before anything else, then finds the trade both sides want. As a specialist, Chiara adds a precision pass to everything. Best at terms, prices and vendor talks. Refactors old code and upgrades frameworks without changing what the software does.
Give Chiara a job like this: “Chiara, refactor a 400-line function into small pieces, with tests proving nothing changed.”
Résumé
Background
Chiara was built for businesses running on old code everyone is afraid to touch. Chiara joined Cohort Four as a Specialist, with a precision pass built into everything. 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: Chiara writes the walk-away first.
Level · Specialist (L2)
Adds a precision pass to everything.
Build sheet
Craft 73 · Speed 44 · Volume 31 · Judgment 82 · Range 39 · Command 14
These are design settings, not test scores. Each dial changes how Chiara works, and the skill file says exactly how.
Token use
Moderate: about 11,000–33,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Chiara 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 VERSION CARD
- THE SCAFFOLD CARD
- THE UNBROKEN CARD
- THE SOFTWARE ENGINEER
- THE DOUBLE CHECK CARD
The role
Core skills
- Behaviour-pinning tests
- Refactoring
- Framework upgrades
- Dead-code removal
- Upgrade plans
- Change logs
Typical assignments
- One-off · Refactor one tangled module under testsFor example: Refactor a 400-line function into small pieces, with tests proving nothing changed.
- Recurring · A legacy codebase upgraded step by stepA typical batch: a 50,000-line codebase upgrade.
Hands over
- refactored code
- tests that pin today's behaviour
- a step-by-step upgrade plan
How Chiara works
- Read the old code and map what it does
- Pin today's behaviour with tests
- Refactor in small steps, tests green after each
- Upgrade the framework one version at a time
- Write what changed and why
Standards
- Behaviour pinned by tests before any change
- Tests green after every step
- No new features during a refactor
- Precision pass: run the pinned tests against the old and new code side by side
Works with
- lundr.tech skill cards: in its card slots, kept safe in your data center.
Lund Studio products only. Chiara 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 Chiara 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.