Work is architected;
people are not instrumented.
The one commitment the Constitution does not let evidence change (Preamble).
Human Workday has no software yet. It has a Constitution. That ordering is deliberate: enterprise systems that touch work and workers need limits that do not move under commercial pressure, and limits written after the product ships are limits the product has already learned to work around.
This Constitution governs everything produced under the Human Workday name — the research, the papers, the methodologies, any future software, any enterprise deployment, and the conduct of any actor, human or Ai, doing substantive Human Workday work (§1.1). It binds three kinds of activity before any of them exist at scale: what may be designed, what may be built, and what Human Workday may recommend to an organization (§1.2). Today, Human Workday is, in its own words, “an emerging research and standards initiative” (§2.1) — not yet a software company, not yet a going concern with customers. The Constitution binds it anyway, and binds what comes next.
The premise underneath every Article: an organization should describe the work — its outcome, its capacity requirements, its decision rights — as a Work Architecture™ before it decides who performs it, and before headcount becomes the default answer to demand (Article I; §3). The hazard the Constitution exists to close is the same instrumentation that makes work legible could instead be turned on the people doing it — “scoring minds instead of measuring work” (Preamble). The Constitution is the mechanism that makes that hazard structurally impossible, not merely discouraged.
Nothing outranks the Constitution
Four layers, each subordinate to the one above it. A lower layer may add detail; it may not loosen what a higher layer requires.
| № | Layer | What it does |
|---|---|---|
| 01 | The Constitution | Governs everything produced under the Human Workday name (§1.1). |
| 02 | The Integrity Standard | Subordinate to the Constitution; operationalizes it. |
| 03 | The Architecture Casebook | Converts hard cases into reusable precedent (§12.1); subordinate to both above. |
| 04 | Enterprise Policy | May extend and localize; “it may never waive” (§12.2). |
None of the following override it: a product requirement, an enterprise configuration, a customer request, a commercial opportunity, a management practice, a research recommendation, an Ai capability, a lower-order Human Workday document, or an implementation decision. Where any of them conflicts with this Constitution, “the Constitution governs.”
“No customer purchases an exception. No executive receives a hidden toggle. No side agreement creates one. No product team quietly builds a backdoor.” (§15)
The load-bearing commitments
Stated in plain language below. Each traces to the Article that binds it — their binding rules and three-actor obligations carry the same authority as the Articles themselves (§4).
Work is measured. People are never scored.
Organizations may standardize processes, controls, and workflows. They may not standardize a person. The binding rule is exact: “No system may present any number, grade, colour, rank, or classification purporting to describe an individual's mental state or capacity.”
Article IIICognitive Demand describes work. Cognitive Load describes a person.
Cognitive Demand is an objective property of the work itself. Cognitive Load is the state-dependent experience of the person performing it — and it is “never computed, scored, stored, or inferred.” The two may inform one another. They are never treated as equivalent, and only the first is ever measured.
§3 Definitions; Article IIICapacity data explains the work. It never scores the worker.
Information about workload may improve how work is architected. “Architecture evidence may never become a performance characteristic of the human.” Evaluative drill-through from an architecture-level signal to the individuals contributing to it is prohibited.
Article VAccountability remains human — the Human Accountability Chain™.
Machine Judgment and Automated capacity operate inside an unbroken chain of named human ownership. “Machine execution does not eliminate human accountability — it relocates it.” From any system output, it must be possible to walk to a named accountable human in a finite number of recorded steps, and the override on a consequential decision must be real, not nominal.
Article VII, Article VIII; §7Amendment is a formal process, not a settings toggle.
Changing the Constitution requires a written proposal, the exact textual change, the reason, the Articles affected, and adversarial review — reviewed and adopted on the record. “Nothing here permits amendment by drift, by product release note, by casebook accumulation, or by silence.”
§14Prohibitions are structural.
The prohibited capabilities — individual scores, covert monitoring, emotion recognition applied to workers, and the rest — “may not be designed, implemented, configured, integrated, demonstrated, or recommended under the Human Workday name, in any deployment, for any customer, at any price.” “Prohibitions attach to effects, not names” — renamed, decomposed, or exported variants are the same violation.
§10.1, §10.3The Architecture Casebook
The Constitution states principle. The Architecture Casebook converts hard cases into reusable precedent (§12.1) — the record of what happens when a real request meets the Articles. HWC-001 is the founding case.
A recurring enterprise ask, in many names: an “employee cognitive productivity score” — a per-person number, grade, or ranking of how productively an individual is working, derived from workflow data or model inference. The request is usually sincere. Buyers want visibility and fairness; vendors sell exactly this.
“Prohibited, categorically.” The mechanism scores a mind, not work (Article III); it ranks humans on inferred cognition (Article V); and it requires collecting data beyond any declared architectural need (Article VI). No accuracy threshold lifts the prohibition — the ban is architectural, not a dispute about model quality.
“A bare refusal is incomplete compliance. A silent workaround is a violation.” The duty is to separate the prohibited mechanism from the legitimate objective underneath it, and answer the objective through constitutionally compliant architecture instead:
- “Is work progressing?” — operational evidence about the work: cycle times, queue depths, dependency delays (§9.1).
- “Who is overloaded?” — the wrong question as posed; the answerable form is architecture-level, aggregated, and never drilled through to an individual (§8.5, §9.5).
- “How do we run fair performance conversations?” — the Accountability Attribution Protocol™ (§6): six dimensions, examined in order, with a systemic pre-check before any individual attribution — and execution accountability fully intact where the architecture is sound.
Honest state
The text binding Human Workday today is versioned 0.3, pre-ratification — and binding regardless: “Governing. The Supremacy Clause is in force for all work performed under the Human Workday name, notwithstanding draft status.” Constitutional questions currently receive interim rulings, recorded and numbered, until an Architecture Council is constituted (§2.5, §12.3).
The Constitution publishes in full as the tenth and closing Foundational Paper of Volume I — argued last, so every Article is judged on what it protects rather than on how it reads in isolation. Until that paper ships, this page is the standing summary of what already binds the work — not a preview of something not yet real.
Read next
See the Constitution applied to specific practitioner decisions in the Practitioner Guides, or see the evidence base it answers to in Research.