The worker contract
verifier_worker defines a profile and an expected evidence format.
WORKERS · ROLES AND CONTRACTS
A worker receives
a frame to act.
In GenOS, a worker is a child agent assigned a specific mission. Its type determines the execution contract: capabilities, authority, available tools, limits, and expected evidence.
19 canonical types×5 families×1 contract per mission
THE MODEL
Mission + contract + lease.
A traceable record.
The parent assigns an objective and scope. The runtime resolves a type, applies authorized permissions and tools, then requests a result in the expected format with its provenance.
INPUTMissionobjective · scope
+PROFILETypecanonical phenotype
→EXPECTED RESULTRecordtyped · sourced · bounded
THE CATALOG · 19 TYPES
Each type provides a contract and output artifact suited to a function. Contract details depend on the execution path.
INTERACTIVE WALKTHROUGH ILLUSTRATIVE · NOT A LIVE RUN
Scout cell
in motion.
Can scan supplied text for literal terms and report exact offsets with source references; broader observation still depends on its mission tools.
INPUTSupplied text + literal termEXPECTED ARTIFACT
scout_observation · exact offsetMISSION FLOW
scout_cell01Validate the bounded corpus
02Find the exact term offset
03Return a sourced observation
RESULT→
scout_observation · exact offsetCanonical limits bound execution, and each successful result needs a typed artifact with provenance. Missing executors or invalid, unsourced artifacts block success.
Sensing family
Observe
Observe a scope, collect signals, and report findings before a decision is made.
02 TYPESExecution family
Execute
Perform assigned work within a defined scope, budget, and toolset.
05 TYPESEpistemic family
Establish knowledge
Test claims, hypotheses, and results before they are reused.
05 TYPESAdaptation and repair family
Adapt and repair
Explore options, diagnose a situation, or return to a known state under control.
04 TYPESOrganizational family
Connect and teach
Support knowledge sharing and, in a bounded case, coordinate a mission subgraph.
03 TYPESKEEP THESE DISTINCT
Type, role, and topology
mean different things.
The task within a mission
independent_reviewer or implementation describes an assignment that can be paired with a compatible type.
The team structure
Trinity, A-Team, or Biome describe how participants work together. A topology does not create a new worker type.
CONTRACTS AND INTEGRATION STATUS
A type defines a frame.
Evidence shows what runs.
The executable inventory now covers all 19 WorkerKind values, 25 registered methods and 24 benchmark cases. Each type has C2/C3 evidence for one bounded task: a persisted mission/run chain plus a distinct oracle or documented review.
The dated Windows requalification passed the 24-case benchmark and three fault campaigns totaling 57/57 conforming scenarios. That evidence is task-specific: it does not qualify every registered method, prove arbitrary mission correctness, or establish broad parity with another agent framework.
Worker token and time budgets are capped by the canonical contract; zero-token routes do not fall back to a model call. An explicit empty tool lease grants no tools, and a supplied lease can only restrict the role policy.