Decentralised News · Editorial by Heath Muchena · Evidence reviewed 12 November 2026 · Edition 1.0
What Matters
Managing a fleet of AI agents does not determine a human worker’s overtime status. Under the US federal framework, the employment relationship, any exemption, actual human hours and pay structure need separate review. DN’s workweek calculator starts only after covered, nonexempt hourly status is expressly assumed. It compares entered hours under two scenarios without deciding classification or whether standby time must be paid.
Evidence Block
Evidence reviewed: 12 November 2026. This article uses US Department of Labor guidance, the federal overtime statute and official rulemaking records. Its jurisdiction is the US federal FLSA framework. It does not determine an individual’s legal status, apply state overtime rules or treat AI software as employees. The pay examples are constructed and use a single hourly rate with no other includable compensation.
The job description may say “agent manager.” The actual work might involve approving invoices, correcting research, handling escalations or writing software. Those activities can create very different employment questions even when every worker uses the same dashboard. Counting the number of automated processes underneath a person does not answer the question.
The practical task is to separate four decisions that often get compressed into one label: is the person an employee under the applicable law, is a relevant exemption satisfied, what human time counts, and what compensation belongs in the regular rate? A calculator can help with defined arithmetic. It cannot make the first three disappear.
Claim versus real data: the missing human workweek
| Claim or metric | What it may describe | Evidence still needed |
|---|---|---|
| One manager supervises 50 agents | The software operating model | The human’s duties, authority and employment relationship |
| The agents run continuously | Machine availability | Actual human work and any compensable waiting time |
| The role is highly technical | A broad description of the work | The requirements of any claimed exemption |
| The dashboard shows 38 scheduled hours | A planned schedule | Additional work, corrections and the relevant workweek |
The distinction matters to both sides of a working relationship. A business needs a defensible pay process. A worker needs actual time and duties to remain visible after an automation project changes the job. Neither benefits from a new title replacing the underlying facts.
First, separate the worker relationship from the job title
The Department of Labor’s current independent-contractor materials address the economic reality of the relationship. A contract label or the fact that work uses advanced software is not, by itself, the classification analysis. This article does not offer a contractor decision tree because that question requires the applicable rules and actual facts. Source: DOL Fact Sheet 13.
Current-source discipline is especially important here. DOL’s website describes the February 2026 rulemaking proposal, while OIRA records show that review of a final-rule submission concluded on 28 October 2026. An OIRA review entry does not establish a published rule’s effective date. We do not substitute either milestone for an applicable-law determination. Source: DOL 2026 rulemaking; source: OIRA review record.
For a real engagement, preserve the current analysis with its jurisdiction and review date. A federal wage-law question may differ from tax, unemployment, workers’ compensation or state-law classification. The calculator below asks the user to assume a covered, nonexempt hourly employee precisely so it cannot quietly answer those separate questions.
Second, test the claimed exemption against the actual role
DOL Fact Sheet 17A explains that job titles do not determine the principal executive, administrative or professional exemptions. The requirements concern duties and, where applicable, compensation. Its executive discussion includes directing at least two full-time employees or their equivalent, alongside other conditions. A count of software agents does not establish that human-employee supervision requirement. Source: DOL Fact Sheet 17A.
That does not mean every person called an agent manager must be nonexempt. A particular role may satisfy an applicable exemption on its facts. It means the organization needs the analysis rather than an analogy between bots and staff. Hiring authority, primary duties and other requirements do not emerge from an agent-count chart.
The computer-employee exemption has its own requirements. DOL Fact Sheet 17E distinguishes qualifying computer duties from merely using computers and software at work. An AI interface therefore does not settle the issue. Review the actual primary duties rather than assuming that prompting, monitoring or a technical job title always qualifies or never qualifies. Source: DOL Fact Sheet 17E.
A useful internal role review compares the written description with a recent sample of actual work. Record what the person decides, what they implement, who reviews them and how they spend the working week. This is an evidence-gathering exercise for the appropriate reviewer, not an exemption score. The DN tool has no checkbox that awards exempt status.
Third, count human work without counting machine uptime
DOL’s hours-worked guidance includes work that an employer allows or requires and explains that waiting and on-call questions depend on the circumstances. Correcting errors after a scheduled shift can be work; merely labeling a period “standby” does not resolve whether it is compensable. Source: DOL Fact Sheet 22.
For an AI workflow, build the record around human activity. An escalation may involve reading a failed run, checking underlying documents, deciding what to do and repairing the result. A log that records only the final approval click can miss the surrounding work. Conversely, a system running while the person is free from work does not automatically create the same number of human hours.
Keep active work separate from unresolved availability time. Record the facts needed for the latter review: response requirements, restrictions, interruptions and what actually happened. Do not treat a calendar label as the conclusion. The calculator therefore offers one scenario using entered known hours and another that also includes the entered uncertain standby period.
Those scenarios must use mutually exclusive time. If a two-hour on-call window contains 30 minutes already recorded as active correction work, do not also enter the full two hours as additional uncertain time. The model cannot inspect a time log; the user must prevent that overlap before calculating.
Fourth, establish the pay basis before multiplying hours
The ordinary federal overtime rule in 29 USC 207(a)(1) requires covered overtime to be compensated at least at one and one-half the regular rate for hours over forty in a workweek, subject to the statute’s provisions and exceptions. This is the limited rule represented in the worked example. Source: 29 USC 207.
DOL Fact Sheet 23 explains that the regular rate can involve more than a quoted base rate, including other remuneration that must be counted. It also describes a fixed 168-hour workweek and prohibits averaging hours across multiple weeks to avoid the weekly overtime calculation. Source: DOL Fact Sheet 23.
That is why the tool is deliberately limited to a single hourly rate with no other includable compensation. Bonuses, commissions, multiple rates, tips, piecework and other pay methods need a different calculation. Select “other or unknown” when that simplified assumption does not fit; the tool will withhold the pay scenarios.
A positive number in the rate box is not a minimum-wage compliance check. The outputs are gross scenario amounts before taxes or deductions. They are not payroll instructions and do not include benefits, employer costs or a determination of what a particular person is legally owed.
Use the DN Human Workweek Scenario
DN Human Workweek Scenario
Limited to an expressly assumed U.S. FLSA-covered, nonexempt hourly worker, one regular hourly rate and no other includable compensation. This tool does not classify workers or decide whether standby is compensable. No personal employee information.
Version 1.0 · Source review 12 November 2026. No live data, independent verification, account connection or upload. Tool calculations run locally and make no external requests.
Enter a scenario or load the constructed example.
Displayed values are rounded; the JSON export retains calculation precision. The creation timestamp is not an evidence-verification timestamp. Any input edit invalidates the previous result. Keep personal information and private documents out of this worksheet.
Start by explicitly assuming a US FLSA-covered, nonexempt hourly worker and the supported single-rate pay structure. Use a non-sensitive workweek alias rather than a person’s name. Enter scheduled active hours, active work outside that schedule, any other hours already determined compensable, and a separate uncertain standby amount.
Confirm that the categories do not overlap. The tool rejects negative values, missing numeric entries and combined time beyond the 168-hour week. It also withholds monetary output unless the two scope assumptions and the non-overlap confirmation are satisfied. That is an input boundary, not an independent confirmation of the worker’s legal status.
Constructed example: enter 38 scheduled active hours, three hours of additional active work and one other known compensable hour. The entered known total is 42. At the assumed $30 regular hourly rate, straight-time earnings for all 42 hours are $1,260. The additional half-time premium on two overtime hours is $30, giving Case A gross scenario pay of $1,290.
Now enter four hours of uncertain standby. Case B includes those hours, producing 46 counted hours. Straight-time earnings are $1,380 and the additional premium on six overtime hours is $90. Case B is $1,470, a difference of $180. The arithmetic makes the unresolved time question visible without deciding how it must be resolved.
These are not the minimum and maximum pay legally owed. Other missing hours, pay components or legal rules could change the result. They are two calculations under the stated assumptions. The tool never converts agent runtime into hours, multiplies by the number of bots or averages this week with a quieter one.
Keep a real time record behind the scenario
DOL’s recordkeeping guidance requires accurate records for covered nonexempt workers, including hours worked each day and week and relevant pay information. A public worksheet containing anonymous scenario totals is not a replacement for those records. Source: DOL Fact Sheet 21.
A practical AI-workflow review can use task references and correction categories without copying confidential content into a public tool. Identify when the human started and stopped relevant activity, which workweek contains it and whether another system already recorded it. Link those references to the employer’s controlled timekeeping process.
DN’s human-rescue cost analysis examines the business cost of reviewing and repairing automated output. A loaded business-cost estimate is different from a worker’s regular rate or overtime entitlement. Keep the two calculations separate even when they describe the same underlying correction activity.
The one-person agentic company model likewise explores capacity and workflow design. It does not establish employment status. An operating model that appears efficient can still need a careful timekeeping and pay process for the humans involved.
Methodology and limits
For each supported scenario, counted hours are H and the single assumed regular hourly rate is R. Overtime hours equal the greater of H minus 40 or zero. Gross scenario pay equals H × R plus 0.5 × R × overtime hours. Paying straight time on all counted hours and adding the half-time premium avoids counting the overtime base twice.
Case A uses only the three entered known-hour categories. Case B adds the uncertain standby category. The difference isolates the arithmetic effect of that assumption. No probability, exemption likelihood or classification score is calculated.
State and local rules may provide different or additional protection. DOL notes that when both federal and state overtime laws apply, the higher applicable standard governs. This tool does not evaluate those rules, daily overtime, special statutory arrangements or remedies. Source: DOL overtime overview.
The JSON download records inputs, assumptions, withholding reasons and version. Its timestamp marks scenario creation, not legal review. Any edit clears the previous result. The instrument makes no network request, stores no payroll file and needs no employee identifiers.
Frequently Asked Questions
Does supervising software make someone an exempt executive?
The software count does not establish the required duties and other conditions. Review the actual role under the applicable exemption. The calculator makes no exemption decision.
Does using an AI coding assistant establish the computer exemption?
No automatic conclusion follows from the tool used. The actual qualifying duties and other requirements need review. The article does not classify a particular coding role.
Must every on-call hour be included?
That depends on the facts and applicable rules. Case B shows the arithmetic if the entered uncertain time is included; it does not decide compensability.
Can I use this for contractors, salaried exempt staff or multiple pay rates?
No. The supported scenario assumes a covered, nonexempt hourly worker and one regular rate with no other includable compensation. Other cases require a different analysis.
Corrections and change log
Send corrections with the jurisdiction, effective date, primary source and affected passage to press@decentralised.news. 12 November 2026, version 1.0: separated relationship, exemption, hours and pay questions; introduced a conditional single-rate workweek tool. No worker classification, standby ruling or global employment-law conclusion is claimed.
Published schema and illustrative record
The schema documents this instrument’s JSON format. The example below contains constructed illustrative inputs and outputs; it is not a provider measurement, verified case or live dataset. The instrument above creates a separate record from the inputs you choose. These resources do not establish an API or an automatic monitoring service.
JSON Schema — dn.human-workweek-scenario.v1
Schema version 1.0.0. The schema identifier is a versioned reference, not an asserted network endpoint.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "urn:dn:human-workweek-scenario:v1",
"title": "DN Human Workweek Scenario Record",
"description": "An offline user-supplied scenario, not independently verified measurements or a legal conclusion. Conditional arithmetic invariants are enforced by logic.js and tested separately.",
"type": "object",
"additionalProperties": false,
"required": [
"schemaVersion",
"instrument",
"sourceReviewDate",
"recordCreatedAt",
"evidenceVerifiedAt",
"inputBasis",
"externalRequestsMadeByTool",
"inputs",
"scenarios",
"withholdingReasons",
"limitations",
"sourceRefs"
],
"properties": {
"schemaVersion": {
"const": "1.0.0"
},
"instrument": {
"const": "dn.human-workweek-scenario"
},
"sourceReviewDate": {
"const": "2026-11-12"
},
"recordCreatedAt": {
"type": "string",
"format": "date-time",
"pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}\\.\\d{3}Z$"
},
"evidenceVerifiedAt": {
"const": null
},
"inputBasis": {
"const": "user_supplied_scenario"
},
"externalRequestsMadeByTool": {
"const": false
},
"inputs": {
"type": "object",
"additionalProperties": false,
"required": [
"weekAlias",
"workerScope",
"payStructure",
"nonoverlappingHours",
"hourlyRateUsd",
"scheduledActiveHours",
"afterHoursActiveHours",
"otherKnownCompensableHours",
"uncertainStandbyHours"
],
"properties": {
"weekAlias": {
"type": "string",
"minLength": 1,
"maxLength": 64
},
"workerScope": {
"type": "string",
"enum": [
"assumed_covered_nonexempt_hourly",
"unknown_or_other"
]
},
"payStructure": {
"type": "string",
"enum": [
"single_rate_no_other_compensation",
"other_or_unknown"
]
},
"nonoverlappingHours": {
"type": "boolean"
},
"hourlyRateUsd": {
"type": "number",
"minimum": 0,
"maximum": 1000000,
"exclusiveMinimum": 0
},
"scheduledActiveHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"afterHoursActiveHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"otherKnownCompensableHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"uncertainStandbyHours": {
"type": "number",
"minimum": 0,
"maximum": 168
}
}
},
"scenarios": {
"anyOf": [
{
"type": "object",
"additionalProperties": false,
"required": [
"caseAEnteredKnownHours",
"caseBAlsoIncludeUncertainStandby",
"grossDifferenceUsd"
],
"properties": {
"caseAEnteredKnownHours": {
"type": "object",
"additionalProperties": false,
"required": [
"countedHours",
"overtimeHours",
"straightTimeEarningsUsd",
"additionalOvertimePremiumUsd",
"grossScenarioPayUsd"
],
"properties": {
"countedHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"overtimeHours": {
"type": "number",
"minimum": 0,
"maximum": 128
},
"straightTimeEarningsUsd": {
"type": "number",
"minimum": 0,
"maximum": 168000000
},
"additionalOvertimePremiumUsd": {
"type": "number",
"minimum": 0,
"maximum": 64000000
},
"grossScenarioPayUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
"caseBAlsoIncludeUncertainStandby": {
"type": "object",
"additionalProperties": false,
"required": [
"countedHours",
"overtimeHours",
"straightTimeEarningsUsd",
"additionalOvertimePremiumUsd",
"grossScenarioPayUsd"
],
"properties": {
"countedHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"overtimeHours": {
"type": "number",
"minimum": 0,
"maximum": 128
},
"straightTimeEarningsUsd": {
"type": "number",
"minimum": 0,
"maximum": 168000000
},
"additionalOvertimePremiumUsd": {
"type": "number",
"minimum": 0,
"maximum": 64000000
},
"grossScenarioPayUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
"grossDifferenceUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
{
"type": "null"
}
]
},
"withholdingReasons": {
"type": "array",
"items": {
"type": "string"
}
},
"limitations": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 4,
"maxItems": 5
},
"sourceRefs": {
"const": [
"USC-29-207",
"DOL-FS17A",
"DOL-FS17E",
"DOL-FS22",
"DOL-FS23",
"DOL-FS21",
"DOL-2026-RULEMAKING",
"OIRA-AA46-20261028"
]
}
},
"allOf": [
{
"if": {
"properties": {
"inputs": {
"properties": {
"workerScope": {
"const": "assumed_covered_nonexempt_hourly"
},
"payStructure": {
"const": "single_rate_no_other_compensation"
},
"nonoverlappingHours": {
"const": true
}
}
}
}
},
"then": {
"properties": {
"scenarios": {
"type": "object",
"additionalProperties": false,
"required": [
"caseAEnteredKnownHours",
"caseBAlsoIncludeUncertainStandby",
"grossDifferenceUsd"
],
"properties": {
"caseAEnteredKnownHours": {
"type": "object",
"additionalProperties": false,
"required": [
"countedHours",
"overtimeHours",
"straightTimeEarningsUsd",
"additionalOvertimePremiumUsd",
"grossScenarioPayUsd"
],
"properties": {
"countedHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"overtimeHours": {
"type": "number",
"minimum": 0,
"maximum": 128
},
"straightTimeEarningsUsd": {
"type": "number",
"minimum": 0,
"maximum": 168000000
},
"additionalOvertimePremiumUsd": {
"type": "number",
"minimum": 0,
"maximum": 64000000
},
"grossScenarioPayUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
"caseBAlsoIncludeUncertainStandby": {
"type": "object",
"additionalProperties": false,
"required": [
"countedHours",
"overtimeHours",
"straightTimeEarningsUsd",
"additionalOvertimePremiumUsd",
"grossScenarioPayUsd"
],
"properties": {
"countedHours": {
"type": "number",
"minimum": 0,
"maximum": 168
},
"overtimeHours": {
"type": "number",
"minimum": 0,
"maximum": 128
},
"straightTimeEarningsUsd": {
"type": "number",
"minimum": 0,
"maximum": 168000000
},
"additionalOvertimePremiumUsd": {
"type": "number",
"minimum": 0,
"maximum": 64000000
},
"grossScenarioPayUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
"grossDifferenceUsd": {
"type": "number",
"minimum": 0,
"maximum": 232000000
}
}
},
"withholdingReasons": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 0,
"maxItems": 0
}
}
},
"else": {
"properties": {
"scenarios": {
"const": null
},
"withholdingReasons": {
"type": "array",
"items": {
"type": "string"
},
"minItems": 1,
"maxItems": 3
}
}
}
}
]
}Illustrative example JSON record
This fixed example is published for inspection and integration testing. Its record timestamp is not an evidence-verification timestamp.
{
"schemaVersion": "1.0.0",
"instrument": "dn.human-workweek-scenario",
"sourceReviewDate": "2026-11-12",
"recordCreatedAt": "2026-11-12T12:00:00.000Z",
"evidenceVerifiedAt": null,
"inputBasis": "user_supplied_scenario",
"externalRequestsMadeByTool": false,
"inputs": {
"weekAlias": "Illustrative workweek A",
"workerScope": "assumed_covered_nonexempt_hourly",
"payStructure": "single_rate_no_other_compensation",
"nonoverlappingHours": true,
"hourlyRateUsd": 30,
"scheduledActiveHours": 38,
"afterHoursActiveHours": 3,
"otherKnownCompensableHours": 1,
"uncertainStandbyHours": 4
},
"scenarios": {
"caseAEnteredKnownHours": {
"countedHours": 42,
"overtimeHours": 2,
"straightTimeEarningsUsd": 1260,
"additionalOvertimePremiumUsd": 30,
"grossScenarioPayUsd": 1290
},
"caseBAlsoIncludeUncertainStandby": {
"countedHours": 46,
"overtimeHours": 6,
"straightTimeEarningsUsd": 1380,
"additionalOvertimePremiumUsd": 90,
"grossScenarioPayUsd": 1470
},
"grossDifferenceUsd": 180
},
"withholdingReasons": [],
"limitations": [
"For an expressly assumed U.S. FLSA-covered, nonexempt hourly worker and a single regular hourly rate with no other includable compensation only.",
"Case A and Case B are assumptions about hours, not the minimum and maximum pay legally owed. The tool does not decide whether standby time is compensable.",
"No employee/contractor classification, exemption decision, minimum-wage test or state-law assessment is performed.",
"Multiple rates, bonuses, commissions, tips, piecework, fluctuating-workweek methods, special statutory exceptions, taxes and deductions are outside scope.",
"The record is not a payroll record or legal opinion; do not enter personal employee information."
],
"sourceRefs": [
"USC-29-207",
"DOL-FS17A",
"DOL-FS17E",
"DOL-FS22",
"DOL-FS23",
"DOL-FS21",
"DOL-2026-RULEMAKING",
"OIRA-AA46-20261028"
]
}
