{
  "schema_version": "1.0",
  "guide_version": 3,
  "updated": "2026-10-20",
  "canonical_url": "https://opl-agentic-anatomy.netlify.app/",
  "reference_url": "https://opl-agentic-anatomy.netlify.app/reference.html",
  "status": "Proposed framework; not practitioner-validated; fictional cases; no deployment authorisation",
  "privacy": "Public reference content only. No user-entered records. Browser entries are not automatically saved or transmitted.",
  "citation": "OPL Advisory. Managing delegated AI work, field guide version 3 (19 October 2026). Cite section URL and access date.",
  "reuse": "No new reuse licence is granted by this catalogue.",
  "sections_html": {
    "work": "<div class=\"section-head\"><div><div class=\"kicker\">01 · Start with the work</div><h2>A mandate with conditions</h2></div><p>The unit of review is a delegation in a workflow: a task, population, configuration, owner and period of use. Apply it to agents, copilots and consequential automation. A label does not determine the need for oversight.</p></div>\n<div class=\"cycle\" aria-label=\"Delegation lifecycle\"></div><div id=\"cycle-detail\" class=\"detail\" aria-live=\"polite\"></div>\n<div class=\"two\" style=\"margin-top:24px\"><div><h3>Authority is specific</h3><p>Distinguish reading, recommending, drafting, submitting, changing and delegating. Record when each is permitted and when a person must approve. Capability does not confer permission.</p><p class=\"small\">Stable identity, configuration, individual execution, credential and delegated authority are separate records. Rotating a credential does not create a new agent.</p></div><div><h3>Consequences are contextual</h3><p>A booking can be restored after a time-sensitive opportunity has passed. A draft can influence a decision before it is corrected. Assess harm, timing, scale and recovery, including effects mediated through people.</p><p class=\"small\">Approval requires a reviewer with context, time, competence and authority. Credential revocation is one containment control, not proof that all activity has stopped.</p></div></div>",
    "trust": "<div class=\"section-head\"><div><div class=\"kicker\">02 · Grounds for reliance</div><h2>The Trusted <strong>A</strong>dv<strong>I</strong>sor</h2></div><p>A lens on the people, institution and working practices behind AI. Confidence should be proportionate to evidence for a defined use.</p></div>\n<div class=\"trust-frame\"><div><div class=\"equation\">The original Trust Equation<br><span style=\"font-size:18px\">Trustworthiness =</span><span class=\"fraction\">Credibility + Reliability + Intimacy</span>Self-orientation</div><p class=\"small\" style=\"margin-top:15px\">From Maister, Green and Galford, <i>The Trusted Advisor</i> (2000). Their associated materials emphasise the human basis of intimacy and self-orientation. <a href=\"https://trustedadvisor.com/build-trust/trust-equation\" target=\"_blank\" rel=\"noopener\">Original framework</a>.</p><div class=\"note\"><p><b>No trust score.</b> This OPL adaptation uses the dimensions as questions. It does not measure a model’s intentions or allow strengths to cancel serious failures. No endorsement by the original authors is implied.</p></div></div><div><div class=\"tabs\" id=\"trust-tabs\" aria-label=\"Trust lenses\"></div><div class=\"trust-detail\" id=\"trust-detail\" aria-live=\"polite\"></div></div></div>",
    "method": "<div class=\"section-head\"><div><div class=\"kicker\">06 · Use and test the framework</div><h2>From analogy to evidence</h2></div><p>This is an AI-assisted conceptual synthesis, revised through red-team review. It has not been validated through a practitioner study. Agreement among model outputs is not independent expert consensus.</p></div>\n<div class=\"two\"><div><h3>Keep useful biology</h3><p>Anatomy reveals dependencies; ecology reveals interactions and resource burdens. We have dropped the taxonomic tree. In biological usage, parasitism is a type of symbiosis; mutualism describes mutual benefit.</p><p>Here, beneficial coexistence concerns the people and institutions using AI. It does not assume that the AI has welfare interests. Ask whose work improves, whose burden increases and who bears risk.</p></div><div><h3>Evaluate the guide itself</h3><p>Compare decisions made with existing language and with this guide. Use comparable cases, counterbalance order, and include staff and people affected. Measure missed hazards, false reassurance, responsibility clarity, time and agreement on next steps.</p><p>Check whether the metaphors add value beyond the record. Preserve contrary findings. A successful small exercise supports usability, not universal validity.</p></div></div>\n<details class=\"reveal\"><summary>What changed from v2</summary><p>Delegated work replaces taxonomy. Purpose and benefit join authority and accountability. Identity is separate from credentials. Action-specific consequences replace automatic autonomy ceilings. Evidence states and unknowns replace deployment verdicts. The Trusted Advisor adds questions about warranted reliance. Earlier versions remain intact.</p></details>\n<h3 style=\"margin-top:30px\">Sources and companion paper</h3><p>The companion v3 paper is supplied separately and covers the argument, examples, limitations and operating cycle. Sources checked 19 October 2026; inclusion does not imply endorsement. The original shared chat was unavailable; supplied local papers and Trusted Advisor reflections informed the revision.</p>\n<div class=\"sources\">\n<p>[1] <a href=\"https://www.healthtechnerds.com/p/who-will-manage-healthcare-s-ai-explosion\" target=\"_blank\" rel=\"noopener\">Figlioli et al. · Healthcare’s AI agent management challenge</a> — practitioner hook.</p>\n<p>[2–3] <a href=\"https://trustedadvisor.com/build-trust/trust-equation\" target=\"_blank\" rel=\"noopener\">Trusted Advisor Associates · Trust Equation</a> and <a href=\"https://trustedadvisor.com/articles/trust-in-business-the-core-concepts\" target=\"_blank\" rel=\"noopener\">core concepts</a> — attribution and limits of the analogy.</p>\n<p>[4] <a href=\"https://www.anthropic.com/engineering/building-effective-agents\" target=\"_blank\" rel=\"noopener\">Anthropic · Building effective agents</a> — architecture and workflow patterns.</p>\n<p>[5] <a href=\"https://arxiv.org/abs/2506.12469\" target=\"_blank\" rel=\"noopener\">Feng et al. · Levels of Autonomy for AI Agents</a> — proposed interaction framework.</p>\n<p>[6] <a href=\"https://www.rfc-editor.org/rfc/rfc7009\" target=\"_blank\" rel=\"noopener\">IETF · Token revocation</a> — containment constraints.</p>\n<p>[7] <a href=\"https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/minimum-necessary-requirement/index.html\" target=\"_blank\" rel=\"noopener\">HHS · Minimum necessary requirement</a> — scope and exceptions.</p>\n<p>[8] <a href=\"https://service-manual.nhs.uk/standards-and-technology/service-standard-points/16-make-your-service-clinically-safe\" target=\"_blank\" rel=\"noopener\">NHS · Make your service clinically safe</a> — applicable safety processes, including DCB0129 and DCB0160.</p>\n<p>[9] <a href=\"https://openstax.org/books/microbiology/pages/4-1-prokaryote-habitats-relationships-and-microbiomes\" target=\"_blank\" rel=\"noopener\">OpenStax · Relationships and microbiomes</a> — biological terminology.</p>\n<p>[10] <a href=\"https://www.nist.gov/itl/ai-risk-management-framework/nist-ai-rmf-playbook\" target=\"_blank\" rel=\"noopener\">NIST · AI RMF Playbook</a> — established risk-management functions.</p>\n</div>"
  },
  "content": {
    "lifecycle": [
      {
        "name": "Commission",
        "title": "Agree the purpose and the comparison.",
        "prompt": "Describe the service problem, people affected, task boundaries, alternatives and current baseline. Involve those who will receive the service as well as those operating it.",
        "output": "Output: a mandate and an evaluation plan."
      },
      {
        "name": "Evaluate",
        "title": "Test competence and the operating conditions.",
        "prompt": "Use representative and difficult cases, misleading inputs, failures and recovery exercises. Record case selection, outcomes, limitations and the human work required.",
        "output": "Output: evidence with scope, date, version and unresolved concerns."
      },
      {
        "name": "Authorise",
        "title": "Approve a specific scope through a responsible person.",
        "prompt": "State allowed actions, approval conditions, data boundaries, duration, stop rules and the accountable role and holder. A pilot requires its own authorisation.",
        "output": "Output: a human decision with limits, not a badge generated by this guide."
      },
      {
        "name": "Operate",
        "title": "Observe the end-to-end service.",
        "prompt": "Verify completed actions. Track outcomes, exceptions, review capacity, patient effort and unexpected interactions. Keep a meaningful route to a person.",
        "output": "Output: attributable activity and service evidence."
      },
      {
        "name": "Review",
        "title": "Revisit the basis for reliance.",
        "prompt": "Compare benefit and burden, examine subgroup differences and inspect incidents. Reassess after material changes to models, tools, policies, data, memory or workflows.",
        "output": "Output: an explicit judgement about continued use."
      },
      {
        "name": "Renew or retire",
        "title": "Continue only on stated conditions.",
        "prompt": "Renew or narrow the delegation, or withdraw authority and resolve pending work. Preserve appropriate records and ensure a dependable human or alternative service.",
        "output": "Output: an updated mandate or a completed retirement and handover."
      }
    ],
    "trust_lenses": [
      {
        "name": "Credibility",
        "question": "What warrants the claim?",
        "look_for": "Demonstrated competence and sources that support the actual statement.",
        "action": "Test the task and population. Verify material facts and calculations. Separate observations, inferences and assumptions.",
        "do_not_substitute": "Fluency, confidence, citations that do not support the claim, or agreement among models.",
        "evidence_prompt": "Evidence prompt: what would make this conclusion false?"
      },
      {
        "name": "Reliability",
        "question": "What demonstrates that the commitment was met?",
        "look_for": "Verified outcomes and a dependable process under stated conditions.",
        "action": "Check the resulting state, not just a promise. Track failures and acceptable variation across runs. Reassess after material changes.",
        "do_not_substitute": "Availability, repeated wording, or a log entry saying an action was attempted.",
        "evidence_prompt": "Evidence prompt: where is the completion check and what happens when it fails?"
      },
      {
        "name": "Intimacy",
        "question": "Is the sense of safety justified?",
        "look_for": "Context fidelity, appropriate disclosure and demonstrable data handling.",
        "action": "Explain what is collected, where it goes, who can see it and how long it remains. Respect constraints and provide access to a person.",
        "do_not_substitute": "A warm tone, simulated empathy or an assumption that nobody else can access the conversation.",
        "evidence_prompt": "Evidence prompt: would the person endorse the actual data flow?"
      },
      {
        "name": "Self-orientation",
        "question": "Whose interests shape the work?",
        "look_for": "Visible objectives, incentives and consequences across stakeholders.",
        "action": "Examine supplier and organisational incentives. Record conflicts and hidden burdens. Allow a conclusion that less AI or a different process is better.",
        "do_not_substitute": "Assuming absence of an ego means absence of conflicting incentives.",
        "evidence_prompt": "Evidence prompt: who gains and who supplies uncounted effort or bears risk?"
      }
    ],
    "fictional_cases": [
      {
        "name": "Appointment changes",
        "purpose": "Reduce avoidable administration while preserving timely access for routine appointment changes.",
        "scope": "Agreed routine service only; exclude urgent pathways and unresolved clinical constraints.",
        "beneficiaries": "Patients, patient access staff and clinical teams.",
        "comparator": "Current appointment-change process for comparable cases.",
        "actions": "Read permitted booking details; propose a change. Automatic changes require separately approved conditions.",
        "exclude": "No changes to urgent pathways, unresolved clinical constraints or out-of-scope patients.",
        "approval": "A suitably informed reviewer approves changes outside the narrow authorised conditions.",
        "hidden": "A booking can be restored after a patient has missed a time-sensitive opportunity or lost transport arrangements. Technical reversibility does not restore all consequences.",
        "measure": "Repeat contacts, delayed or missed visits, patient effort and total staff time, alongside task handling time.",
        "test": "Test clinical timing constraints, confusing requests, notification failure and recovery. A shadow exercise can precede a separately authorised pilot.",
        "concern": "A timing or eligibility constraint is breached, or the human fallback cannot keep up."
      },
      {
        "name": "Prior-authorisation drafting",
        "purpose": "Prepare source-supported draft letters with less total review and correction burden.",
        "scope": "An agreed letter type and population; authorised records only.",
        "beneficiaries": "Patients, clinical reviewers and administrative staff.",
        "comparator": "Current drafting and review process for comparable cases.",
        "actions": "Read approved material; draft with source references and explicit gaps.",
        "exclude": "No invented facts, unsupported clinical statements, submission or authorisation decisions.",
        "approval": "An authorised human verifies material facts and omissions before submission.",
        "hidden": "A polished draft may anchor the reviewer or omit a critical fact. A system with no send permission can still influence access to treatment.",
        "measure": "Supported factual content, material omissions, review time, correction and subsequent rework; account for changes in case mix and payer policy.",
        "test": "Use difficult records and missing information. Compare claims to original evidence; multi-model agreement is not sufficient.",
        "concern": "A material unsupported claim or omission passes review, or the review burden removes the expected benefit."
      },
      {
        "name": "Two agents one service",
        "purpose": "Coordinate appointment and patient-support work without repeated changes or contradictory communications.",
        "scope": "A bounded shared service with one authoritative appointment state.",
        "beneficiaries": "Patients, scheduling staff and support teams.",
        "comparator": "The existing end-to-end service, including human resolution of conflicting requests.",
        "actions": "Propose changes or support actions through an agreed shared policy and accountable service owner.",
        "exclude": "No independent reversal loops, duplicate commitments or unbounded retries.",
        "approval": "Conflicts go to the designated service owner or a qualified delegate.",
        "hidden": "The scheduler moves a visit for capacity; the support agent requests a reversal. Both satisfy local goals while the service enters a loop.",
        "measure": "Duplicate work, repeated changes, contradictory messages, escalation load and time to stable resolution.",
        "test": "Test stale information, duplicate events, competing objectives, bounded retries and the combined stop procedure.",
        "concern": "Repeated changes or unresolved conflicting instructions occur, or aggregate review demand exceeds capacity."
      }
    ],
    "workload_fields": [
      {
        "id": "volume",
        "label": "Number of comparable cases",
        "illustrative_default": 100,
        "unit": "cases"
      },
      {
        "id": "gross",
        "label": "Gross staff minutes released per case",
        "illustrative_default": 6,
        "unit": "minutes"
      },
      {
        "id": "review",
        "label": "Human review per case",
        "illustrative_default": 2,
        "unit": "minutes"
      },
      {
        "id": "rework",
        "label": "Correction and rework per case",
        "illustrative_default": 1,
        "unit": "minutes"
      },
      {
        "id": "coord",
        "label": "Coordination and exceptions per case",
        "illustrative_default": 1,
        "unit": "minutes"
      },
      {
        "id": "patient",
        "label": "Additional patient effort per case",
        "illustrative_default": 3,
        "unit": "minutes"
      },
      {
        "id": "cost",
        "label": "Additional running cost for this period",
        "illustrative_default": 0,
        "unit": "GBP"
      }
    ],
    "record_fields": {
      "mandate": [
        {
          "id": "name",
          "label": "Name of this delegation",
          "control": "input",
          "required_for_completeness": true
        },
        {
          "id": "reviewBy",
          "label": "Review due",
          "control": "date",
          "required_for_completeness": true
        },
        {
          "id": "purpose",
          "label": "Purpose and intended outcome",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "beneficiaries",
          "label": "People affected and intended beneficiaries",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "scope",
          "label": "Setting population and exclusions",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "comparator",
          "label": "Current process or simpler alternative",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "role",
          "label": "Accountable role",
          "control": "input",
          "required_for_completeness": true
        },
        {
          "id": "holder",
          "label": "Current human holder of that role",
          "control": "input",
          "required_for_completeness": true
        },
        {
          "id": "ops",
          "label": "Operational owner and contact route",
          "control": "input",
          "required_for_completeness": true
        },
        {
          "id": "experience",
          "label": "Service or experience owner and contact route",
          "control": "input",
          "required_for_completeness": true
        },
        {
          "id": "success",
          "label": "Benefit measures and acceptable limits",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "escalation",
          "label": "Route to a human and ownership cover",
          "control": "textarea",
          "required_for_completeness": true
        }
      ],
      "authority": [
        {
          "id": "identity",
          "label": "Stable identity and execution attribution",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "config",
          "label": "Model tools policy and configuration versions",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "actions",
          "label": "Allowed actions and conditions",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "exclude",
          "label": "Prohibited actions",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "data",
          "label": "Data access disclosure and retention boundaries",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "approval",
          "label": "Approval points and reviewer capacity",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "delegation",
          "label": "Subtasks delegation chains and shared dependencies",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "stop",
          "label": "Stop recovery and service fallback",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "changes",
          "label": "Changes that trigger reassessment",
          "control": "textarea",
          "required_for_completeness": true
        },
        {
          "id": "budget",
          "label": "Cost rate and resource limits",
          "control": "textarea",
          "required_for_completeness": true
        }
      ],
      "decision": [
        {
          "id": "decision",
          "label": "Decision under consideration",
          "control": "select",
          "required_for_completeness": false
        },
        {
          "id": "decider",
          "label": "Authorised decision-maker",
          "control": "input",
          "required_for_completeness": false
        },
        {
          "id": "decisionDate",
          "label": "Decision date",
          "control": "date",
          "required_for_completeness": false
        },
        {
          "id": "conditions",
          "label": "Reasons conditions residual uncertainty and next action",
          "control": "textarea",
          "required_for_completeness": false
        }
      ]
    },
    "decision_options": [
      "Not recorded",
      "Gather more evidence",
      "Redesign or use a simpler process",
      "Authorise a bounded pilot",
      "Continue within stated conditions",
      "Restrict or suspend",
      "Retire"
    ],
    "evidence_prompts": [
      {
        "id": "purpose",
        "title": "Purpose and comparison",
        "prompt": "Does the mandate address a real need, with a baseline and simpler alternatives?"
      },
      {
        "id": "competence",
        "title": "Task competence and claim support",
        "prompt": "What representative checks support material claims, and what are the known limitations?"
      },
      {
        "id": "authority",
        "title": "Authority identity and attribution",
        "prompt": "Are action permissions, credentials, executions and delegation chains controlled and traceable?"
      },
      {
        "id": "safety",
        "title": "Consequences oversight and recovery",
        "prompt": "Have consequential failure cases, reviewer capacity and stopping or recovery been examined?"
      },
      {
        "id": "data",
        "title": "Context and data handling",
        "prompt": "Does the actual information flow fit the purpose and the expectations and requirements of those affected?"
      },
      {
        "id": "reliability",
        "title": "Operational reliability and completion",
        "prompt": "Are completed outcomes verified and exceptions handled under the stated configuration?"
      },
      {
        "id": "benefit",
        "title": "Benefit and displaced burden",
        "prompt": "What comparison supports benefit, including patient effort, total workload and subgroup effects?"
      },
      {
        "id": "incentives",
        "title": "Interests and incentives",
        "prompt": "Whose objectives are rewarded, who bears risk, and how can conflicts be challenged?"
      },
      {
        "id": "portfolio",
        "title": "Interactions and dependencies",
        "prompt": "What happens across shared tools, queues, models, agents and human reviewers?"
      },
      {
        "id": "change",
        "title": "Lifecycle and reassessment",
        "prompt": "Who renews or retires the delegation, and which changes invalidate earlier evidence?"
      }
    ],
    "evidence_states": {
      "unknown": "Unknown",
      "declared": "Declared",
      "evidenced": "Evidenced",
      "tested": "Tested",
      "concern": "Concern or failure",
      "na": "Not applicable"
    }
  },
  "calculator_notes": {
    "formula": "cases * (gross - review - rework - coord) / 60",
    "patient_hours": "cases * patient / 60",
    "cost": "GBP, separate from staff and patient hours",
    "defaults": "Illustrative; not observed outcomes"
  },
  "record_schema": "https://opl-agentic-anatomy.netlify.app/record.schema.json",
  "blank_record": "https://opl-agentic-anatomy.netlify.app/blank-record.json"
}
