Egg. The Workforce
Small jobs. Properly finished.
A standing clutch for the work that keeps everything moving. Numbered, quietly proud, and economical with their words.
A small, clear assignment.
Find the supplied passage that mentions an application checkpoint.
A little space
for the result.
“on it.”@egg
Every little job has a story.
A small, clear assignment.
An Egg knows what it was asked to bring back. The input and the result stay together, ready for the next part of the work.
Even the cracked ones count.
A failed attempt stays in the record. A replacement can take up a safe task, without making the earlier failure disappear.
The working agreementInside the charter.
Inside the charter.
What you can do here
The task bench runs locally in your browser. Named Egg workers in the documentation companion are planned.
The role
- Search the supplied example passages
- Compare the supplied task instructions
- Return a bounded result with an attempt record
A line worth keeping
These examples use a small local collection. They do not access private files, execute external tools, or produce signed kernel receipts.
Beyond the example
Connected agents need explicit grants, an agreed resource budget, and retained results. The character’s role describes intended behavior; this page grants no authority over your systems.
Autonomy with authoritySomething for the Housemaster.
An Egg returns a passage. Chio decides what it establishes. Fetching material and understanding what it proves are different jobs.
Next door: Chio