Interprets conditions
adapts- Situated judgment
- Detection and coordination
- Verification and intervention
- Recovery under variation
HAOP is the work-system design framework for locating how human, AI, and organizational performers jointly produce work.
It shows where verification, grounding, authority, and correction must be designed before representation becomes consequence. The work system, not the AI product, is the unit of success and failure.
Piloting an AI product? Examine the work system before you scale it. HAOP workflow pilots →
Framework under active development · pilots and research collaborations invited
HAOP extends Human and Organizational Performance into work systems where AI materially shapes what is seen, decided, or done. AI does not need autonomy or intention to operate at performer level. It needs a delegated or absorbed function whose variability can materially shape what is seen, prioritized, decided, authorized, or executed.
Performer is a functional category, not a moral one. It implies no consciousness, intention, personhood, or moral agency in the AI. The organization is in the register because it allocates the functions and authors the conditions under which the other two perform.
Human control is not a label. It must be designed.
Operating mode classifies what an AI system does in the work. A product purchased to answer questions may operate as an Orchestrator when it is permitted to plan, browse, and invoke tools before responding. Walk the modes and watch the control surface change.
The five classes are a baseline operational register within HAOP's scope. They are connected, not mutually exclusive, and not exhaustive of AI risk.
Embodied AI carries energy, mass, speed, force, and software-defined or adaptive action into physical work.
Surveillance, scoring, pacing, scheduling, and machine-generated attribution can reduce autonomy, intensify work, suppress reporting, and make power continuous.
AI can reshape attention, situational awareness, competence, judgment, alarm burden, and verification demand. Verification Overrun appears here, but the condition is authored through work-system design.
Representations are repeatedly summarized, classified, merged, selected, stored, retrieved, and transformed until provenance, context, uncertainty, low-frequency conditions, or situated knowledge disappears.
Consequential control fragments across vendors, procurement, configuration, leadership, and local operation while verification and accountability concentrate at the visible point of use.
The work sets the demand for verification. The workflow supplies the capacity. A person can be present and still lack the knowledge, evidence, time, or authority the check requires.
Human, AI, and organizational performers select, transform, route, suppress, approve, or act.
A consequential transition approaches: after passage, correction becomes materially harder.
The verification function defines what must be established under the operating condition.
Knowledge, evidence, time, and authority must all satisfy the requirement.
A functional gate can proceed, return, revise, reject, pause, defer, constrain, or escalate.
ARECC (Anticipate, Recognize, Evaluate, Control, and Confirm) is inherited from industrial hygiene. HAOP's deposited contribution is its translation across the three performers and the verification architecture.
Establish True Function and unacceptable outcomes before selecting a product.
Reconstruct work-as-done, decompose functions, and locate consequential transitions.
Test Verification Capacity, grounding, Anchor Access, reversibility, and alternatives.
Allocate functions and engineer gates, evidence, constraints, pause, and handback.
Deploy, learn, monitor, and revalidate as the work and operating conditions change.
Version 1.0 deposits the application. The method continues to develop; Revision 6.0.1 Section VIII is the current statement.
Each resource carries its publication or development status. The live diagnostic is an entry tool, not a safety certification and not the complete HAOP method.
Run the deposited nine-question test against one bounded workflow. Read the gap between work-as-imagined and work-as-done, and where the five hazards enter. No maturity score.
The controlling source for the three performers, five hazards, operating modes, Accountability by Control, grounding, verification, and the applied method.
The HAOP Workbook, the HAOP Operating Manual, and the complete AI Deployment Safety Data Sheet remain in development. The ADSDS name and bidirectional purpose are deposited.
Bring a bounded workflow and the people who perform it. A pilot begins before product selection: you leave knowing where control is real, what the work requires, and whether AI belongs in the workflow at all.