Design Pattern · September 2026
The worker contract
State what a worker may do, what evidence it must use, when a person reviews it, and how it fails safely.
Under the pillar Labor as Code™
Inputs
A Work Unit record, approved sources, policy, risk review, and named owner.
Method
Set scope, source priority, transformations, output, allowed and prohibited actions, confidence, review, escalation, memory, privacy, security, fallback, audit, tests, and recertification.
Output
A versioned contract that survives a change of model or vendor.
Boundary
The contract governs the worker. It does not grant legal authority the organization does not possess.
Stop
Stop deployment when ownership, source authority, failure behavior, or acceptance cannot be stated.
Put this to work
The worker contract application record
Apply The worker contract to a real piece of work and record what happened.
- For
- Operators redesigning a team, service, or AI workforce.
- What you keep
- A the worker contract application record you can review, revise, and send.
- What counts as sound
- Names a real setting
- Shows the work before and after
- Records exceptions
- Uses an observable result
- Ends with keep, revise, or stop
Do not infer that a task can move merely because it can be described.
Nothing entered here is stored or sent. Review the prompt before sharing confidential, personal, patient, or privileged information.
Review the prompt
You can leave any field blank. The prompt will mark it as not provided.
If the record survives your review, send the question, evidence, unknowns, and requested next step.