{
  "status": "research crosswalk, not conformity assessment",
  "draftPagesRead": 29,
  "rows": [
    {
      "id": "HO-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "1",
      "pages": [
        7
      ],
      "verbalForce": "scope",
      "topic": "Provider-oriented, cross-sector scope",
      "paloBasis": "Case File context, system registry and risk-route assessment",
      "gap": "The presentation must distinguish applicability from a generic maturity score.",
      "proposedExtension": "Pin provider/deployer roles, system, intended use, jurisdictions and version before selecting controls.",
      "acceptanceEvidence": "Reject a scope record with undetermined roles or unreviewed applicability.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "2",
      "pages": [
        7
      ],
      "verbalForce": "normative references",
      "topic": "Dependencies on risk, logging and transparency drafts",
      "paloBasis": "source registry and semantic mappings",
      "gap": "A mapping to one draft does not cover its dependencies.",
      "proposedExtension": "Version-pin each referenced source and maintain change-impact decisions.",
      "acceptanceEvidence": "Change a referenced draft version and require crosswalk review.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-3-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "3.4",
      "pages": [
        11,
        12,
        13
      ],
      "verbalForce": "definitions",
      "topic": "Human role, overload and three different timing concepts",
      "paloBasis": "ctrl-human-review; system-card humanOversight",
      "gap": "Approval timestamps do not measure the complete human-to-effect loop.",
      "proposedExtension": "Distinguish reaction window, minimum feasible human intervention, response initiation and actuator latency.",
      "acceptanceEvidence": "Use event timestamps with a common reference and documented clock uncertainty.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.1",
      "pages": [
        13
      ],
      "verbalForce": "objectives and informative notes",
      "topic": "Effective oversight protects people and fundamental rights",
      "paloBasis": "ctrl-human-review; impact assessment",
      "gap": "A business-loss-only definition misses harm to affected people.",
      "proposedExtension": "Use a harm scenario and causal chain; justify oversight within the risk-control hierarchy.",
      "acceptanceEvidence": "Record technical prevention options and their adequacy before assigning human responsibility.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.1",
      "pages": [
        13
      ],
      "verbalForce": "shall",
      "topic": "Identify risk scenarios",
      "paloBasis": "Frame, Assess; ctrl-adversarial-testing",
      "gap": "Generic use-case descriptions do not identify each agent/tool causal chain.",
      "proposedExtension": "Scenario IDs link outputs, hazards, downstream effects and affected groups.",
      "acceptanceEvidence": "Trace each consequential action to an approved scenario and owner.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.2",
      "pages": [
        14
      ],
      "verbalForce": "shall",
      "topic": "Determine a reaction timeframe for each scenario",
      "paloBasis": "kpi-incident-triage-time; action/capability expiry",
      "gap": "TTL and incident-triage time are not time-to-harm.",
      "proposedExtension": "Add reaction-window bounds and their operational justification.",
      "acceptanceEvidence": "Measure from the relevant hazardous output to mitigation taking effect, with clock uncertainty.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.3",
      "pages": [
        14
      ],
      "verbalForce": "shall",
      "topic": "Select and justify collectively adequate measures",
      "paloBasis": "ctrl-human-review; lifecycle Control gate",
      "gap": "No typed per-scenario allocation of review modes and measured response budget.",
      "proposedExtension": "Link retrospective, alert-triggered and continuous measures to each scenario.",
      "acceptanceEvidence": "Show that the combined operational loop fits the available time under specified load.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.4",
      "pages": [
        14,
        15
      ],
      "verbalForce": "shall",
      "topic": "When real-time human intervention is infeasible",
      "paloBasis": "Authority gates and guarded execution; preview resource holds",
      "gap": "An approval button cannot protect a subsecond external effect after it starts.",
      "proposedExtension": "Specify tested automated protection plus retrospective review; never substitute nominal oversight.",
      "acceptanceEvidence": "Fast-action fixture holds or applies a validated protective path; human-only configuration fails.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-5",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.5",
      "pages": [
        15
      ],
      "verbalForce": "shall",
      "topic": "Overload and conflicts across simultaneous scenarios",
      "paloBasis": "AI-literacy and human-review controls; swarm exposure bounds",
      "gap": "Exposure reservation is not reviewer-capacity reservation.",
      "proposedExtension": "Measure reviewer queues, concurrent alerts, fatigue and conflicting duties; define backup coverage.",
      "acceptanceEvidence": "Representative-user testing at peak joint load, including correlated alert bursts.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-2-6",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.2.6",
      "pages": [
        15
      ],
      "verbalForce": "shall",
      "topic": "Review assignments after changes or monitoring findings",
      "paloBasis": "ctrl-change-gate; assurance signals; immutable version records",
      "gap": "Fitness invalidation does not yet reopen typed oversight qualifications.",
      "proposedExtension": "Invalidate scenario qualification on model, tool, UI, staffing, workload or deployment change.",
      "acceptanceEvidence": "Version change prevents reuse of the old assessment until accountable requalification.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.1",
      "pages": [
        15
      ],
      "verbalForce": "shall",
      "topic": "Combine oversight categories per scenario",
      "paloBasis": "PALO lifecycle tailoring",
      "gap": "A single human-in/on/out-loop label loses scenario-specific adequacy.",
      "proposedExtension": "Allow several modes per scenario and document why their combination is sufficient.",
      "acceptanceEvidence": "Two scenarios on one agent can require different modes without ambiguity.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-2-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.2.1",
      "pages": [
        15,
        16
      ],
      "verbalForce": "shall",
      "topic": "Retrospective review interface and context",
      "paloBasis": "Receipts, attestations, trace records; system cards",
      "gap": "Technical event logs alone do not demonstrate a usable review interface.",
      "proposedExtension": "Associate input references, output, model/version, available scores, alarms and human annotations.",
      "acceptanceEvidence": "Reconstruct a selected trajectory through authorized evidence access; missing data remains visible.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-2-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.2.2",
      "pages": [
        16
      ],
      "verbalForce": "shall",
      "topic": "Retention, navigation and corrective-action trace",
      "paloBasis": "Lineage, privacy, retention and incident contracts",
      "gap": "Retention periods and filters are not qualified against harm discovery and review tasks.",
      "proposedExtension": "Define privacy-minimized review retention, scenario filters and annotation-to-remedy links.",
      "acceptanceEvidence": "Retrieve a historical case within the justified retention window and verify access restrictions.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-2-3-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.2.3.1",
      "pages": [
        16,
        17
      ],
      "verbalForce": "shall",
      "topic": "Verify review effectiveness and fallback",
      "paloBasis": "Generic assurance record and adversarial test controls",
      "gap": "No reviewed user-study evidence in this assessment establishes oversight effectiveness.",
      "proposedExtension": "Specify acceptance criteria and degraded-interface/logging fallback.",
      "acceptanceEvidence": "Representative reviewers detect hazardous cases; outage drill retains required review capability.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-2-3-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.2.3.2",
      "pages": [
        17
      ],
      "verbalForce": "can",
      "topic": "Possible retrospective metrics",
      "paloBasis": "KPI/KRI registry",
      "gap": "Completion rate misses false negatives, inconsistency and fatigue.",
      "proposedExtension": "Add review accuracy, missed-harm rate, time distribution, agreement and workload measurements.",
      "acceptanceEvidence": "Publish denominators, scenario mix and uncertainty; do not label suggested metrics mandatory.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-3-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.3.1",
      "pages": [
        17
      ],
      "verbalForce": "shall",
      "topic": "Design risk-calibrated notifications",
      "paloBasis": "Runtime telemetry; incident records",
      "gap": "An emitted event does not prove it reached an available human in time.",
      "proposedExtension": "Specify routing, triggering, acknowledgement and escalation contracts.",
      "acceptanceEvidence": "Measure end-to-end delivery and mitigation time, including unavailable reviewers.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-3-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.3.2",
      "pages": [
        18
      ],
      "verbalForce": "shall",
      "topic": "Perceivable, interpretable and validated alerts",
      "paloBasis": "Accessibility and explanation-comprehension packs",
      "gap": "Dashboard visibility alone does not validate alert discrimination or prioritisation.",
      "proposedExtension": "Test modality, urgency, accessibility and advance warning in the intended environment.",
      "acceptanceEvidence": "Inject noisy concurrent alerts and verify correct priority and timely action.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-4-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.4.1",
      "pages": [
        18
      ],
      "verbalForce": "shall",
      "topic": "Continuous access to operational and intervention status",
      "paloBasis": "Operational snapshot; execution and cancellation status",
      "gap": "Distributed stop availability and freshness need a reviewer-facing contract.",
      "proposedExtension": "Show current actions, stale observations, alerts and available controls separately.",
      "acceptanceEvidence": "Partitioned worker displays unknown status and cannot be reported safely stopped.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-4-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.4.2",
      "pages": [
        18
      ],
      "verbalForce": "shall plus informative guidance",
      "topic": "HMI supports judgment and protects against accidental mitigation",
      "paloBasis": "System-card explanation and accessibility controls",
      "gap": "No specific oversight HMI study or accidental-trigger evidence reviewed.",
      "proposedExtension": "Use explicit action context, uncertainty and guarded critical controls.",
      "acceptanceEvidence": "Usability trials cover accidental activation and reversible confirmation design.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-4-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.4.3",
      "pages": [
        19
      ],
      "verbalForce": "shall",
      "topic": "Functions support capability and limitation understanding",
      "paloBasis": "Knowledge Reader, system cards, evidence references",
      "gap": "A grounded answer does not demonstrate a reviewer can operate the control.",
      "proposedExtension": "Separate explanation, current-state evidence and actual intervention affordances.",
      "acceptanceEvidence": "Reviewer identifies stale data, unavailable actions and policy limitations.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-4-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.4.4",
      "pages": [
        19
      ],
      "verbalForce": "shall",
      "topic": "Verify task completion within the scenario timeframe",
      "paloBasis": "Control tests and generic governance-assurance measurements",
      "gap": "Runtime tests do not establish human task performance.",
      "proposedExtension": "Bind the oversight qualification to system/UI version, user population and load envelope.",
      "acceptanceEvidence": "Predefined task-success and timing criteria must be met before claiming effective oversight.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-3-4-5",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.3.4.5",
      "pages": [
        19
      ],
      "verbalForce": "should/can",
      "topic": "Representative usability studies and metrics",
      "paloBasis": "AI-literacy competence and comprehension indicators",
      "gap": "Suggested generic percentages are not evidence-based safety thresholds.",
      "proposedExtension": "Pre-register task success, initiation time, misinterpretation and workload criteria.",
      "acceptanceEvidence": "Compare distributions and failure cases; qualify thresholds as case-specific.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-4-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.4.1",
      "pages": [
        20
      ],
      "verbalForce": "shall",
      "topic": "Provider-deployer implementation and verification contract",
      "paloBasis": "Integration guide, enterprise adapters and case owners",
      "gap": "An API contract does not allocate staffing, competence and residual-risk acceptance.",
      "proposedExtension": "Create a provider/deployer responsibility matrix with technical, procedural and staffing prerequisites.",
      "acceptanceEvidence": "Deployer signs measured readiness evidence for each transferred measure.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-4-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.4.2",
      "pages": [
        21
      ],
      "verbalForce": "shall",
      "topic": "Residual risks and conditions of use",
      "paloBasis": "System-card limitations; assurance findings",
      "gap": "A residual-risk note needs to constrain operation when a prerequisite is absent.",
      "proposedExtension": "Link missing staffing, unavailable monitoring or unqualified connectors to operating restrictions.",
      "acceptanceEvidence": "Run configuration without required coverage; gate remains held.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-4-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.4.3",
      "pages": [
        21
      ],
      "verbalForce": "shall when applicable",
      "topic": "Deployer notification implementation specification",
      "paloBasis": "HTTPS/MCP schemas and event telemetry",
      "gap": "Notification thresholds, payload, modalities and delivery expectations are not a complete qualified specification.",
      "proposedExtension": "Publish an integrator contract sufficient to implement and test alerts.",
      "acceptanceEvidence": "Independent implementer builds the alert path from the specification without hidden assumptions.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-5-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.5.1",
      "pages": [
        21
      ],
      "verbalForce": "shall",
      "topic": "Design against passive acceptance and over-reliance",
      "paloBasis": "ctrl-human-review; explanation and AI-literacy packs",
      "gap": "Exact approval proves binding, not independent critical judgment.",
      "proposedExtension": "Require active review, counter-evidence access and explicit uncertainty; keep automation-bias risk visible.",
      "acceptanceEvidence": "Reviewer can reject an incorrect but confidently worded recommendation without workflow penalty.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-5-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.5.2",
      "pages": [
        21,
        22
      ],
      "verbalForce": "can; scenario recommendation uses should",
      "topic": "Automation-bias testing",
      "paloBasis": "Generic adversarial/user-evaluation framework",
      "gap": "No controlled evaluation of wrong-answer acceptance is available.",
      "proposedExtension": "Design counterbalanced trials with intentionally flawed outputs, workload variation and mitigation variants.",
      "acceptanceEvidence": "Report erroneous acceptance, corrective action and decision quality, with sample and task limitations.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-6-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.6.1",
      "pages": [
        22
      ],
      "verbalForce": "shall",
      "topic": "Interpretation of capability, scores and unreliability",
      "paloBasis": "System-card performance and limitations; source-based copilot",
      "gap": "Citation presence and model confidence are not calibrated correctness probabilities.",
      "proposedExtension": "Explain measurement meaning, calibration population, unavailable evidence and failure conditions.",
      "acceptanceEvidence": "Test whether reviewers distinguish source provenance, confidence, data quality and observed effect.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-6-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.6.2",
      "pages": [
        22
      ],
      "verbalForce": "should",
      "topic": "Training relevant to oversight tasks and learning feedback",
      "paloBasis": "AI-literacy pack; role-based competencies",
      "gap": "Training may omit whether human corrections enter future learning or agent memory.",
      "proposedExtension": "Document correction scope and prevent unreviewed feedback-to-training loops.",
      "acceptanceEvidence": "Reviewer correctly predicts whether an edit changes only the case or future behaviour.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-7-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.7.1",
      "pages": [
        22,
        23
      ],
      "verbalForce": "shall",
      "topic": "At least one intervention function, plus a stop procedure",
      "paloBasis": "Approval denial, capability revocation, incidents",
      "gap": "These controls do not prove every deployed system can reach an appropriate safe state.",
      "proposedExtension": "Declare supported intervention semantics, measured latency and abstention events.",
      "acceptanceEvidence": "Separate initiated, acknowledged, effected and verified states; require stop capability.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-7-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.7.2",
      "pages": [
        23
      ],
      "verbalForce": "shall for disregard",
      "topic": "Reject output before execution without re-execution",
      "paloBasis": "Exact-claim denial and one-time capability",
      "gap": "Workflow retries or alternative credentials can defeat a local rejection.",
      "proposedExtension": "Bind the rejected action and invalidate dependent retries; acknowledge the human event.",
      "acceptanceEvidence": "Rejected output never executes through any in-scope route.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-7-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.7.3",
      "pages": [
        23
      ],
      "verbalForce": "shall for override",
      "topic": "Block original action and integrate human alternative",
      "paloBasis": "New Action Claim can bind changed arguments",
      "gap": "A replacement flow is not yet a complete typed override record.",
      "proposedExtension": "Link original and replacement claims and revalidate the alternative under current policy.",
      "acceptanceEvidence": "Original path halts; changed action cannot inherit the old exact approval.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-7-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.7.4",
      "pages": [
        23
      ],
      "verbalForce": "shall for reverse",
      "topic": "Reversal including dependent processes and infeasible cases",
      "paloBasis": "Effect Contracts; compensation explicitly requires a new Action Claim",
      "gap": "Automatic rollback is deliberately absent; compensation does not undo every external harm.",
      "proposedExtension": "Specify reversibility boundaries, dependency propagation and safe-state fallback.",
      "acceptanceEvidence": "Undo or compensate a synthetic action; verify downstream effects; retain irreversibility as a finding.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-7-5",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.7.5",
      "pages": [
        23,
        24
      ],
      "verbalForce": "shall subject to scenario/design conditions",
      "topic": "Safe state and recovery qualification",
      "paloBasis": "Preview hold, revocation and cancellation mechanisms",
      "gap": "Revocation/worker acknowledgement is not a system-wide safe-state proof.",
      "proposedExtension": "Define active functions, independent trigger, transition budget and recovery authority for each scenario.",
      "acceptanceEvidence": "Test delayed/unreachable workers, harmful abrupt halt and forbidden automatic restart.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.1",
      "pages": [
        24,
        25
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Prevent action before required natural-person review",
      "paloBasis": "Approval binding and controlled-executor concepts",
      "gap": "Single-resolver approval is not the draft RBI review barrier.",
      "proposedExtension": "Separate optional RBI profile with reviewed legal applicability and two-person barrier.",
      "acceptanceEvidence": "Unreviewed identification cannot cause an in-scope downstream action or transmission.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-2-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.2.1",
      "pages": [
        25
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Authenticated review state machine",
      "paloBasis": "Approval statuses and actor identity",
      "gap": "Generic approval statuses do not establish two distinct completed reviews.",
      "proposedExtension": "Use review-required, review-complete and rejected with natural-person review records.",
      "acceptanceEvidence": "Duplicate identity or rejected result cannot complete the gate.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-2-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.2.2",
      "pages": [
        25
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Evidence required by each reviewer",
      "paloBasis": "System-card and artifact-reference patterns",
      "gap": "PALO has no qualified biometric review UI.",
      "proposedExtension": "Specify protected access to probe/reference material, quality indicators and context.",
      "acceptanceEvidence": "Each authorized reviewer can inspect the relevant evidence without disclosure beyond scope.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-2-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.2.3",
      "pages": [
        25
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Biometric inspection and low-quality alerts",
      "paloBasis": "Accessibility and explanation principles",
      "gap": "Image inspection and alert functionality are not implemented by generic PALO evidence forms.",
      "proposedExtension": "Keep this as a sector adapter acceptance profile.",
      "acceptanceEvidence": "Test usable visual comparison and quality alerts with representative operators.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-2-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.2.4",
      "pages": [
        25,
        26
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Explicit decisions, notes and timestamps",
      "paloBasis": "Approval rationale and event timestamps",
      "gap": "Passive acknowledgement must not count as substantive review.",
      "proposedExtension": "Record separate active decisions and disagreement handling.",
      "acceptanceEvidence": "No timeout, default choice or page visit completes a review.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-3",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.3",
      "pages": [
        26
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Distinct identities and sequential-review independence",
      "paloBasis": "Authentication/tenant binding; independent-remedy concept",
      "gap": "Two agents or two clicks by one person are not two natural persons.",
      "proposedExtension": "Keep reviewer decisions sealed until independent sequential submission.",
      "acceptanceEvidence": "Same identity, shared credentials or premature visibility fails the qualification.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-4",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.4",
      "pages": [
        26
      ],
      "verbalForce": "shall within RBI profile",
      "topic": "Review architecture, independence tests and configuration documentation",
      "paloBasis": "Governance-assurance evidence contract",
      "gap": "A schema-valid record is insufficient evidence of enforced independence.",
      "proposedExtension": "Attach architecture and negative integration tests for each review configuration.",
      "acceptanceEvidence": "Attempt duplicate review and downstream bypass through actual adapters.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-5-8-5",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "5.8.5",
      "pages": [
        26,
        27
      ],
      "verbalForce": "shall plus recommended competence detail",
      "topic": "Reviewer competence and training",
      "paloBasis": "AI-literacy effectiveness controls",
      "gap": "Generic attendance records do not establish biometric review competence.",
      "proposedExtension": "Use system-specific competence and training evidence in the separate RBI profile.",
      "acceptanceEvidence": "Representative review tasks demonstrate the declared competence.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-6-1",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "6.1",
      "pages": [
        27
      ],
      "verbalForce": "shall",
      "topic": "Oversight content in instructions for use",
      "paloBasis": "System cards and integration guides",
      "gap": "Provider/deployer requirements are distributed across artifacts.",
      "proposedExtension": "Generate a versioned deployer handover dossier from approved scenario records.",
      "acceptanceEvidence": "Completeness checks link every applicable instruction to evidence and responsible roles.",
      "priority": "P1",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-6-2",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "6.2",
      "pages": [
        27
      ],
      "verbalForce": "shall",
      "topic": "Technical documentation for verification and limitations",
      "paloBasis": "Evidence bundle and governance-assurance record",
      "gap": "No dedicated collection of timing, overload, fallback and intervention qualification evidence.",
      "proposedExtension": "Compose existing evidence records with the proposed oversight scenario profile.",
      "acceptanceEvidence": "A reviewer can reproduce results and trace failed criteria to open corrective actions.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    },
    {
      "id": "HO-ZA",
      "source": "prEN 18229-3:2026, July 2026 user-supplied enquiry draft",
      "clause": "ZA",
      "pages": [
        28
      ],
      "verbalForce": "informative",
      "topic": "Draft mapping to Article 14 and conditional future presumption",
      "paloBasis": "Source-status and legal-applicability controls",
      "gap": "An enquiry draft must not be labelled an adopted harmonised standard or certification.",
      "proposedExtension": "Track draft status, published edition and any applicable Official Journal reference separately.",
      "acceptanceEvidence": "No presumption-of-conformity claim is emitted from a draft crosswalk.",
      "priority": "P0",
      "status": "partial foundation; extension proposed"
    }
  ]
}
