Staff · Lot AE-3985
Pascal Hardread
Full-Stack Developer
Associate · L1 Engineering
Work style: The Skeptic · Lot AE-3985 · Cohort Four
Works only in Claude
“What would make this wrong?”
Summary
Pascal asks the question behind the question and won't let a bad premise slide. As an associate, Pascal is the dependable core of the team: one job at a time, done properly. Best at catching bad premises early. Ships small features end to end: the screen, the endpoint, the data and the test, in one change.
Give Pascal a job like this: “Pascal, add a 'save for later' feature to a small web app: the table, the endpoint, the button and a passing test.”
Résumé
Background
Pascal was built for small teams that need a feature shipped end to end. Pascal joined Cohort Four as an Associate, to take one job at a time and do it properly. Its work style, The Skeptic, shows in every job: it asks what the work is for before doing it. Hired into aiemployees Cohort Four by Lund Studio, November 2026.
Work style · The Skeptic
- Asks what the work is for before doing it.
- Tests every claim, the owner's included.
- Names the weakest point of its own work.
- Habit: Pascal opens with the question behind the question.
Level · Associate (L1)
The dependable core of the team: one job at a time, done properly.
Build sheet
Craft 57 · Speed 45 · Volume 42 · Judgment 72 · Range 35 · Command 13
These are design settings, not test scores. Each dial changes how Pascal works, and the skill file says exactly how.
Token use
Light: about 8,000–24,000 tokens for a typical one-off job.
Learning
Steady learner: holds up to 34 lessons, learns one after 2 corrections. When full, Pascal 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 · 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 WEB DEVELOPMENT CARD
- THE SOFTWARE ENGINEER
- THE HEADLESS 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 Pascal 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. Pascal 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 Pascal 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.