<?xml version="1.0" encoding="utf-8"?>
<rbl:kb xmlns:rbl="http://rbl.io/schema/RBLang">

  <!-- Concepts -->
  <concept name="Control" type="string"/>
  <concept name="Deficiency" type="string"/>
  <concept name="ICFR Assessment" type="string"/>
  <concept name="Relied On Report" type="string"/>
  <concept name="Testing Policy" type="string"/>
  <concept name="Sample Size Row" type="string"/>
  <concept name="Severity Row" type="string"/>
  <concept name="Remediation Row" type="string"/>
  <concept name="Aggregation Row" type="string"/>
  <concept name="Risk" type="string"/>
  <concept name="Assertion" type="string"/>
  <concept name="Line Item" type="string"/>
  <concept name="Performer Role" type="string"/>
  <concept name="Framework" type="string"/>
  <concept name="Reporting Regime" type="string"/>
  <concept name="Control Scope" type="string"/>
  <concept name="Frequency" type="string"/>
  <concept name="Risk Level" type="string"/>
  <concept name="Control Type" type="string"/>
  <concept name="Control Nature" type="string"/>
  <concept name="Control Timing" type="string"/>
  <concept name="Control Attribute" type="string"/>
  <concept name="COSO Component" type="string"/>
  <concept name="Materiality Band" type="string"/>
  <concept name="Likelihood" type="string"/>
  <concept name="Sampling Method" type="string"/>
  <concept name="Exception Nature" type="string"/>
  <concept name="Deviation Class" type="string"/>
  <concept name="Sufficiency Test" type="string"/>
  <concept name="ITGC Conclusion" type="string"/>
  <concept name="Report Class" type="string"/>
  <concept name="Reliance Availability" type="string"/>
  <concept name="Further Procedure" type="string"/>
  <concept name="Deficiency Type" type="string"/>
  <concept name="Indicator" type="string"/>
  <concept name="Assessor Role" type="string"/>
  <concept name="Direction Of Exposure" type="string"/>
  <concept name="Evidence Source Class" type="string"/>
  <concept name="Evidence Form" type="string"/>
  <concept name="Precision Tier" type="string"/>
  <concept name="Design Assessment" type="string"/>
  <concept name="Operating Conclusion" type="string"/>
  <concept name="US Severity" type="string"/>
  <concept name="UK Declaration Outcome" type="string"/>
  <concept name="International Classification" type="string"/>
  <concept name="ICFR Conclusion" type="string"/>
  <concept name="Finding" type="string"/>
  <concept name="Reason" type="string"/>
  <concept name="Summary" type="string"/>
  <concept name="Open Question" type="string"/>
  <concept name="Disclosure Element" type="string"/>
  <concept name="Communication Requirement" type="string"/>
  <concept name="Instrument" type="string"/>
  <concept name="Judgement Owner" type="string"/>
  <concept name="Count" type="number"/>
  <concept name="Percent" type="number"/>
  <concept name="Rank" type="number"/>
  <concept name="Month Count" type="number"/>
  <concept name="Event Date" type="date"/>
  <concept name="Flag" type="truth"/>

  <!-- Relationships -->
  <rel name="has framework" subject="Control" object="Framework" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Which reporting framework applies to control %S - US ICFR or UK Material Controls?</secondFormObject>
  </rel>
  <rel name="has reporting regime" subject="Control" object="Reporting Regime" askable="none"/>
  <rel name="has control scope" subject="Control" object="Control Scope" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>What is the scope of control %S - Financial Reporting, Operational, Reporting, Compliance or Strategic?</secondFormObject>
  </rel>
  <rel name="addresses risk" subject="Control" object="Risk" askable="secondFormObject" allowUnknown="true" canAdd="all">
    <secondFormObject>Which risk does control %S address, as the bank records it?</secondFormObject>
  </rel>
  <rel name="relates to assertion" subject="Control" object="Assertion" askable="none" canAdd="all"/>
  <rel name="sits in coso component" subject="Control" object="COSO Component" askable="none"/>
  <rel name="is key control" subject="Control" object="Flag" askable="none"/>
  <rel name="is material control" subject="Control" object="Flag" askable="none"/>
  <rel name="has materiality band" subject="Control" object="Materiality Band" askable="none"/>
  <rel name="has period end" subject="Control" object="Event Date" askable="none"/>
  <rel name="has assessor role" subject="Control" object="Assessor Role" askable="none"/>
  <rel name="acquired in period" subject="Control" object="Flag" askable="none"/>
  <rel name="assessment feasible before due date" subject="Control" object="Flag" askable="none"/>
  <rel name="prior year exclusion already taken" subject="Control" object="Flag" askable="none"/>
  <rel name="has performer role" subject="Control" object="Performer Role" askable="secondFormObject" allowUnknown="true" canAdd="all">
    <secondFormObject>Which role performs control %S - the role, not a named person?</secondFormObject>
  </rel>
  <rel name="has frequency" subject="Control" object="Frequency" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>How often is control %S performed - Annual, Quarterly, Monthly, Weekly, Daily or Multiple Times Daily?</secondFormObject>
  </rel>
  <rel name="has timing" subject="Control" object="Control Timing" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S operate Before Transaction or After Transaction?</secondFormObject>
  </rel>
  <rel name="has procedure described" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the documentation for control %S describe the procedure the performer carries out?</secondFormObject>
  </rel>
  <rel name="produces evidence" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S produce evidence of its performance?</secondFormObject>
  </rel>
  <rel name="states precision threshold" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S state the precision or threshold at which it operates?</secondFormObject>
  </rel>
  <rel name="has control type" subject="Control" object="Control Type" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is control %S Manual, Automated or IT Dependent Manual?</secondFormObject>
  </rel>
  <rel name="has control nature" subject="Control" object="Control Nature" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is control %S Preventive or Detective?</secondFormObject>
  </rel>
  <rel name="has risk level" subject="Control" object="Risk Level" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>What is the risk associated with control %S - Low, Medium or High?</secondFormObject>
  </rel>
  <rel name="addresses the stated risk" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>As described, would control %S address the risk it is recorded against?</secondFormObject>
  </rel>
  <rel name="relies on application" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S rely on an application to perform any part of the control?</secondFormObject>
  </rel>
  <rel name="relies on information produced by the entity" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S rely on a report or data set produced inside the bank?</secondFormObject>
  </rel>
  <rel name="changed during the period" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did control %S change during the period under review?</secondFormObject>
  </rel>
  <rel name="is management review control" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is control %S a management review control - a review of information by a person exercising judgement?</secondFormObject>
  </rel>
  <rel name="has review threshold band" subject="Control" object="Materiality Band" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Relative to the materiality bands the bank uses, at which band is the investigation threshold for control %S set?</secondFormObject>
  </rel>
  <rel name="mrc addresses assertion level risk" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the review in control %S address the assessed risk at the assertion level?</secondFormObject>
  </rel>
  <rel name="mrc precision factors documented" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Are the precision factors for the review in control %S documented - the level of aggregation and the predictability of what is reviewed?</secondFormObject>
  </rel>
  <rel name="mrc investigation steps documented" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Are the steps to identify, investigate and resolve significant differences documented for control %S?</secondFormObject>
  </rel>
  <rel name="mrc performer authority attested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the reviewer in control %S have the authority to act on what the review finds?</secondFormObject>
  </rel>
  <rel name="mrc information source identified" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the information used in the review in control %S identified, including whether it is system generated?</secondFormObject>
  </rel>
  <rel name="mrc evidence of steps performed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the test evidence for control %S show the steps the reviewer performed to identify and investigate significant differences?</secondFormObject>
  </rel>
  <rel name="mrc evidence of conclusions reached" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the test evidence for control %S show the conclusions the reviewer reached, including any corrective action taken?</secondFormObject>
  </rel>
  <rel name="test evidenced only by sign off" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the only evidence of performance for control %S a signature or sign off?</secondFormObject>
  </rel>
  <rel name="is budget comparison review" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is control %S a comparison of actual results against budget or forecast?</secondFormObject>
  </rel>
  <rel name="account is complex or unpredictable" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the account or disclosure that control %S addresses complex, or less predictable period to period?</secondFormObject>
  </rel>
  <rel name="follow up of outliers documented" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the follow up of items the review identified as outliers documented for control %S?</secondFormObject>
  </rel>
  <rel name="test includes inquiry" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did the test of control %S include inquiry of the people who perform it?</secondFormObject>
  </rel>
  <rel name="test includes observation" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did the test of control %S include observing the control being performed?</secondFormObject>
  </rel>
  <rel name="test includes inspection" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did the test of control %S include inspection of documentation?</secondFormObject>
  </rel>
  <rel name="test includes reperformance" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did the test of control %S include re-performance of the control?</secondFormObject>
  </rel>
  <rel name="has population size" subject="Control" object="Count" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>How many times was control %S performed in the period - the population size?</secondFormObject>
  </rel>
  <rel name="population completeness established" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the completeness of the population established before the sample for control %S was drawn?</secondFormObject>
  </rel>
  <rel name="has sampling method" subject="Control" object="Sampling Method" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>How was the sample for control %S selected - Random, Systematic, Haphazard, Judgemental, Full Population or Not Applicable?</secondFormObject>
  </rel>
  <rel name="has sample size tested" subject="Control" object="Count" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>How many instances of control %S were tested?</secondFormObject>
  </rel>
  <rel name="has exception count" subject="Control" object="Count" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>How many exceptions were found in the sample for control %S?</secondFormObject>
  </rel>
  <rel name="has exception nature" subject="Control" object="Exception Nature" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>What is the nature of the exceptions found for control %S - Isolated, Systemic or Unknown?</secondFormObject>
  </rel>
  <rel name="root cause identified" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Has the root cause of the exceptions in control %S been established?</secondFormObject>
  </rel>
  <rel name="has deviation class" subject="Control" object="Deviation Class" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the deviation found in control %S a Control Failure or a Documentation Gap?</secondFormObject>
  </rel>
  <rel name="has untestable item count" subject="Control" object="Count" askable="none"/>
  <rel name="is combination of controls" subject="Control" object="Flag" askable="none"/>
  <rel name="has performer population count" subject="Control" object="Count" askable="none"/>
  <rel name="depends primarily on segregation of duties" subject="Control" object="Flag" askable="none"/>
  <rel name="evidence retained" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the evidence of performance for the instances of control %S tested retained?</secondFormObject>
  </rel>
  <rel name="evidence dated within period" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the retained evidence for control %S dated within the period under review?</secondFormObject>
  </rel>
  <rel name="evidence shows performer" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the retained evidence for control %S show who performed the control?</secondFormObject>
  </rel>
  <rel name="evidence shows what was done" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the retained evidence for control %S show what the performer actually did?</secondFormObject>
  </rel>
  <rel name="performer independent of preparer" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the person who performs control %S independent of the person who prepared what is being controlled?</secondFormObject>
  </rel>
  <rel name="reviewer competence attested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Has the competence of the person performing control %S been attested?</secondFormObject>
  </rel>
  <rel name="performer authority attested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the person who performs control %S have the authority to perform it as designed?</secondFormObject>
  </rel>
  <rel name="sampling rationale recorded" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the rationale for how the sample for control %S was selected recorded?</secondFormObject>
  </rel>
  <rel name="test served dual purpose" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did the test of control %S also serve a substantive purpose, testing whether the transactions themselves were correct?</secondFormObject>
  </rel>
  <rel name="dual purpose required size" subject="Control" object="Count" askable="none"/>
  <rel name="has evidence source class" subject="Control" object="Evidence Source Class" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the evidence for control %S obtained from a knowledgeable source independent of the bank, or from the bank's own records - Independent External or Entity Internal?</secondFormObject>
  </rel>
  <rel name="has evidence form" subject="Control" object="Evidence Form" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>In what form was the evidence for control %S held - Original, Copy Or Conversion, or Directly Obtained?</secondFormObject>
  </rel>
  <rel name="third party restriction attached" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Did any third party restriction, limitation or disclaimer attach to the evidence used for control %S?</secondFormObject>
  </rel>
  <rel name="external information supplied electronically" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was information the bank obtained from an external source supplied in electronic form for the test of control %S?</secondFormObject>
  </rel>
  <rel name="external information modification tested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was it tested whether the bank modified that externally sourced information, or were the controls over it tested instead?</secondFormObject>
  </rel>
  <rel name="prior year test approach repeated" subject="Control" object="Flag" askable="none"/>
  <rel name="superseded in period" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was control %S superseded during the period by a replacement control?</secondFormObject>
  </rel>
  <rel name="successor achieves same objectives" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does the control that replaced control %S achieve the same control objectives?</secondFormObject>
  </rel>
  <rel name="successor in place long enough to test" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Has the replacement for control %S been in place long enough for its design to be assessed and its operation tested?</secondFormObject>
  </rel>
  <rel name="superseded control important to control risk assessment" subject="Control" object="Flag" askable="none"/>
  <rel name="misstatement not detected by this control" subject="Control" object="Flag" askable="none"/>
  <rel name="internal audit reports read" subject="Control" object="Flag" askable="none"/>
  <rel name="has interim test date" subject="Control" object="Event Date" askable="none"/>
  <rel name="roll forward performed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was roll forward work performed for control %S between the interim test and the period end?</secondFormObject>
  </rel>
  <rel name="changes since interim" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were there significant changes in control %S or the controls around it after the interim test date?</secondFormObject>
  </rel>
  <rel name="interim exceptions noted" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were any exceptions noted when control %S was tested at interim?</secondFormObject>
  </rel>
  <rel name="substantially all evidence at interim" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was substantially all of the test evidence for control %S obtained at the interim date?</secondFormObject>
  </rel>
  <rel name="roll forward sample size" subject="Control" object="Count" askable="none"/>
  <rel name="roll forward procedure was inquiry only" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the roll forward work for control %S inquiry only, with no retest of any instance?</secondFormObject>
  </rel>
  <rel name="roll forward sufficiency inferred from substantive work" subject="Control" object="Flag" askable="none"/>
  <rel name="substantive inference position" subject="Control" object="Flag" askable="none"/>
  <rel name="interim change enquiry performed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was evidence obtained about significant changes to control %S after the interim test date?</secondFormObject>
  </rel>
  <rel name="addresses significant risk" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S address a risk the bank has determined to be a significant risk?</secondFormObject>
  </rel>
  <rel name="prior period evidence relied on" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is reliance being placed on testing of control %S carried out in an earlier assessment rather than in the current one?</secondFormObject>
  </rel>
  <rel name="has assessments since last test" subject="Control" object="Count" askable="none"/>
  <rel name="prior period relevance inquiry performed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was inquiry made to establish that the earlier testing of control %S remains relevant?</secondFormObject>
  </rel>
  <rel name="prior period relevance corroborated" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was that inquiry about control %S combined with observation or inspection?</secondFormObject>
  </rel>
  <rel name="has significant manual element" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does control %S contain a significant manual element?</secondFormObject>
  </rel>
  <rel name="personnel changes affecting application" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Have personnel changes significantly affected the way control %S is applied?</secondFormObject>
  </rel>
  <rel name="circumstances indicate control must change" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Have circumstances changed in a way that indicates control %S itself now needs to change?</secondFormObject>
  </rel>
  <rel name="control environment deficient" subject="Control" object="Flag" askable="none"/>
  <rel name="monitoring process deficient" subject="Control" object="Flag" askable="none"/>
  <rel name="deviation specific inquiries made" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were specific inquiries made to understand the deviations found in control %S and their potential consequences?</secondFormObject>
  </rel>
  <rel name="deviation basis for reliance determined" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Has it been determined whether the tests of control %S still provide an appropriate basis for reliance, or whether further work is needed?</secondFormObject>
  </rel>
  <rel name="has itgc conclusion" subject="Control" object="ITGC Conclusion" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>What is the conclusion on the general IT controls over the application control %S relies on - Effective, Deficient or Not Tested?</secondFormObject>
  </rel>
  <rel name="itgc currently tested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Are the general IT controls relevant to control %S being tested in the current period?</secondFormObject>
  </rel>
  <rel name="control unchanged since baseline" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Has control %S been verified unchanged since the baseline test was established?</secondFormObject>
  </rel>
  <rel name="has baseline age months" subject="Control" object="Month Count" askable="none"/>
  <rel name="is initial year assessment" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is this the first year control %S has been assessed?</secondFormObject>
  </rel>
  <rel name="depends on service organisation" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is any part of control %S performed by a service organisation outside the bank?</secondFormObject>
  </rel>
  <rel name="service auditor report available" subject="Control" object="Flag" askable="none"/>
  <rel name="service auditor report covers period" subject="Control" object="Flag" askable="none"/>
  <rel name="complementary user entity controls tested" subject="Control" object="Flag" askable="none"/>
  <rel name="entity level control relied on" subject="Control" object="Flag" askable="none"/>
  <rel name="entity level control precision tier" subject="Control" object="Precision Tier" askable="none"/>
  <rel name="depends on related data table" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Does automated control %S depend on a related file, table, rate or parameter held outside the program logic?</secondFormObject>
  </rel>
  <rel name="related data integrity addressed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the integrity of that related data for control %S tested as well as the program logic?</secondFormObject>
  </rel>
  <rel name="it dependent control it controls tested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were the IT controls over the completeness and accuracy of the data control %S uses tested as well as the control itself?</secondFormObject>
  </rel>
  <rel name="ipe completeness and accuracy tested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were the completeness and accuracy of the internally produced information used by control %S tested?</secondFormObject>
  </rel>
  <rel name="ipe query logic tested" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Was the logic of the query or extract that produced the information used by control %S tested?</secondFormObject>
  </rel>
  <rel name="ipe report parameters checked" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Were the parameters used to run the report relied on by control %S checked?</secondFormObject>
  </rel>
  <rel name="ipe sufficiently precise and detailed" subject="Control" object="Flag" askable="secondFormObject" allowUnknown="true">
    <secondFormObject>Is the internally produced information used by control %S sufficiently precise and detailed for the purpose the control puts it to?</secondFormObject>
  </rel>
  <rel name="has relied on report" subject="Control" object="Relied On Report" askable="none" canAdd="all" plural="true"/>
  <rel name="report has class" subject="Relied On Report" object="Report Class" askable="none"/>
  <rel name="report has itgc conclusion" subject="Relied On Report" object="ITGC Conclusion" askable="none"/>
  <rel name="report within tested itgc scope" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report parameters checked" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report is unmodified" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report change management evidenced" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report reconciled" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report completeness and accuracy tested" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report other procedures performed" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="report reliance available" subject="Relied On Report" object="Flag" askable="none"/>
  <rel name="has unreliable relied on report" subject="Control" object="Relied On Report" askable="none" plural="true"/>
  <rel name="has reliable relied on report" subject="Control" object="Relied On Report" askable="none" plural="true"/>
  <rel name="has deficiency" subject="Control" object="Deficiency" askable="none" canAdd="all" plural="true"/>
  <rel name="deficiency of control" subject="Deficiency" object="Control" askable="none" canAdd="all"/>
  <rel name="has deficiency type" subject="Deficiency" object="Deficiency Type" askable="none"/>
  <rel name="has likelihood" subject="Deficiency" object="Likelihood" askable="none"/>
  <rel name="has magnitude band" subject="Deficiency" object="Materiality Band" askable="none"/>
  <rel name="for assertion" subject="Deficiency" object="Assertion" askable="none" canAdd="all"/>
  <rel name="for line item" subject="Deficiency" object="Line Item" askable="none" canAdd="all"/>
  <rel name="for coso component" subject="Deficiency" object="COSO Component" askable="none"/>
  <rel name="compensating control exists" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="compensating control tested effective" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="compensating control precision adequate" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="compensating control same assertion" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has direction of exposure" subject="Deficiency" object="Direction Of Exposure" askable="none"/>
  <rel name="already communicated in writing" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has prior communication position" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has oversight position" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="restatement relates to previously issued period" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="prior period determination exists" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has indicator" subject="Deficiency" object="Indicator" askable="none" plural="true"/>
  <rel name="prudent official test applies" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="is pervasive" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="root cause established" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediation action stated" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediated before period end" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediated control retested" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediation first performed date" subject="Deficiency" object="Event Date" askable="none"/>
  <rel name="remediated control retest sample size" subject="Deficiency" object="Count" askable="none"/>
  <rel name="remediation months of operation" subject="Deficiency" object="Month Count" askable="none"/>
  <rel name="remediation retester independent" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="reported in prior year declaration" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="publicly disclosed during the year" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="is near miss" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="is significant control failing" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="is improvement area" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="recurred within the period" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="disclosure would reveal confidential information" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="audit committee oversight ineffective" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has international significance indicator" subject="Deficiency" object="Indicator" askable="none" plural="true"/>
  <rel name="material misstatement not detected by control" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="previously communicated and unremediated" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="merits attention of those charged with governance" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="merits management attention" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="assertion has deficiency" subject="Assertion" object="Deficiency" askable="none" plural="true"/>
  <rel name="line item has deficiency" subject="Line Item" object="Deficiency" askable="none" plural="true"/>
  <rel name="component has deficiency" subject="COSO Component" object="Deficiency" askable="none" plural="true"/>
  <rel name="assertion has deficiency band rank" subject="Assertion" object="Rank" askable="none" plural="true"/>
  <rel name="line item has deficiency band rank" subject="Line Item" object="Rank" askable="none" plural="true"/>
  <rel name="component has deficiency band rank" subject="COSO Component" object="Rank" askable="none" plural="true"/>
  <rel name="has group size candidate" subject="Deficiency" object="Count" askable="none" plural="true"/>
  <rel name="has aggregated band candidate" subject="Deficiency" object="Materiality Band" askable="none" plural="true"/>
  <rel name="assessment covers control" subject="ICFR Assessment" object="Control" askable="none" canAdd="all" plural="true"/>
  <rel name="assessment has period end" subject="ICFR Assessment" object="Event Date" askable="none"/>
  <rel name="assessment has framework" subject="ICFR Assessment" object="Framework" askable="none"/>
  <rel name="assessment has reporting regime" subject="ICFR Assessment" object="Reporting Regime" askable="none"/>
  <rel name="has icfr conclusion" subject="ICFR Assessment" object="ICFR Conclusion" askable="none"/>
  <rel name="has icfr disclosure requirement" subject="ICFR Assessment" object="Disclosure Element" askable="none" plural="true"/>
  <rel name="assessment has material weakness at period end" subject="ICFR Assessment" object="Flag" askable="none"/>
  <rel name="assessment has material weakness deficiency" subject="ICFR Assessment" object="Deficiency" askable="none" plural="true"/>
  <rel name="assessment has unevaluated deficiency" subject="ICFR Assessment" object="Deficiency" askable="none" plural="true"/>
  <rel name="assessment severe finding position" subject="ICFR Assessment" object="Flag" askable="none"/>
  <rel name="assessment evaluation driver" subject="ICFR Assessment" object="Flag" askable="none" plural="true"/>
  <rel name="has icfr finding" subject="ICFR Assessment" object="Finding" askable="none" plural="true"/>
  <rel name="has icfr summary" subject="ICFR Assessment" object="Summary" askable="none"/>
  <rel name="has icfr open question" subject="ICFR Assessment" object="Open Question" askable="none" plural="true"/>
  <rel name="has icfr applied instrument" subject="ICFR Assessment" object="Instrument" askable="none" plural="true"/>
  <rel name="has icfr judgement input" subject="ICFR Assessment" object="Judgement Owner" askable="none" plural="true"/>
  <rel name="has sample size row" subject="Testing Policy" object="Sample Size Row" askable="none" plural="true"/>
  <rel name="row frequency" subject="Sample Size Row" object="Frequency" askable="none"/>
  <rel name="row risk level" subject="Sample Size Row" object="Risk Level" askable="none"/>
  <rel name="row sample size" subject="Sample Size Row" object="Count" askable="none"/>
  <rel name="has severity row" subject="Testing Policy" object="Severity Row" askable="none" plural="true"/>
  <rel name="row magnitude band" subject="Severity Row" object="Materiality Band" askable="none"/>
  <rel name="row likelihood" subject="Severity Row" object="Likelihood" askable="none"/>
  <rel name="row us severity" subject="Severity Row" object="US Severity" askable="none"/>
  <rel name="row is ambiguous in sources" subject="Severity Row" object="Flag" askable="none"/>
  <rel name="has remediation row" subject="Testing Policy" object="Remediation Row" askable="none" plural="true"/>
  <rel name="remediation row frequency" subject="Remediation Row" object="Frequency" askable="none"/>
  <rel name="remediation row minimum months" subject="Remediation Row" object="Month Count" askable="none"/>
  <rel name="remediation row minimum occurrences" subject="Remediation Row" object="Count" askable="none"/>
  <rel name="has aggregation row" subject="Testing Policy" object="Aggregation Row" askable="none" plural="true"/>
  <rel name="aggregation row individual band" subject="Aggregation Row" object="Materiality Band" askable="none"/>
  <rel name="aggregation row minimum count" subject="Aggregation Row" object="Count" askable="none"/>
  <rel name="aggregation row aggregated band" subject="Aggregation Row" object="Materiality Band" askable="none"/>
  <rel name="band has rank" subject="Materiality Band" object="Rank" askable="none"/>
  <rel name="likelihood has rank" subject="Likelihood" object="Rank" askable="none"/>
  <rel name="severity has rank" subject="US Severity" object="Rank" askable="none"/>
  <rel name="frequency has annual occurrences" subject="Frequency" object="Count" askable="none"/>
  <rel name="automated control sample size" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="automated fallback sample floor" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="sample extension permitted" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="unknown exception nature treated as systemic" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="tolerable deviation rate percent" subject="Testing Policy" object="Percent" askable="none"/>
  <rel name="maximum roll forward gap months" subject="Testing Policy" object="Month Count" askable="none"/>
  <rel name="roll forward unavailable gap months" subject="Testing Policy" object="Month Count" askable="none"/>
  <rel name="minimum roll forward sample size" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="benchmarking permitted" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="maximum baseline age months" subject="Testing Policy" object="Month Count" askable="none"/>
  <rel name="maximum assessments since last test" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="prior period evidence permitted" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="international indicator effect conclusive" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="review precision margin ranks" subject="Testing Policy" object="Rank" askable="none"/>
  <rel name="compensating control effect permitted" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="compensating control must be tested" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="indicator effect conclusive" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="self assessment admissible" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="evidence floor requires more than inquiry" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="remediation retester independence required" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="aggregates by assertion" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="aggregates by line item" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="aggregates by coso component" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="required attribute count" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="required sufficiency test count" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="ambiguous severity cell resolution" subject="Testing Policy" object="US Severity" askable="none"/>
  <rel name="timing consistency check enabled" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="evidence practice legs required" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="sampling method has rank" subject="Sampling Method" object="Rank" askable="none"/>
  <rel name="minimum sampling method rank" subject="Testing Policy" object="Rank" askable="none"/>
  <rel name="change enquiry offered as practice" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="ipe depth offered as practice" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="service organisation evaluation enabled" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="search below material weakness required" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="expected deviation rate percent" subject="Testing Policy" object="Percent" askable="none"/>
  <rel name="tolerable deviation sample threshold" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="unpredictability reporting enabled" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="source class has rank" subject="Evidence Source Class" object="Rank" askable="none"/>
  <rel name="evidence form has rank" subject="Evidence Form" object="Rank" askable="none"/>
  <rel name="reliability hierarchy enabled" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="precision tier has rank" subject="Precision Tier" object="Rank" askable="none"/>
  <rel name="superseded control route enabled" subject="Testing Policy" object="Flag" askable="none"/>
  <rel name="acquired business exclusion years permitted" subject="Testing Policy" object="Count" askable="none"/>
  <rel name="applies testing policy" subject="Control" object="Testing Policy" askable="none"/>
  <rel name="deficiency applies testing policy" subject="Deficiency" object="Testing Policy" askable="none"/>
  <rel name="is a control under assessment" subject="Control" object="Flag" askable="none"/>
  <rel name="framework is bound" subject="Control" object="Flag" askable="none"/>
  <rel name="is in scope for the framework" subject="Control" object="Flag" askable="none"/>
  <rel name="is out of scope for the framework" subject="Control" object="Flag" askable="none"/>
  <rel name="has scope decline reason" subject="Control" object="Reason" askable="none" plural="true"/>
  <rel name="has input inconsistency" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has input conflict" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has design record inconsistency" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has attribute clearance" subject="Control" object="Control Attribute" askable="none" plural="true"/>
  <rel name="has missing attribute" subject="Control" object="Control Attribute" askable="none" plural="true"/>
  <rel name="has design finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has design statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has design candidate" subject="Control" object="Design Assessment" askable="none" plural="true"/>
  <rel name="has design assessment" subject="Control" object="Design Assessment" askable="none"/>
  <rel name="has confirmed control type" subject="Control" object="Control Type" askable="none"/>
  <rel name="has corrected control type" subject="Control" object="Control Type" askable="none"/>
  <rel name="has confirmed control nature" subject="Control" object="Control Nature" askable="none"/>
  <rel name="has corrected control nature" subject="Control" object="Control Nature" askable="none"/>
  <rel name="has review precision conclusion" subject="Control" object="Finding" askable="none"/>
  <rel name="has design reason" subject="Control" object="Reason" askable="none" plural="true"/>
  <rel name="has design summary" subject="Control" object="Summary" askable="none"/>
  <rel name="has effective control type" subject="Control" object="Control Type" askable="none"/>
  <rel name="uses frequency based extent" subject="Control" object="Flag" askable="none"/>
  <rel name="uses automated fallback extent" subject="Control" object="Flag" askable="none"/>
  <rel name="uses automated single instance extent" subject="Control" object="Flag" askable="none"/>
  <rel name="sampling approach does not apply" subject="Control" object="Flag" askable="none"/>
  <rel name="sample size comparison applies" subject="Control" object="Flag" askable="none"/>
  <rel name="has required sample size candidate" subject="Control" object="Count" askable="none" plural="true"/>
  <rel name="has required sample size" subject="Control" object="Count" askable="none"/>
  <rel name="extent of testing sufficient" subject="Control" object="Flag" askable="none"/>
  <rel name="has sample size basis" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has effective exception count" subject="Control" object="Count" askable="none"/>
  <rel name="has deviation rate percent" subject="Control" object="Percent" askable="none"/>
  <rel name="has effective exception nature" subject="Control" object="Exception Nature" askable="none"/>
  <rel name="exception position clear" subject="Control" object="Flag" askable="none"/>
  <rel name="has exception finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has sufficiency clearance" subject="Control" object="Sufficiency Test" askable="none" plural="true"/>
  <rel name="evidence is sufficient" subject="Control" object="Flag" askable="none"/>
  <rel name="has evidence sufficiency finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has roll forward candidate" subject="Control" object="Further Procedure" askable="none" plural="true"/>
  <rel name="has roll forward requirement" subject="Control" object="Further Procedure" askable="none"/>
  <rel name="roll forward sufficient" subject="Control" object="Flag" askable="none"/>
  <rel name="has roll forward finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has roll forward gap months" subject="Control" object="Month Count" askable="none"/>
  <rel name="has prior period reliance candidate" subject="Control" object="Reliance Availability" askable="none" plural="true"/>
  <rel name="has prior period reliance availability" subject="Control" object="Reliance Availability" askable="none"/>
  <rel name="has prior period reliance finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has deviation response finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has itgc reliance candidate" subject="Control" object="Reliance Availability" askable="none" plural="true"/>
  <rel name="has itgc reliance availability" subject="Control" object="Reliance Availability" askable="none"/>
  <rel name="has itgc reliance finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has ipe reliance candidate" subject="Control" object="Reliance Availability" askable="none" plural="true"/>
  <rel name="has ipe reliance availability" subject="Control" object="Reliance Availability" askable="none"/>
  <rel name="has ipe reliance finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has operating candidate" subject="Control" object="Operating Conclusion" askable="none" plural="true"/>
  <rel name="has operating effectiveness conclusion" subject="Control" object="Operating Conclusion" askable="none"/>
  <rel name="has suppressed candidate" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has operating reason" subject="Control" object="Reason" askable="none" plural="true"/>
  <rel name="has operating summary" subject="Control" object="Summary" askable="none"/>
  <rel name="benchmarking available" subject="Control" object="Flag" askable="none"/>
  <rel name="has benchmarking finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="baseline age within maximum" subject="Control" object="Flag" askable="none"/>
  <rel name="related data integrity cleared" subject="Control" object="Flag" askable="none"/>
  <rel name="has sampling method finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has dual purpose finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has reliability finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has superseded control finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has unpredictability statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has service organisation finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has entity level reliance effect" subject="Control" object="Reliance Availability" askable="none"/>
  <rel name="has entity level reliance finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has assessor role statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has search boundary statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has scope basis" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has acquired business outcome" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has acquired business disclosure" subject="Control" object="Disclosure Element" askable="none" plural="true"/>
  <rel name="has deficiency trigger" subject="Control" object="Deficiency Type" askable="none" plural="true"/>
  <rel name="has compensating control effect" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has compensating control finding" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has prudent official position" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has group deficiency count" subject="Deficiency" object="Count" askable="none"/>
  <rel name="has aggregated magnitude band" subject="Deficiency" object="Materiality Band" askable="none"/>
  <rel name="has aggregated band candidate rank" subject="Deficiency" object="Rank" askable="none" plural="true"/>
  <rel name="has aggregation finding" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has effective magnitude band" subject="Deficiency" object="Materiality Band" askable="none"/>
  <rel name="persists at period end" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediation period sufficient" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediation occurrences sufficient" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="remediation independence cleared" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has remediation months candidate" subject="Deficiency" object="Month Count" askable="none" plural="true"/>
  <rel name="has remediation months" subject="Deficiency" object="Month Count" askable="none"/>
  <rel name="has remediation finding" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="requires retest" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has retest condition" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has judgement input" subject="Deficiency" object="Judgement Owner" askable="none" plural="true"/>
  <rel name="has communication requirement" subject="Deficiency" object="Communication Requirement" askable="none" plural="true"/>
  <rel name="has communication recipient" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has communication deadline" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has communication form" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has communication basis" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has communication summary" subject="Deficiency" object="Summary" askable="none"/>
  <rel name="has restatement statement" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has control judgement input" subject="Control" object="Judgement Owner" askable="none" plural="true"/>
  <rel name="has judgement statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has deficiency judgement statement" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has open question" subject="Control" object="Open Question" askable="none" plural="true"/>
  <rel name="has deficiency open question" subject="Deficiency" object="Open Question" askable="none" plural="true"/>
  <rel name="has applied instrument" subject="Control" object="Instrument" askable="none" plural="true"/>
  <rel name="has deficiency applied instrument" subject="Deficiency" object="Instrument" askable="none" plural="true"/>
  <rel name="has us severity candidate" subject="Deficiency" object="US Severity" askable="none" plural="true"/>
  <rel name="us severity reduced by compensating control" subject="Deficiency" object="Flag" askable="none"/>
  <rel name="has us severity determination" subject="Deficiency" object="US Severity" askable="none"/>
  <rel name="has us severity finding" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has us severity reason" subject="Deficiency" object="Reason" askable="none" plural="true"/>
  <rel name="has us severity summary" subject="Deficiency" object="Summary" askable="none"/>
  <rel name="has us disclosure requirement" subject="Deficiency" object="Disclosure Element" askable="none" plural="true"/>
  <rel name="has applicable indicator" subject="Deficiency" object="Indicator" askable="none" plural="true"/>
  <rel name="has uk declaration candidate" subject="Control" object="UK Declaration Outcome" askable="none" plural="true"/>
  <rel name="has uk declaration determination" subject="Control" object="UK Declaration Outcome" askable="none"/>
  <rel name="has uk declaration finding" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has uk declaration reason" subject="Control" object="Reason" askable="none" plural="true"/>
  <rel name="has uk declaration summary" subject="Control" object="Summary" askable="none"/>
  <rel name="has uk disclosure element" subject="Control" object="Disclosure Element" askable="none" plural="true"/>
  <rel name="must be described in the declaration" subject="Control" object="Flag" askable="none"/>
  <rel name="has uk reportable statement" subject="Control" object="Disclosure Element" askable="none" plural="true"/>
  <rel name="has persisting deficiency" subject="Control" object="Deficiency" askable="none" plural="true"/>
  <rel name="has international classification candidate" subject="Deficiency" object="International Classification" askable="none" plural="true"/>
  <rel name="has international classification" subject="Deficiency" object="International Classification" askable="none"/>
  <rel name="has international classification finding" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has international classification reason" subject="Deficiency" object="Reason" askable="none" plural="true"/>
  <rel name="has determination" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has deficiency determination" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has framework statement" subject="Control" object="Finding" askable="none" plural="true"/>
  <rel name="has deficiency framework statement" subject="Deficiency" object="Finding" askable="none" plural="true"/>
  <rel name="has rolled up open question" subject="Control" object="Open Question" askable="none" plural="true"/>

  <!-- Instances -->
  <concinst name="US ICFR" type="Framework"/>
  <concinst name="UK Material Controls" type="Framework"/>
  <concinst name="SOX 404 Listed Issuer" type="Reporting Regime"/>
  <concinst name="FDICIA Part 363" type="Reporting Regime"/>
  <concinst name="UK Provision 29" type="Reporting Regime"/>
  <concinst name="Financial Reporting" type="Control Scope"/>
  <concinst name="Operational" type="Control Scope"/>
  <concinst name="Reporting" type="Control Scope"/>
  <concinst name="Compliance" type="Control Scope"/>
  <concinst name="Strategic" type="Control Scope"/>
  <concinst name="Annual" type="Frequency"/>
  <concinst name="Quarterly" type="Frequency"/>
  <concinst name="Monthly" type="Frequency"/>
  <concinst name="Weekly" type="Frequency"/>
  <concinst name="Daily" type="Frequency"/>
  <concinst name="Multiple Times Daily" type="Frequency"/>
  <concinst name="Low" type="Risk Level"/>
  <concinst name="Medium" type="Risk Level"/>
  <concinst name="High" type="Risk Level"/>
  <concinst name="Manual" type="Control Type"/>
  <concinst name="Automated" type="Control Type"/>
  <concinst name="IT Dependent Manual" type="Control Type"/>
  <concinst name="Preventive" type="Control Nature"/>
  <concinst name="Detective" type="Control Nature"/>
  <concinst name="Before Transaction" type="Control Timing"/>
  <concinst name="After Transaction" type="Control Timing"/>
  <concinst name="Performer Role" type="Control Attribute"/>
  <concinst name="Frequency" type="Control Attribute"/>
  <concinst name="Timing" type="Control Attribute"/>
  <concinst name="Procedure Described" type="Control Attribute"/>
  <concinst name="Evidence Produced" type="Control Attribute"/>
  <concinst name="Precision Or Threshold" type="Control Attribute"/>
  <concinst name="Risk Coverage" type="Control Attribute"/>
  <concinst name="Control Environment" type="COSO Component"/>
  <concinst name="Risk Assessment" type="COSO Component"/>
  <concinst name="Control Activities" type="COSO Component"/>
  <concinst name="Information and Communication" type="COSO Component"/>
  <concinst name="Monitoring Activities" type="COSO Component"/>
  <concinst name="Inconsequential" type="Materiality Band"/>
  <concinst name="More Than Inconsequential" type="Materiality Band"/>
  <concinst name="Material" type="Materiality Band"/>
  <concinst name="Remote" type="Likelihood"/>
  <concinst name="Reasonably Possible" type="Likelihood"/>
  <concinst name="Probable" type="Likelihood"/>
  <concinst name="Random" type="Sampling Method"/>
  <concinst name="Systematic" type="Sampling Method"/>
  <concinst name="Haphazard" type="Sampling Method"/>
  <concinst name="Judgemental" type="Sampling Method"/>
  <concinst name="Full Population" type="Sampling Method"/>
  <concinst name="Sampling Not Applicable" type="Sampling Method"/>
  <concinst name="Isolated" type="Exception Nature"/>
  <concinst name="Systemic" type="Exception Nature"/>
  <concinst name="Unknown Nature" type="Exception Nature"/>
  <concinst name="Control Failure" type="Deviation Class"/>
  <concinst name="Documentation Gap" type="Deviation Class"/>
  <concinst name="Evidence Retained" type="Sufficiency Test"/>
  <concinst name="Evidence Dated Within Period" type="Sufficiency Test"/>
  <concinst name="Evidence Shows Performer" type="Sufficiency Test"/>
  <concinst name="Evidence Shows What Was Done" type="Sufficiency Test"/>
  <concinst name="Performer Independent Of Preparer" type="Sufficiency Test"/>
  <concinst name="Procedures Above Inquiry Only" type="Sufficiency Test"/>
  <concinst name="Effective" type="ITGC Conclusion"/>
  <concinst name="Deficient" type="ITGC Conclusion"/>
  <concinst name="Not Tested" type="ITGC Conclusion"/>
  <concinst name="Canned Report" type="Report Class"/>
  <concinst name="Custom Report" type="Report Class"/>
  <concinst name="Ad Hoc Query" type="Report Class"/>
  <concinst name="Independent External" type="Evidence Source Class"/>
  <concinst name="Entity Internal" type="Evidence Source Class"/>
  <concinst name="Original" type="Evidence Form"/>
  <concinst name="Copy Or Conversion" type="Evidence Form"/>
  <concinst name="Directly Obtained" type="Evidence Form"/>
  <concinst name="Indirect Entity Level Control" type="Precision Tier"/>
  <concinst name="Monitoring Entity Level Control" type="Precision Tier"/>
  <concinst name="Assertion Precise Entity Level Control" type="Precision Tier"/>
  <concinst name="Management Or Second Line" type="Assessor Role"/>
  <concinst name="Internal Audit" type="Assessor Role"/>
  <concinst name="External Auditor" type="Assessor Role"/>
  <concinst name="Overstatement" type="Direction Of Exposure"/>
  <concinst name="Understatement" type="Direction Of Exposure"/>
  <concinst name="Overstatement And Understatement" type="Direction Of Exposure"/>
  <concinst name="Reliance Available" type="Reliance Availability"/>
  <concinst name="Reliance Not Available" type="Reliance Availability"/>
  <concinst name="Reliance Not Applicable" type="Reliance Availability"/>
  <concinst name="Inquiry" type="Further Procedure"/>
  <concinst name="Limited Retest" type="Further Procedure"/>
  <concinst name="Full Retest" type="Further Procedure"/>
  <concinst name="No Further Procedure Required" type="Further Procedure"/>
  <concinst name="Design Deficiency" type="Deficiency Type"/>
  <concinst name="Operating Deficiency" type="Deficiency Type"/>
  <concinst name="Fraud By Senior Management" type="Indicator"/>
  <concinst name="Restatement Correcting Material Misstatement" type="Indicator"/>
  <concinst name="Material Misstatement Found By Auditor Not By ICFR" type="Indicator"/>
  <concinst name="Ineffective Audit Committee Oversight" type="Indicator"/>
  <concinst name="Prudent Official Test" type="Indicator"/>
  <concinst name="Material Misstatement Not Prevented Or Detected" type="Indicator"/>
  <concinst name="Previously Communicated Deficiency Unremediated" type="Indicator"/>
  <concinst name="Ineffective Risk Assessment Process" type="Indicator"/>
  <concinst name="Ineffective Response To Identified Significant Risk" type="Indicator"/>
  <concinst name="Restatement Of Previously Issued Statements" type="Indicator"/>
  <concinst name="Management Inability To Oversee Financial Statements" type="Indicator"/>
  <concinst name="Evidence Of Ineffective Control Environment Aspect" type="Indicator"/>
  <concinst name="Significant Deficiency Reportable To Those Charged With Governance" type="International Classification"/>
  <concinst name="Deficiency Meriting Management Attention" type="International Classification"/>
  <concinst name="Deficiency Meriting Neither" type="International Classification"/>
  <concinst name="Classification Not Determinable" type="International Classification"/>
  <concinst name="Design Effective" type="Design Assessment"/>
  <concinst name="Design Deficient" type="Design Assessment"/>
  <concinst name="No Design Determination" type="Design Assessment"/>
  <concinst name="Operating Effective" type="Operating Conclusion"/>
  <concinst name="Exception Requiring Evaluation" type="Operating Conclusion"/>
  <concinst name="Not Operating Effectively" type="Operating Conclusion"/>
  <concinst name="Insufficient Evidence" type="Operating Conclusion"/>
  <concinst name="Testing Not Required" type="Operating Conclusion"/>
  <concinst name="No Operating Determination" type="Operating Conclusion"/>
  <concinst name="Deficiency" type="US Severity"/>
  <concinst name="Significant Deficiency" type="US Severity"/>
  <concinst name="Material Weakness" type="US Severity"/>
  <concinst name="Material Control Operated Effectively" type="UK Declaration Outcome"/>
  <concinst name="Material Control Did Not Operate Effectively" type="UK Declaration Outcome"/>
  <concinst name="Effectiveness Not Determinable" type="UK Declaration Outcome"/>
  <concinst name="No Declaration Consequence" type="UK Declaration Outcome"/>
  <concinst name="ICFR Effective" type="ICFR Conclusion"/>
  <concinst name="ICFR Not Effective" type="ICFR Conclusion"/>
  <concinst name="Management" type="Judgement Owner"/>
  <concinst name="The Board" type="Judgement Owner"/>
  <concinst name="The Audit Committee" type="Judgement Owner"/>
  <concinst name="The Control Owner" type="Judgement Owner"/>
  <concinst name="The Second Line Controls Function" type="Judgement Owner"/>
  <concinst name="PCAOB AS 2201 as cited AS No 5 text" type="Instrument"/>
  <concinst name="PCAOB AS 2315 Audit Sampling current text" type="Instrument"/>
  <concinst name="PCAOB AS 1105 Audit Evidence current text" type="Instrument"/>
  <concinst name="PCAOB AS 1305 current text" type="Instrument"/>
  <concinst name="PCAOB Staff Audit Practice Alert 11 of 24 October 2013" type="Instrument"/>
  <concinst name="SEC Release 33-8810 of 20 June 2007" type="Instrument"/>
  <concinst name="SEC Release 33-8829 effective 10 September 2007" type="Instrument"/>
  <concinst name="Regulation S-K Item 308 as amended" type="Instrument"/>
  <concinst name="FDIC 12 CFR Part 363 effective 1 January 2026" type="Instrument"/>
  <concinst name="UK Corporate Governance Code 2024" type="Instrument"/>
  <concinst name="FRC Corporate Governance Code Guidance 2024 updated 3 June 2026" type="Instrument"/>
  <concinst name="ISA UK 265 Updated September 2025" type="Instrument"/>
  <concinst name="ISA UK 330 Revised July 2017 Updated September 2025" type="Instrument"/>
  <concinst name="ISA UK 315 Revised July 2020 Updated September 2025" type="Instrument"/>
  <concinst name="COSO Internal Control Integrated Framework 2013 executive summary" type="Instrument"/>
  <concinst name="Description of how the board monitored and reviewed the framework" type="Disclosure Element"/>
  <concinst name="Declaration of effectiveness of material controls at the balance sheet date" type="Disclosure Element"/>
  <concinst name="Description of material controls that did not operate effectively" type="Disclosure Element"/>
  <concinst name="Action taken or proposed to improve those controls" type="Disclosure Element"/>
  <concinst name="Action taken to address previously reported issues" type="Disclosure Element"/>
  <concinst name="Explanation under comply or explain where no declaration can be given" type="Disclosure Element"/>
  <concinst name="Reporting against a publicised in year failure alongside a clean declaration" type="Disclosure Element"/>
  <concinst name="Nature of the weakness" type="Disclosure Element"/>
  <concinst name="Impact on financial reporting and on internal control" type="Disclosure Element"/>
  <concinst name="Remediation planned or undertaken" type="Disclosure Element"/>
  <concinst name="Whether the weakness is pervasive or not pervasive" type="Disclosure Element"/>
  <concinst name="Public disclosure in the annual internal control report" type="Disclosure Element"/>
  <concinst name="No public disclosure of this severity is required" type="Disclosure Element"/>
  <concinst name="Prior disclosures considered for continued appropriateness" type="Disclosure Element"/>
  <concinst name="Material change to internal control disclosed under Item 308 c" type="Disclosure Element"/>
  <concinst name="Acquired business identified and the exclusion stated" type="Disclosure Element"/>
  <concinst name="Significance of the acquired business indicated" type="Disclosure Element"/>
  <concinst name="Material control changes arising from the acquisition disclosed" type="Disclosure Element"/>
  <concinst name="Conclusion that internal control over financial reporting is not effective" type="Disclosure Element"/>
  <concinst name="In writing to management and the audit committee before the report is issued" type="Communication Requirement"/>
  <concinst name="In writing to the audit committee on a timely basis" type="Communication Requirement"/>
  <concinst name="In writing to management with the audit committee informed that it was made" type="Communication Requirement"/>
  <concinst name="To the board because audit committee oversight is ineffective" type="Communication Requirement"/>
  <concinst name="No further communication required because it was already communicated in writing" type="Communication Requirement"/>
  <concinst name="In writing to those charged with governance on a timely basis" type="Communication Requirement"/>
  <concinst name="To management at an appropriate level of responsibility on a timely basis" type="Communication Requirement"/>
  <concinst name="Reported to the board even though it has been remediated" type="Communication Requirement"/>
  <concinst name="No communication requirement identified on the facts supplied" type="Communication Requirement"/>
  <concinst name="Default Testing Policy" type="Testing Policy"/>
  <concinst name="Sample Annual Low" type="Sample Size Row"/>
  <concinst name="Sample Annual Medium" type="Sample Size Row"/>
  <concinst name="Sample Annual High" type="Sample Size Row"/>
  <concinst name="Sample Quarterly Low" type="Sample Size Row"/>
  <concinst name="Sample Quarterly Medium" type="Sample Size Row"/>
  <concinst name="Sample Quarterly High" type="Sample Size Row"/>
  <concinst name="Sample Monthly Low" type="Sample Size Row"/>
  <concinst name="Sample Monthly Medium" type="Sample Size Row"/>
  <concinst name="Sample Monthly High" type="Sample Size Row"/>
  <concinst name="Sample Weekly Low" type="Sample Size Row"/>
  <concinst name="Sample Weekly Medium" type="Sample Size Row"/>
  <concinst name="Sample Weekly High" type="Sample Size Row"/>
  <concinst name="Sample Daily Low" type="Sample Size Row"/>
  <concinst name="Sample Daily Medium" type="Sample Size Row"/>
  <concinst name="Sample Daily High" type="Sample Size Row"/>
  <concinst name="Sample Multiple Daily Low" type="Sample Size Row"/>
  <concinst name="Sample Multiple Daily Medium" type="Sample Size Row"/>
  <concinst name="Sample Multiple Daily High" type="Sample Size Row"/>
  <concinst name="Severity Inconsequential Remote" type="Severity Row"/>
  <concinst name="Severity Inconsequential Reasonably Possible" type="Severity Row"/>
  <concinst name="Severity Inconsequential Probable" type="Severity Row"/>
  <concinst name="Severity More Than Inconsequential Remote" type="Severity Row"/>
  <concinst name="Severity More Than Inconsequential Reasonably Possible" type="Severity Row"/>
  <concinst name="Severity More Than Inconsequential Probable" type="Severity Row"/>
  <concinst name="Severity Material Remote" type="Severity Row"/>
  <concinst name="Severity Material Reasonably Possible" type="Severity Row"/>
  <concinst name="Severity Material Probable" type="Severity Row"/>
  <concinst name="Remediation Annual" type="Remediation Row"/>
  <concinst name="Remediation Quarterly" type="Remediation Row"/>
  <concinst name="Remediation Monthly" type="Remediation Row"/>
  <concinst name="Remediation Weekly" type="Remediation Row"/>
  <concinst name="Remediation Daily" type="Remediation Row"/>
  <concinst name="Remediation Multiple Daily" type="Remediation Row"/>
  <concinst name="Aggregation Inconsequential To More Than" type="Aggregation Row"/>
  <concinst name="Aggregation More Than To Material" type="Aggregation Row"/>

  <!-- Facts -->
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Annual Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Annual Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Annual High"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Quarterly Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Quarterly Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Quarterly High"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Monthly Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Monthly Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Monthly High"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Weekly Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Weekly Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Weekly High"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Daily Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Daily Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Daily High"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Multiple Daily Low"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Multiple Daily Medium"/>
  <relinst type="has sample size row" subject="Default Testing Policy" object="Sample Multiple Daily High"/>
  <relinst type="row frequency" subject="Sample Annual Low" object="Annual"/>
  <relinst type="row risk level" subject="Sample Annual Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Annual Low" object="1"/>
  <relinst type="row frequency" subject="Sample Annual Medium" object="Annual"/>
  <relinst type="row risk level" subject="Sample Annual Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Annual Medium" object="1"/>
  <relinst type="row frequency" subject="Sample Annual High" object="Annual"/>
  <relinst type="row risk level" subject="Sample Annual High" object="High"/>
  <relinst type="row sample size" subject="Sample Annual High" object="1"/>
  <relinst type="row frequency" subject="Sample Quarterly Low" object="Quarterly"/>
  <relinst type="row risk level" subject="Sample Quarterly Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Quarterly Low" object="2"/>
  <relinst type="row frequency" subject="Sample Quarterly Medium" object="Quarterly"/>
  <relinst type="row risk level" subject="Sample Quarterly Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Quarterly Medium" object="2"/>
  <relinst type="row frequency" subject="Sample Quarterly High" object="Quarterly"/>
  <relinst type="row risk level" subject="Sample Quarterly High" object="High"/>
  <relinst type="row sample size" subject="Sample Quarterly High" object="2"/>
  <relinst type="row frequency" subject="Sample Monthly Low" object="Monthly"/>
  <relinst type="row risk level" subject="Sample Monthly Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Monthly Low" object="2"/>
  <relinst type="row frequency" subject="Sample Monthly Medium" object="Monthly"/>
  <relinst type="row risk level" subject="Sample Monthly Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Monthly Medium" object="3"/>
  <relinst type="row frequency" subject="Sample Monthly High" object="Monthly"/>
  <relinst type="row risk level" subject="Sample Monthly High" object="High"/>
  <relinst type="row sample size" subject="Sample Monthly High" object="5"/>
  <relinst type="row frequency" subject="Sample Weekly Low" object="Weekly"/>
  <relinst type="row risk level" subject="Sample Weekly Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Weekly Low" object="5"/>
  <relinst type="row frequency" subject="Sample Weekly Medium" object="Weekly"/>
  <relinst type="row risk level" subject="Sample Weekly Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Weekly Medium" object="10"/>
  <relinst type="row frequency" subject="Sample Weekly High" object="Weekly"/>
  <relinst type="row risk level" subject="Sample Weekly High" object="High"/>
  <relinst type="row sample size" subject="Sample Weekly High" object="15"/>
  <relinst type="row frequency" subject="Sample Daily Low" object="Daily"/>
  <relinst type="row risk level" subject="Sample Daily Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Daily Low" object="20"/>
  <relinst type="row frequency" subject="Sample Daily Medium" object="Daily"/>
  <relinst type="row risk level" subject="Sample Daily Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Daily Medium" object="25"/>
  <relinst type="row frequency" subject="Sample Daily High" object="Daily"/>
  <relinst type="row risk level" subject="Sample Daily High" object="High"/>
  <relinst type="row sample size" subject="Sample Daily High" object="30"/>
  <relinst type="row frequency" subject="Sample Multiple Daily Low" object="Multiple Times Daily"/>
  <relinst type="row risk level" subject="Sample Multiple Daily Low" object="Low"/>
  <relinst type="row sample size" subject="Sample Multiple Daily Low" object="25"/>
  <relinst type="row frequency" subject="Sample Multiple Daily Medium" object="Multiple Times Daily"/>
  <relinst type="row risk level" subject="Sample Multiple Daily Medium" object="Medium"/>
  <relinst type="row sample size" subject="Sample Multiple Daily Medium" object="40"/>
  <relinst type="row frequency" subject="Sample Multiple Daily High" object="Multiple Times Daily"/>
  <relinst type="row risk level" subject="Sample Multiple Daily High" object="High"/>
  <relinst type="row sample size" subject="Sample Multiple Daily High" object="60"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Inconsequential Remote"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Inconsequential Reasonably Possible"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Inconsequential Probable"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity More Than Inconsequential Remote"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity More Than Inconsequential Reasonably Possible"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity More Than Inconsequential Probable"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Material Remote"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Material Reasonably Possible"/>
  <relinst type="has severity row" subject="Default Testing Policy" object="Severity Material Probable"/>
  <relinst type="row magnitude band" subject="Severity Inconsequential Remote" object="Inconsequential"/>
  <relinst type="row likelihood" subject="Severity Inconsequential Remote" object="Remote"/>
  <relinst type="row us severity" subject="Severity Inconsequential Remote" object="Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity Inconsequential Remote" object="false"/>
  <relinst type="row magnitude band" subject="Severity Inconsequential Reasonably Possible" object="Inconsequential"/>
  <relinst type="row likelihood" subject="Severity Inconsequential Reasonably Possible" object="Reasonably Possible"/>
  <relinst type="row us severity" subject="Severity Inconsequential Reasonably Possible" object="Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity Inconsequential Reasonably Possible" object="false"/>
  <relinst type="row magnitude band" subject="Severity Inconsequential Probable" object="Inconsequential"/>
  <relinst type="row likelihood" subject="Severity Inconsequential Probable" object="Probable"/>
  <relinst type="row us severity" subject="Severity Inconsequential Probable" object="Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity Inconsequential Probable" object="false"/>
  <relinst type="row magnitude band" subject="Severity More Than Inconsequential Remote" object="More Than Inconsequential"/>
  <relinst type="row likelihood" subject="Severity More Than Inconsequential Remote" object="Remote"/>
  <relinst type="row us severity" subject="Severity More Than Inconsequential Remote" object="Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity More Than Inconsequential Remote" object="false"/>
  <relinst type="row magnitude band" subject="Severity More Than Inconsequential Reasonably Possible" object="More Than Inconsequential"/>
  <relinst type="row likelihood" subject="Severity More Than Inconsequential Reasonably Possible" object="Reasonably Possible"/>
  <relinst type="row us severity" subject="Severity More Than Inconsequential Reasonably Possible" object="Significant Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity More Than Inconsequential Reasonably Possible" object="false"/>
  <relinst type="row magnitude band" subject="Severity More Than Inconsequential Probable" object="More Than Inconsequential"/>
  <relinst type="row likelihood" subject="Severity More Than Inconsequential Probable" object="Probable"/>
  <relinst type="row us severity" subject="Severity More Than Inconsequential Probable" object="Significant Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity More Than Inconsequential Probable" object="true"/>
  <relinst type="row magnitude band" subject="Severity Material Remote" object="Material"/>
  <relinst type="row likelihood" subject="Severity Material Remote" object="Remote"/>
  <relinst type="row us severity" subject="Severity Material Remote" object="Significant Deficiency"/>
  <relinst type="row is ambiguous in sources" subject="Severity Material Remote" object="false"/>
  <relinst type="row magnitude band" subject="Severity Material Reasonably Possible" object="Material"/>
  <relinst type="row likelihood" subject="Severity Material Reasonably Possible" object="Reasonably Possible"/>
  <relinst type="row us severity" subject="Severity Material Reasonably Possible" object="Material Weakness"/>
  <relinst type="row is ambiguous in sources" subject="Severity Material Reasonably Possible" object="false"/>
  <relinst type="row magnitude band" subject="Severity Material Probable" object="Material"/>
  <relinst type="row likelihood" subject="Severity Material Probable" object="Probable"/>
  <relinst type="row us severity" subject="Severity Material Probable" object="Material Weakness"/>
  <relinst type="row is ambiguous in sources" subject="Severity Material Probable" object="false"/>
  <relinst type="ambiguous severity cell resolution" subject="Default Testing Policy" object="Significant Deficiency"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Annual"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Quarterly"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Monthly"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Weekly"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Daily"/>
  <relinst type="has remediation row" subject="Default Testing Policy" object="Remediation Multiple Daily"/>
  <relinst type="remediation row frequency" subject="Remediation Annual" object="Annual"/>
  <relinst type="remediation row minimum months" subject="Remediation Annual" object="12"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Annual" object="1"/>
  <relinst type="remediation row frequency" subject="Remediation Quarterly" object="Quarterly"/>
  <relinst type="remediation row minimum months" subject="Remediation Quarterly" object="6"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Quarterly" object="2"/>
  <relinst type="remediation row frequency" subject="Remediation Monthly" object="Monthly"/>
  <relinst type="remediation row minimum months" subject="Remediation Monthly" object="6"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Monthly" object="3"/>
  <relinst type="remediation row frequency" subject="Remediation Weekly" object="Weekly"/>
  <relinst type="remediation row minimum months" subject="Remediation Weekly" object="3"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Weekly" object="10"/>
  <relinst type="remediation row frequency" subject="Remediation Daily" object="Daily"/>
  <relinst type="remediation row minimum months" subject="Remediation Daily" object="3"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Daily" object="25"/>
  <relinst type="remediation row frequency" subject="Remediation Multiple Daily" object="Multiple Times Daily"/>
  <relinst type="remediation row minimum months" subject="Remediation Multiple Daily" object="3"/>
  <relinst type="remediation row minimum occurrences" subject="Remediation Multiple Daily" object="40"/>
  <relinst type="has aggregation row" subject="Default Testing Policy" object="Aggregation Inconsequential To More Than"/>
  <relinst type="has aggregation row" subject="Default Testing Policy" object="Aggregation More Than To Material"/>
  <relinst type="aggregation row individual band" subject="Aggregation Inconsequential To More Than" object="Inconsequential"/>
  <relinst type="aggregation row minimum count" subject="Aggregation Inconsequential To More Than" object="3"/>
  <relinst type="aggregation row aggregated band" subject="Aggregation Inconsequential To More Than" object="More Than Inconsequential"/>
  <relinst type="aggregation row individual band" subject="Aggregation More Than To Material" object="More Than Inconsequential"/>
  <relinst type="aggregation row minimum count" subject="Aggregation More Than To Material" object="3"/>
  <relinst type="aggregation row aggregated band" subject="Aggregation More Than To Material" object="Material"/>
  <relinst type="band has rank" subject="Inconsequential" object="1"/>
  <relinst type="band has rank" subject="More Than Inconsequential" object="2"/>
  <relinst type="band has rank" subject="Material" object="3"/>
  <relinst type="likelihood has rank" subject="Remote" object="1"/>
  <relinst type="likelihood has rank" subject="Reasonably Possible" object="2"/>
  <relinst type="likelihood has rank" subject="Probable" object="3"/>
  <relinst type="severity has rank" subject="Deficiency" object="1"/>
  <relinst type="severity has rank" subject="Significant Deficiency" object="2"/>
  <relinst type="severity has rank" subject="Material Weakness" object="3"/>
  <relinst type="sampling method has rank" subject="Random" object="4"/>
  <relinst type="sampling method has rank" subject="Systematic" object="3"/>
  <relinst type="sampling method has rank" subject="Haphazard" object="2"/>
  <relinst type="sampling method has rank" subject="Judgemental" object="1"/>
  <relinst type="sampling method has rank" subject="Full Population" object="5"/>
  <relinst type="sampling method has rank" subject="Sampling Not Applicable" object="5"/>
  <relinst type="source class has rank" subject="Independent External" object="2"/>
  <relinst type="source class has rank" subject="Entity Internal" object="1"/>
  <relinst type="evidence form has rank" subject="Directly Obtained" object="3"/>
  <relinst type="evidence form has rank" subject="Original" object="2"/>
  <relinst type="evidence form has rank" subject="Copy Or Conversion" object="1"/>
  <relinst type="precision tier has rank" subject="Indirect Entity Level Control" object="1"/>
  <relinst type="precision tier has rank" subject="Monitoring Entity Level Control" object="2"/>
  <relinst type="precision tier has rank" subject="Assertion Precise Entity Level Control" object="3"/>
  <relinst type="frequency has annual occurrences" subject="Annual" object="1"/>
  <relinst type="frequency has annual occurrences" subject="Quarterly" object="4"/>
  <relinst type="frequency has annual occurrences" subject="Monthly" object="12"/>
  <relinst type="frequency has annual occurrences" subject="Weekly" object="52"/>
  <relinst type="frequency has annual occurrences" subject="Daily" object="250"/>
  <relinst type="frequency has annual occurrences" subject="Multiple Times Daily" object="500"/>
  <relinst type="automated control sample size" subject="Default Testing Policy" object="1"/>
  <relinst type="automated fallback sample floor" subject="Default Testing Policy" object="25"/>
  <relinst type="sample extension permitted" subject="Default Testing Policy" object="false"/>
  <relinst type="unknown exception nature treated as systemic" subject="Default Testing Policy" object="true"/>
  <relinst type="tolerable deviation rate percent" subject="Default Testing Policy" object="5"/>
  <relinst type="maximum roll forward gap months" subject="Default Testing Policy" object="3"/>
  <relinst type="roll forward unavailable gap months" subject="Default Testing Policy" object="6"/>
  <relinst type="minimum roll forward sample size" subject="Default Testing Policy" object="1"/>
  <relinst type="benchmarking permitted" subject="Default Testing Policy" object="true"/>
  <relinst type="maximum baseline age months" subject="Default Testing Policy" object="36"/>
  <relinst type="prior period evidence permitted" subject="Default Testing Policy" object="true"/>
  <relinst type="maximum assessments since last test" subject="Default Testing Policy" object="3"/>
  <relinst type="review precision margin ranks" subject="Default Testing Policy" object="1"/>
  <relinst type="compensating control effect permitted" subject="Default Testing Policy" object="true"/>
  <relinst type="compensating control must be tested" subject="Default Testing Policy" object="true"/>
  <relinst type="indicator effect conclusive" subject="Default Testing Policy" object="true"/>
  <relinst type="international indicator effect conclusive" subject="Default Testing Policy" object="false"/>
  <relinst type="self assessment admissible" subject="Default Testing Policy" object="false"/>
  <relinst type="evidence floor requires more than inquiry" subject="Default Testing Policy" object="true"/>
  <relinst type="remediation retester independence required" subject="Default Testing Policy" object="true"/>
  <relinst type="aggregates by assertion" subject="Default Testing Policy" object="true"/>
  <relinst type="aggregates by line item" subject="Default Testing Policy" object="true"/>
  <relinst type="aggregates by coso component" subject="Default Testing Policy" object="true"/>
  <relinst type="timing consistency check enabled" subject="Default Testing Policy" object="true"/>
  <relinst type="evidence practice legs required" subject="Default Testing Policy" object="true"/>
  <relinst type="minimum sampling method rank" subject="Default Testing Policy" object="1"/>
  <relinst type="change enquiry offered as practice" subject="Default Testing Policy" object="true"/>
  <relinst type="ipe depth offered as practice" subject="Default Testing Policy" object="true"/>
  <relinst type="service organisation evaluation enabled" subject="Default Testing Policy" object="true"/>
  <relinst type="search below material weakness required" subject="Default Testing Policy" object="false"/>
  <relinst type="tolerable deviation sample threshold" subject="Default Testing Policy" object="25"/>
  <relinst type="expected deviation rate percent" subject="Default Testing Policy" object="0"/>
  <relinst type="unpredictability reporting enabled" subject="Default Testing Policy" object="true"/>
  <relinst type="reliability hierarchy enabled" subject="Default Testing Policy" object="true"/>
  <relinst type="superseded control route enabled" subject="Default Testing Policy" object="true"/>
  <relinst type="acquired business exclusion years permitted" subject="Default Testing Policy" object="1"/>
  <relinst type="required attribute count" subject="Default Testing Policy" object="6"/>
  <relinst type="required sufficiency test count" subject="Default Testing Policy" object="6"/>

  <!-- Rules -->
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control with a framework is under assessment (method gate - no instrument)"
           alt="A framework has been supplied for this control, so it is a control under assessment">
    <condition rel="has framework" subject="%S" object="%F"/>
  </relinst>
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control with a period end is under assessment (method gate - no instrument)"
           alt="A period end has been supplied for this control, so it is a control under assessment">
    <condition rel="has period end" subject="%S" object="%PE"/>
  </relinst>
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control with a reporting regime is under assessment (method gate - no instrument)"
           alt="A reporting regime has been supplied for this control, so it is a control under assessment">
    <condition rel="has reporting regime" subject="%S" object="%RR"/>
  </relinst>
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control with a materiality band is under assessment (method gate - no instrument)"
           alt="A materiality band has been supplied for this control, so it is a control under assessment">
    <condition rel="has materiality band" subject="%S" object="%MB"/>
  </relinst>
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control with a deficiency record is under assessment (method gate - no instrument)"
           alt="A deficiency record has been supplied against this control, so it is a control under assessment">
    <condition rel="has deficiency" subject="%S" object="%D"/>
  </relinst>
  <relinst type="is a control under assessment" object="true" cf="100"
           name="[CORE] A1 anchor - a control mapped to an assertion is under assessment (method gate - no instrument)"
           alt="The control is mapped to a financial statement assertion, so it is a control under assessment">
    <condition rel="relates to assertion" subject="%S" object="%A"/>
  </relinst>
  <relinst type="framework is bound" object="true" cf="100"
           name="[CORE] A1 - the framework overlay has been supplied (COSO Internal Control FAQs 2013, external criteria govern classification)"
           alt="The framework overlay {{%F}} has been supplied, so the determination can proceed on that framework's criteria">
    <condition rel="has framework" subject="%S" object="%F"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] A1 X2 - no framework supplied so no determination is available (COSO Internal Control FAQs 2013, external criteria govern classification)"
           alt="No framework overlay has been supplied, so no determination is available on any path">
    <condition rel="is a control under assessment" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has framework',*) is equal to 0" weight="1"
               alt="No framework overlay has been supplied for this control"/>
    <condition expression="'Which reporting framework applies - US ICFR or UK Material Controls. No determination is available on either path until the framework is supplied, because each framework supplies its own criteria for classifying a deficiency.'" value="%O"/>
  </relinst>
  <relinst type="applies testing policy" object="Default Testing Policy" cf="100"
           name="[CORE] I1 - a control under assessment applies the default testing policy (method gate - no instrument)"
           alt="This control applies the default calibration policy shipped with the accelerator">
    <condition rel="is a control under assessment" subject="%S" object="true"/>
  </relinst>
  <relinst type="deficiency applies testing policy" object="Default Testing Policy" cf="100"
           name="[CORE] I1 - a deficiency applies the testing policy of its control (method gate - no instrument)"
           alt="This deficiency applies the same calibration policy as the control it belongs to">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="is a control under assessment" subject="%C" object="true" weight="1"/>
  </relinst>
  <relinst type="has input inconsistency" cf="100"
           name="[CORE] B8 - automated control with no application relied on is an inconsistent record (AS 2201 paras B28, 39 to 41)"
           alt="The control is recorded as automated yet relies on no application, which the standard's own taxonomy cannot describe">
    <condition rel="has control type" subject="%S" object="Automated"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
    <condition expression="'Inconsistent record: the control is recorded as Automated but is recorded as relying on no application. Benchmarking is available to an entirely automated application control precisely because it is not subject to breakdown through human failure (AS 2201 para B28), and an IT dependent manual control is a distinct type with distinct testing (paras 39 to 41). No determination is reached until the record is corrected.'" value="%O"/>
  </relinst>
  <relinst type="has input inconsistency" cf="100"
           name="[CORE] B8 - automated control recorded with a human performer and no application (AS 2201 paras B28, 39 to 41)"
           alt="The control is recorded as automated with a performing role {{%PR}} and no application, which cannot be true of one control">
    <condition rel="has control type" subject="%S" object="Automated"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
    <condition rel="has performer role" subject="%S" object="%PR" weight="1"/>
    <condition expression="'Inconsistent record: the control is recorded as Automated and as performed by the role ' + %PR + ' with no application relied on. Under the standard s own taxonomy an entirely automated control is not performed by a person and an IT dependent manual control relies on an application (AS 2201 paras B28, 39 to 41).'" value="%O"/>
  </relinst>
  <relinst type="has design record inconsistency" cf="100"
           name="[CORE] B8 B9 - automated control with no application relied on is an inconsistent design record (AS 2201 paras B28, 39 to 41)"
           alt="The control is recorded as automated yet relies on no application, which the standard's own taxonomy cannot describe">
    <condition rel="has control type" subject="%S" object="Automated"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
    <condition expression="'Inconsistent record: the control is recorded as Automated but is recorded as relying on no application. Benchmarking is available to an entirely automated application control precisely because it is not subject to breakdown through human failure (AS 2201 para B28), and an IT dependent manual control is a distinct type with distinct testing (paras 39 to 41). No determination is reached until the record is corrected.'" value="%O"/>
  </relinst>
  <relinst type="has design record inconsistency" cf="100"
           name="[CORE] B8 B9 - automated control recorded with a human performer and no application is an inconsistent design record (AS 2201 paras B28, 39 to 41)"
           alt="The control is recorded as automated with a performing role {{%PR2}} and no application, which cannot be true of one control">
    <condition rel="has control type" subject="%S" object="Automated"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
    <condition rel="has performer role" subject="%S" object="%PR2" weight="1"/>
    <condition expression="'Inconsistent record: the control is recorded as Automated and as performed by the role ' + %PR2 + ' with no application relied on. Under the standard s own taxonomy an entirely automated control is not performed by a person and an IT dependent manual control relies on an application (AS 2201 paras B28, 39 to 41).'" value="%O"/>
  </relinst>
  <relinst type="has input inconsistency" cf="100"
           name="[CORE] C18 R5 - interim test date after the period end is invalid input (AS 2201 paras 55 to 56, the remaining period)"
           alt="The interim test date falls after the period end, so there is no remaining period for the standard to describe">
    <condition rel="has interim test date" subject="%S" object="%IT"/>
    <condition rel="has period end" subject="%S" object="%PE" weight="1"/>
    <condition expression="isAfterDate(%IT,%PE) is equal to true" weight="1"
               alt="The interim test date {{%IT}} falls after the period end {{%PE}}"/>
    <condition expression="'Inconsistent record: the interim test date falls after the period end. The roll forward paragraphs speak of the evidence needed for the remaining period AFTER an interim date (AS 2201 paras 55 to 56), so a date later than the period end describes nothing the standards contemplate. No determination is reached until the dates are corrected.'" value="%O"/>
  </relinst>
  <relinst type="has input inconsistency" cf="100"
           name="[CORE] C10a R5 - more deviations than items tested is invalid input (AS 2315 paras 40 and 41)"
           alt="More deviations are recorded than items tested, so no deviation rate can be estimated from the sample">
    <condition rel="has sample size tested" subject="%S" object="%SS"/>
    <condition rel="has exception count" subject="%S" object="%EC" weight="1"/>
    <condition expression="%EC is greater than %SS" weight="1"
               alt="The exception count {{%EC}} exceeds the sample size tested {{%SS}}"/>
    <condition expression="'Inconsistent record: more deviations are recorded than items tested. The deviation rate observed in the sample is the best estimate of the rate in the population (AS 2315 para 41), and a deviation is a selected item to which the control was not applied as planned (para 40) - so the count cannot exceed the number of items selected. No determination is reached on this control until the sample size and the exception count are reconciled.'" value="%O"/>
  </relinst>
  <relinst type="has input inconsistency" cf="100"
           name="[CORE] C10a R5 - a sample larger than its population is invalid input (AS 2315 paras 17 and 41)"
           alt="The sample tested is larger than the population it was drawn from, so it is not a sample of that population">
    <condition rel="has sample size tested" subject="%S" object="%SS2"/>
    <condition rel="has population size" subject="%S" object="%PS2" weight="1"/>
    <condition expression="%SS2 is greater than %PS2" weight="1"
               alt="The sample size tested {{%SS2}} exceeds the population size {{%PS2}}"/>
    <condition expression="'Inconsistent record: the sample tested is larger than the population it was drawn from. A sample is a selection from the population about which a conclusion is to be drawn (AS 2315 para 17), and the rate observed in it estimates the rate in that population (para 41); neither holds where the selection exceeds the population. No determination is reached until the population and sample figures are reconciled.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="Management" cf="100"
           name="[CORE] G5 - the risk associated with the control is a management judgement taken as an input (AS 2201 para 46)"
           alt="The risk associated with the control is {{%RL}}, a judgement supplied to the graph rather than derived by it">
    <condition rel="has risk level" subject="%S" object="%RL"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] G5 - statement of the risk judgement relied on and its owner (AS 2201 para 46)"
           alt="States that the risk level {{%RL}} was supplied as a judgement and names the role that should own it">
    <condition rel="has risk level" subject="%S" object="%RL"/>
    <condition expression="'Judgement taken as an input: the risk associated with the control is ' + %RL + '. The evidence needed increases as the risk associated with the control increases (AS 2201 para 46), but no source converts a control description into a risk level, so the judgement is supplied and should be owned by management or the second line controls function.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Control Owner" cf="100"
           name="[CORE] G5 - the nature of an exception is a judgement taken as an input (AS 2315 para 42)"
           alt="The nature of the exceptions found is {{%EN}}, a judgement supplied to the graph rather than derived by it">
    <condition rel="has exception nature" subject="%S" object="%EN"/>
  </relinst>
  <relinst type="has applied instrument" object="COSO Internal Control Integrated Framework 2013 executive summary" cf="100"
           name="[CORE] A8 G8 - COSO 2013 supplies the component vocabulary applied (COSO executive summary, five components)"
           alt="The control is grouped under the COSO component {{%CC}}, so the framework edition that supplies that vocabulary is named">
    <condition rel="sits in coso component" subject="%S" object="%CC"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] A9 G8 - the severity vocabulary comes from the regulator not the control framework (COSO Internal Control FAQs 2013)"
           alt="States that severity is classified with the external regulator's criteria rather than the control framework's own, which is why the determination vocabulary differs by path">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has framework" subject="%S" object="%AF9"/>
    <condition expression="'Why the vocabulary depends on the path. The control framework the components come from does not classify the severity of a deficiency where an external authority has already done so: where a regulator or standard setter has established its own criteria for defining, evaluating and reporting deficiencies, management should use only those external criteria in place of the framework s own classifications, COSO Internal Control FAQs. The framework s own severity term is therefore not used as a determination anywhere in this method. The framework applied here is ' + %AF9 + ', and the determination vocabulary on this result is that authority s vocabulary and no other.'" value="%O"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] A13 - likelihood is taken as a band and no numeric probability is asked for or emitted (AS 2201 para 65 Note 1)"
           alt="States that the likelihood judgement is made on a three point band scale and that no percentage is required or produced">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'How likelihood is expressed. The evaluation of whether a possibility is reasonable can be made without quantifying the probability as a specific percentage or range, AS 2201 paragraph 65 Note 1. This method therefore takes the likelihood judgement only on its band scale - remote, reasonably possible, probable - and never asks for a percentage, never infers one, and never converts a band into a number in any output. A band is the answer, not a rounding of one.'" value="%O"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] A11 G14 - statement of the COSO component the control sits in (COSO executive summary, five components)"
           alt="States the COSO component {{%CC}} the control was evaluated in, which the bank supplies and the graph never derives">
    <condition rel="sits in coso component" subject="%S" object="%CC"/>
    <condition expression="'The control sits in the COSO component ' + %CC + '. The component is supplied by the bank and is never derived here. It matters because severity judgements may differ by objective category and because deficiencies are aggregated across components and not only within one.'" value="%O"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[US] A3 - a financial reporting control is within ICFR scope (17 CFR 229.308 a 2 and 17 CFR 240.13a-15 f)"
           alt="The control is over financial reporting, which is the scope of a US internal control determination">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has control scope" subject="%S" object="Financial Reporting" weight="1"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[US] A3 - statement of the ICFR scope basis for a financial reporting control (17 CFR 229.308 a 2 and 17 CFR 240.13a-15 f)"
           alt="States the basis on which a financial reporting control is inside the scope of a US determination">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has control scope" subject="%S" object="Financial Reporting" weight="1"/>
    <condition expression="'Scope applied: internal control over financial reporting. Management reports on the effectiveness of internal control over financial reporting as defined at 17 CFR 240.13a-15 f, and Regulation S-K Item 308 a 2 asks for that assessment and no wider one.'" value="%O"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[US] E17 - a regulatory reporting control is within Part 363 financial reporting scope (12 CFR 363.1 c and App A Guideline 4A)"
           alt="On a Part 363 determination, financial reporting includes the statements prepared for regulatory reporting purposes, so this control is in scope">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="FDICIA Part 363" weight="1"/>
    <condition rel="has control scope" subject="%S" object="Reporting" weight="1"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[US] E17 - statement of the wider Part 363 financial reporting scope (12 CFR 363.1 c and App A Guideline 4A)"
           alt="States that a Part 363 determination treats regulatory reporting as part of financial reporting, which a listed issuer determination would not">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="FDICIA Part 363" weight="1"/>
    <condition rel="has control scope" subject="%S" object="Reporting" weight="1"/>
    <condition expression="'Scope applied: the wider Part 363 meaning of financial reporting. For Part 363 purposes financial reporting includes at a minimum both the financial statements prepared in accordance with generally accepted accounting principles and the financial statements prepared for regulatory reporting purposes, with recognition and measurement conforming to those principles and to section 37 of the FDI Act, 12 CFR 363.1 c. Appendix A Guideline 4A identifies the regulatory report schedules equivalent to basic financial statements. A control over a regulatory return is therefore in scope here though it would be outside the scope of a listed issuer determination.'" value="%O"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[US] A6a - statement that the Part 363 regime also covers the GAAP basis statements (12 CFR 363.1 c and 363.2 b 3 iii)"
           alt="States that a Part 363 determination covers the GAAP basis financial statements as well, with the Part 363 citation rather than the Item 308 one">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="FDICIA Part 363" weight="1"/>
    <condition rel="has control scope" subject="%S" object="Financial Reporting" weight="1"/>
    <condition expression="'Reporting regime applied: 12 CFR Part 363. The determination rests on the Part 363 instruments rather than on Regulation S-K. Financial reporting for Part 363 purposes includes the financial statements prepared under generally accepted accounting principles, 12 CFR 363.1 c, and the preclusion on an effective conclusion where a material weakness exists at the reporting date is carried at 12 CFR 363.2 b 3 iii in terms identical to Item 308 a 3. Whether this institution is caught by Part 363 is not decided here.'" value="%O"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[US] A6a - statement of the listed issuer regime basis (17 CFR 229.308 and 15 USC 7262 a)"
           alt="States that a listed issuer determination rests on the SEC instruments">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="SOX 404 Listed Issuer" weight="1"/>
    <condition expression="'Reporting regime applied: listed issuer reporting under section 404 a of the Sarbanes Oxley Act, 15 USC 7262 a, with the report content set by Regulation S-K Item 308. Whether this registrant is an accelerated filer, and so whether an auditor attestation is also required, is not decided here.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] A6a A6b - the reporting regime has not been supplied so the scope citation cannot be fixed (17 CFR 229.308 and 12 CFR 363.1 c)"
           alt="No reporting regime has been supplied, and the two US regimes have different scope boundaries, so the question is asked rather than assumed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition expression="countRelationshipInstances(%S,'has reporting regime',*) is equal to 0" weight="1"
               alt="No reporting regime has been supplied for this control"/>
    <condition expression="'Which US reporting regime applies - listed issuer reporting under section 404, or 12 CFR Part 363. The two have different scope boundaries: Part 363 treats the regulatory reporting statements as part of financial reporting, 12 CFR 363.1 c, and a listed issuer determination does not. Whether an institution is caught by Part 363 is a scoping question this graph does not decide.'" value="%O"/>
  </relinst>
  <relinst type="is out of scope for the framework" object="true" cf="100"
           name="[US] A3 - an operational control is outside ICFR scope (17 CFR 240.13a-15 f and 17 CFR 229.308 a 2)"
           alt="The control is an operational control, which is outside the internal control over financial reporting a US determination covers">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has control scope" subject="%S" object="Operational" weight="1"/>
  </relinst>
  <relinst type="is out of scope for the framework" object="true" cf="100"
           name="[US] A3 - a compliance control is outside ICFR scope (17 CFR 240.13a-15 f and 17 CFR 229.308 a 2)"
           alt="The control is a compliance control, which is outside the internal control over financial reporting a US determination covers">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has control scope" subject="%S" object="Compliance" weight="1"/>
  </relinst>
  <relinst type="is out of scope for the framework" object="true" cf="100"
           name="[US] A3 - a strategic control is outside ICFR scope (17 CFR 240.13a-15 f and 17 CFR 229.308 a 2)"
           alt="The control is a strategic control, which is outside the internal control over financial reporting a US determination covers">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has control scope" subject="%S" object="Strategic" weight="1"/>
  </relinst>
  <relinst type="is out of scope for the framework" object="true" cf="100"
           name="[US] E17 - a regulatory reporting control is outside a listed issuer determination (17 CFR 240.13a-15 f and 12 CFR 363.1 c by contrast)"
           alt="The control is over regulatory reporting and the regime is listed issuer reporting, which reaches financial reporting only">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="SOX 404 Listed Issuer" weight="1"/>
    <condition rel="has control scope" subject="%S" object="Reporting" weight="1"/>
  </relinst>
  <relinst type="has scope decline reason" cf="100"
           name="[US] A3 - reason a control outside financial reporting receives no US determination (17 CFR 240.13a-15 f and 17 CFR 229.308 a 2)"
           alt="Explains that a control of scope {{%CS}} receives no US determination, and that this is not a finding against the control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is out of scope for the framework" subject="%S" object="true" weight="1"/>
    <condition rel="has control scope" subject="%S" object="%CS" weight="1"/>
    <condition expression="'No determination is reached on the US path. The scope recorded for this control is ' + %CS + '. A US determination covers internal control over financial reporting as defined at 17 CFR 240.13a-15 f, which is what Regulation S-K Item 308 a 2 asks management to assess. This is a statement about the boundary of the framework and not a finding against the control. The same control can be assessed on the UK path, whose own scope sentence is wider.'" value="%O"/>
  </relinst>
  <relinst type="has scope decline reason" cf="100"
           name="[US] E17 - reason a regulatory reporting control is declined under the listed issuer regime (17 CFR 240.13a-15 f and 12 CFR 363.1 c)"
           alt="Explains that a regulatory reporting control is outside a listed issuer determination but would be inside a Part 363 one">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="SOX 404 Listed Issuer" weight="1"/>
    <condition rel="has control scope" subject="%S" object="Reporting" weight="1"/>
    <condition expression="'No determination is reached on the US path for this control under the listed issuer regime, whose scope is internal control over financial reporting as defined at 17 CFR 240.13a-15 f. The boundary moves with the regime: on a 12 CFR Part 363 determination the same control is in scope, because financial reporting there includes the statements prepared for regulatory reporting purposes, 12 CFR 363.1 c.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] A3 - the control scope has not been supplied so the ICFR boundary cannot be tested (17 CFR 240.13a-15 f)"
           alt="No control scope has been supplied, and the US path tests the ICFR boundary before anything else">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition expression="countRelationshipInstances(%S,'has control scope',*) is equal to 0" weight="1"
               alt="No control scope has been supplied for this control"/>
    <condition expression="'What is the scope of this control - financial reporting, operational, reporting, compliance or strategic. A US determination covers internal control over financial reporting as defined at 17 CFR 240.13a-15 f, so no determination is reached until the scope is known.'" value="%O"/>
  </relinst>
  <relinst type="is out of scope for the framework" object="true" cf="100"
           name="[US] E18 - an acquired business control is excluded where assessment is not feasible and no prior exclusion was taken (12 CFR Part 363 App A Guideline 8B)"
           alt="The control belongs to a business acquired in the period, assessment before the report due date is not feasible, and the one permitted exclusion has not already been taken">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior year exclusion already taken','true') is equal to 0" weight="1"
               alt="No prior annual assessment is recorded as having taken the acquired business exclusion for this control"/>
  </relinst>
  <relinst type="has acquired business outcome" cf="100"
           name="[US] E18 - the acquired business exclusion is available this year (12 CFR Part 363 App A Guideline 8B)"
           alt="States that the acquired business exclusion is available and that disclosure obligations still attach">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior year exclusion already taken','true') is equal to 0" weight="1"
               alt="No prior annual assessment is recorded as having taken the acquired business exclusion for this control"/>
    <condition expression="'Control excluded as acquired business scope. The internal control of a business acquired during the year may be excluded from the assessment where assessment is not feasible before the report due date, 12 CFR Part 363 Appendix A Guideline 8B. The exclusion does not remove the reporting obligations: the report must identify the acquired business, state the exclusion and indicate its significance, and material control changes arising from the acquisition must still be disclosed. An acquired institution that remains subject to Part 363 in its own right continues to file its own report.'" value="%O"/>
  </relinst>
  <relinst type="has acquired business disclosure" object="Acquired business identified and the exclusion stated" cf="100"
           name="[US] E18 - the report identifies the acquired business and states the exclusion (12 CFR Part 363 App A Guideline 8B)"
           alt="Where the exclusion is taken, the report must identify the acquired business and state that its control was excluded">
    <condition rel="has acquired business outcome" subject="%S" object="%ABO"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior year exclusion already taken','true') is equal to 0" weight="1"
               alt="No prior annual assessment is recorded as having taken the acquired business exclusion for this control"/>
  </relinst>
  <relinst type="has acquired business disclosure" object="Significance of the acquired business indicated" cf="100"
           name="[US] E18 - the report indicates the significance of the acquired business (12 CFR Part 363 App A Guideline 8B)"
           alt="Where the exclusion is taken, the report must indicate the significance of the acquired business">
    <condition rel="has acquired business outcome" subject="%S" object="%ABO"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior year exclusion already taken','true') is equal to 0" weight="1"
               alt="No prior annual assessment is recorded as having taken the acquired business exclusion for this control"/>
  </relinst>
  <relinst type="has acquired business disclosure" object="Material control changes arising from the acquisition disclosed" cf="100"
           name="[US] E18 - material control changes from the acquisition are still disclosable (12 CFR Part 363 App A Guideline 8B)"
           alt="The exclusion does not remove the obligation to disclose material control changes arising from the acquisition">
    <condition rel="has acquired business outcome" subject="%S" object="%ABO"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior year exclusion already taken','true') is equal to 0" weight="1"
               alt="No prior annual assessment is recorded as having taken the acquired business exclusion for this control"/>
  </relinst>
  <relinst type="has acquired business outcome" cf="100"
           name="[US] E18 - the acquired business exclusion is spent after one annual assessment (12 CFR Part 363 App A Guideline 8B)"
           alt="The exclusion was already taken for a prior annual assessment, so it is unavailable and the control must be assessed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="prior year exclusion already taken" subject="%S" object="true" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="acquired business exclusion years permitted" subject="%P" object="%YP" weight="1"/>
    <condition expression="'Acquired business exclusion unavailable. The exclusion runs for ' + %YP" value="%YPTEXT"/>
    <condition expression="%YPTEXT + ' annual assessment only, 12 CFR Part 363 Appendix A Guideline 8B, and it has already been taken for this acquired business. The control is assessed on the ordinary scope test this year.'" value="%O"/>
  </relinst>
  <relinst type="has acquired business outcome" cf="100"
           name="[US] E18 - assessment is feasible so no acquired business exclusion arises (12 CFR Part 363 App A Guideline 8B)"
           alt="The business was acquired in the period but assessment before the report due date is feasible, so the exclusion does not arise">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="acquired in period" subject="%S" object="true" weight="1"/>
    <condition rel="assessment feasible before due date" subject="%S" object="true" weight="1"/>
    <condition expression="'No acquired business exclusion. The exclusion is conditional on assessment not being feasible before the report due date, 12 CFR Part 363 Appendix A Guideline 8B. Assessment is recorded as feasible here, so the control is assessed in the ordinary way and the acquisition changes nothing about the determination.'" value="%O"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[US] E15 - an inability to assess is not a permitted scope limitation (SEC Release 33-8810 II.B.5)"
           alt="Where the assessment could not reach part of internal control, the US path offers no scope limitation and the judgement rests with management">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has untestable item count" subject="%S" object="%UIC" weight="1"/>
    <condition expression="%UIC is greater than 0" weight="1"
               alt="There are {{%UIC}} items the assessment could not reach"/>
    <condition expression="'No scope limitation is available. Where management is unable to assess part of internal control over financial reporting, the inability is not a permitted scope limitation: management must determine whether the inability to assess is significant enough to compel the conclusion that internal control over financial reporting is not effective, SEC Release 33-8810 section II.B.5. That determination is management s own and is taken as an input here, not reached by this graph.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="Management" cf="100"
           name="[US] E15 G5 - the significance of an inability to assess is a management judgement (SEC Release 33-8810 II.B.5)"
           alt="Names management as the owner of the judgement on whether an inability to assess compels an ineffective conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has untestable item count" subject="%S" object="%UIC" weight="1"/>
    <condition expression="%UIC is greater than 0" weight="1"
               alt="There are {{%UIC}} items the assessment could not reach"/>
  </relinst>
  <relinst type="has applied instrument" object="PCAOB AS 2201 as cited AS No 5 text" cf="100"
           name="[US] G8 - AS 2201 is applied on the US path (PCAOB AS 2201, the standard on an audit of internal control)"
           alt="Names the version of AS 2201 the determination applied">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="PCAOB AS 2315 Audit Sampling current text" cf="100"
           name="[US] G8 - AS 2315 is applied where a sample was drawn (PCAOB AS 2315, Audit Sampling)"
           alt="Names the version of AS 2315 applied, because a sample size or a deviation rate was evaluated">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has sample size tested" subject="%S" object="%SS" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="PCAOB AS 1105 Audit Evidence current text" cf="100"
           name="[US] G8 - AS 1105 is applied where evidence reliability was evaluated (PCAOB AS 1105, Audit Evidence)"
           alt="Names the version of AS 1105 applied, because the source class of the evidence was evaluated">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has evidence source class" subject="%S" object="%ESC" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="PCAOB Staff Audit Practice Alert 11 of 24 October 2013" cf="100"
           name="[US] G8 - Practice Alert 11 is applied to a management review control (PCAOB Staff Audit Practice Alert 11)"
           alt="Names the practice alert applied, because the control is a management review control whose precision was assessed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="SEC Release 33-8810 of 20 June 2007" cf="100"
           name="[US] G8 - Release 33-8810 is applied on the US path (SEC Release 33-8810, management guidance)"
           alt="Names the SEC management guidance release the determination applied">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="Regulation S-K Item 308 as amended" cf="100"
           name="[US] G8 - Item 308 is applied on a listed issuer determination (17 CFR 229.308)"
           alt="Names the Regulation S-K item that sets the content of a listed issuer internal control report">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="SOX 404 Listed Issuer" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="FDIC 12 CFR Part 363 effective 1 January 2026" cf="100"
           name="[US] G8 - Part 363 is applied on a FDICIA determination (12 CFR Part 363)"
           alt="Names the version of Part 363 applied on a FDICIA reporting determination">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has reporting regime" subject="%S" object="FDICIA Part 363" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="SEC Release 33-8829 effective 10 September 2007" cf="100"
           name="[US] G8 - Release 33-8829 is applied where the significant deficiency threshold is reached (SEC Release 33-8829)"
           alt="Names the release that settled the definition of a significant deficiency, applied because a materiality band was evaluated">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has materiality band" subject="%S" object="%MB" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="PCAOB AS 1305 current text" cf="100"
           name="[US] G8 - AS 1305 is applied where a deficiency must be communicated (PCAOB AS 1305, communications about control deficiencies)"
           alt="Names the version of AS 1305 applied, because a deficiency was recorded against the control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has deficiency" subject="%S" object="%D" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="PCAOB AS 2201 as cited AS No 5 text" cf="100"
           name="[US] G8 - a deficiency on the US path applies AS 2201 (PCAOB AS 2201 paras 62 to 70, evaluating deficiencies)"
           alt="Names the version of AS 2201 the severity determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="SEC Release 33-8810 of 20 June 2007" cf="100"
           name="[US] G8 - a deficiency on the US path applies Release 33-8810 (SEC Release 33-8810 II.B)"
           alt="Names the SEC management guidance release the severity and disclosure determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="SEC Release 33-8829 effective 10 September 2007" cf="100"
           name="[US] G8 - a deficiency on the US path applies Release 33-8829 (SEC Release 33-8829, definition of significant deficiency)"
           alt="Names the release that settled the definition of a significant deficiency">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="PCAOB AS 1305 current text" cf="100"
           name="[US] G8 - a deficiency on the US path applies AS 1305 (PCAOB AS 1305 paras 04 to 09)"
           alt="Names the version of AS 1305 the communication determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="Regulation S-K Item 308 as amended" cf="100"
           name="[US] G8 - a listed issuer deficiency applies Item 308 (17 CFR 229.308 a 3)"
           alt="Names the Regulation S-K item that carries the preclusion and the disclosure obligation">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
    <condition rel="has reporting regime" subject="%C" object="SOX 404 Listed Issuer" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="FDIC 12 CFR Part 363 effective 1 January 2026" cf="100"
           name="[US] G8 - a FDICIA deficiency applies Part 363 (12 CFR 363.2 b 3 iii)"
           alt="Names the version of Part 363 that carries the preclusion on a FDICIA determination">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="US ICFR" weight="1"/>
    <condition rel="has reporting regime" subject="%C" object="FDICIA Part 363" weight="1"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[UK] F6 - a financial control is within the Provision 29 scope sentence (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="The control is a financial control, one of the four categories the monitoring and review should cover">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Financial Reporting" weight="1"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[UK] F6 - an operational control is within the Provision 29 scope sentence (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="The control is an operational control, one of the four categories the monitoring and review should cover">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Operational" weight="1"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[UK] F6 - a reporting control is within the Provision 29 scope sentence (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="The control is a reporting control, the category the 2024 edition added to the three the earlier edition carried">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Reporting" weight="1"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[UK] F6 - a compliance control is within the Provision 29 scope sentence (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="The control is a compliance control, one of the four categories the monitoring and review should cover">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Compliance" weight="1"/>
  </relinst>
  <relinst type="has scope basis" cf="100"
           name="[UK] A4 F6 - statement of the four category scope the UK path applied (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="States that a control of scope {{%CS}} is inside the UK path because the Code covers four categories, not financial reporting alone">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is in scope for the framework" subject="%S" object="true" weight="1"/>
    <condition rel="has control scope" subject="%S" object="%CS" weight="1"/>
    <condition expression="'Scope applied: all material controls. The scope recorded for this control is ' + %CS + '. The monitoring and review should cover all material controls, including financial, operational, reporting and compliance controls, Provision 29 of the UK Corporate Governance Code 2024, scope sentence. The reporting category is the one the 2024 edition added. This path is therefore wider than a determination restricted to financial reporting, and the same control may be in scope here and out of scope on the other path.'" value="%O"/>
  </relinst>
  <relinst type="is in scope for the framework" object="true" cf="100"
           name="[UK] F6a - a strategic control is assessed with the gap in the sources flagged (FRC Corporate Governance Code Guidance 2024 para 248)"
           alt="The control is a strategic control, which the guidance lists as a fifth aspect though Provision 29 names four">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Strategic" weight="1"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] F6a - whether a strategic control is inside the declaration is unresolved (Code 2024 Provision 29 scope sentence and FRC Guidance para 248)"
           alt="Records that the Code names four control categories and the guidance five, and that neither resolves whether a strategic control is inside the declaration">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Strategic" weight="1"/>
    <condition expression="'Unresolved in the sources: whether a strategic control falls inside the declaration. Provision 29 names four categories of material control - financial, operational, reporting and compliance. The FRC guidance describes controls as spanning five aspects, adding strategic, at paragraph 248. Neither text says whether the fifth sits inside the declaration. The control is assessed here and the gap is reported rather than resolved. Whether to include it is a board judgement.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Board" cf="100"
           name="[UK] F6a G5 - whether to bring a strategic control inside the declaration is a board judgement (FRC Corporate Governance Code Guidance 2024 para 248)"
           alt="Names the board as the owner of the judgement on whether a strategic control is inside the declaration">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has control scope" subject="%S" object="Strategic" weight="1"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] F6 - the control scope has not been supplied so the category cannot be named (UK Corporate Governance Code 2024 Provision 29 scope sentence)"
           alt="No control scope has been supplied, and the UK output names the category the control was assessed in">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition expression="countRelationshipInstances(%S,'has control scope',*) is equal to 0" weight="1"
               alt="No control scope has been supplied for this control"/>
    <condition expression="'What is the scope of this control - financial, operational, reporting, compliance or strategic. All four Provision 29 categories are in scope on this path, so the answer does not decide whether the control is assessed, but the output names the category and the fifth aspect carries an unresolved question in the sources.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Board" cf="100"
           name="[UK] A5 F5a G5 - the material control designation is a board judgement taken as an input (FRC Guidance 2024 exec summary para 8 and paras 270 to 271)"
           alt="Names the board as the owner of the material control designation, which the graph consumes and never derives">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="%MC" weight="1"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[UK] A5 F5a - the material control designation was supplied and not derived (FRC Guidance 2024 exec summary para 8 and paras 270 to 271)"
           alt="States that the material control designation is the board's own and was taken as an input here">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="%MC" weight="1"/>
    <condition expression="'Judgement taken as an input: whether this is a material control. The FRC states that it is not its role or intention to prescribe or dictate what a material control is for a company, FRC guidance executive summary paragraph 8, and that material controls are company specific by size, business model, strategy, operations, structure and complexity, paragraph 270. The test the board applies is how a hypothetical deficiency in the control could impact the interests of the company, its shareholders and other stakeholders, paragraph 271. The designation is consumed here and never derived.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] A5 F5a - the material control designation has not been supplied (UK Corporate Governance Code 2024 Provision 29 and FRC Guidance para 271)"
           alt="No material control designation has been supplied, and the declaration consequence turns on it">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition expression="countRelationshipInstances(%S,'is material control',*) is equal to 0" weight="1"
               alt="No material control designation has been supplied for this control"/>
    <condition expression="'Has the board designated this a material control. The declaration under Provision 29 is about material controls, so the designation decides whether a failure carries a declaration consequence or only a reporting and communication one. It is the board s own judgement, FRC guidance paragraph 271, and is never derived here.'" value="%O"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Description of how the board monitored and reviewed the framework" cf="100"
           name="[UK] F3a - the first Provision 29 bullet is a disclosure the board must supply (UK Corporate Governance Code 2024 Provision 29 first bullet and FRC Guidance para 290)"
           alt="Names the monitoring and review description as a required Provision 29 disclosure, whatever this control's determination turns out to be">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F3a F3b - the determination is about this control and not the framework (Code 2024 Provision 29 first bullet and FRC Guidance exec summary para 8)"
           alt="States the boundary of the output: one control, not the bank's framework, and names the framework level disclosure the board owes separately">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'Boundary of this output. The determination here is about this control. The declaration under Provision 29 relates to the internal controls and not to the framework as a whole, FRC guidance executive summary paragraph 8, whereas the annual effectiveness review behind it is of the framework. Provision 29 also requires a description of how the board has monitored and reviewed the effectiveness of the framework, first bullet, mirrored at guidance paragraph 290. That description is the board s to write and is not produced here.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F1b - the declaration is a reasonable conclusion and not a guarantee (FRC Corporate Governance Code Guidance 2024 paras 286 and 296)"
           alt="States that the declaration is a reasonable conclusion from the work done, not a guarantee, and that an effective control does not remove the risk">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'How far the conclusion goes. A declaration of effectiveness is a reasonable conclusion drawn from the work carried out and the evidence obtained; it is not a guarantee and it is not absolute certainty, FRC guidance paragraph 296. An effective control reduces but does not eliminate the underlying risk, paragraph 286. Nothing in this output is assurance against a future failure.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F10a - the declaration is other information and not an audited statement (FRC Provision 29 Mythbuster on auditor responsibilities 24 June 2026 and ISA UK 720)"
           alt="States that the declaration is read by the auditor as other information and that this output is a board determination rather than an audit opinion">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'Status of the statement. Auditing standards were not changed or extended in response to the Code. The auditor reads and considers the declaration as other information for material inconsistency under ISA UK 720, and performing those procedures does not represent an assurance engagement, FRC Provision 29 Mythbuster on auditor responsibilities, 24 June 2026. The board s material controls and the controls relevant to the audit overlap but are not identical and serve different purposes. This output is a management and board determination, not an audit opinion.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F10b - no external assurance over material control effectiveness is required (FRC Corporate Governance Code Guidance 2024 paras 274 to 276)"
           alt="States that external assurance is a board choice and that its absence is never treated as a deficiency here">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'External assurance. Neither the Code nor the guidance requires or expects external assurance over the effectiveness of material controls; whether to obtain any is a board decision, FRC guidance paragraphs 274 to 276. The absence of external assurance is therefore never treated here as a deficiency or as a gap in evidence.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F14 - the edition applied and the periods it reaches (UK Corporate Governance Code 2024 Application section and Provision 29 footnote 9)"
           alt="Names the Code edition the determination applied and the accounting periods Provision 29 reaches">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'Edition applied: the UK Corporate Governance Code 2024, with the FRC Corporate Governance Code Guidance as last updated 3 June 2026. Provision 29 applies to accounting periods beginning on or after 1 January 2026, Application section and Provision 29 footnote 9, with first reporting expected in 2027. For an earlier accounting period the predecessor edition of the provision applies instead, and no rule in this graph is drawn from it.'" value="%O"/>
  </relinst>
  <relinst type="has applied instrument" object="UK Corporate Governance Code 2024" cf="100"
           name="[UK] G8 - the Code 2024 is applied on the UK path (UK Corporate Governance Code 2024 Provision 29)"
           alt="Names the Code edition the determination applied">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="FRC Corporate Governance Code Guidance 2024 updated 3 June 2026" cf="100"
           name="[UK] G8 - the FRC guidance edition is applied on the UK path (FRC Corporate Governance Code Guidance Section 4)"
           alt="Names the edition of the FRC guidance the determination applied">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="ISA UK 265 Updated September 2025" cf="100"
           name="[UK] F10c G8 - ISA UK 265 is applied as the bridge to the Code (ISA UK 265 para A12-1)"
           alt="Names the revision of ISA UK 265 applied, which is the standard that joins the audit communication duty to the Code">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="ISA UK 330 Revised July 2017 Updated September 2025" cf="100"
           name="[UK] G8 - ISA UK 330 is applied where test timing or prior period evidence was evaluated (ISA UK 330 paras 11 to 17)"
           alt="Names the revision of ISA UK 330 applied, because the period of reliance or the response to a deviation was evaluated">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has sample size tested" subject="%S" object="%SS" weight="1"/>
  </relinst>
  <relinst type="has applied instrument" object="ISA UK 315 Revised July 2020 Updated September 2025" cf="100"
           name="[UK] G8 - ISA UK 315 is applied where general IT controls were evaluated (ISA UK 315 paras 26 and 27)"
           alt="Names the revision of ISA UK 315 applied, because reliance on general IT controls was evaluated">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has itgc conclusion" subject="%S" object="%IC" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="UK Corporate Governance Code 2024" cf="100"
           name="[UK] G8 - a deficiency on the UK path applies the Code 2024 (UK Corporate Governance Code 2024 Provision 29 third bullet)"
           alt="Names the Code edition the declaration determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="FRC Corporate Governance Code Guidance 2024 updated 3 June 2026" cf="100"
           name="[UK] G8 - a deficiency on the UK path applies the FRC guidance (FRC Corporate Governance Code Guidance paras 290 to 300)"
           alt="Names the edition of the FRC guidance the declaration determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="ISA UK 265 Updated September 2025" cf="100"
           name="[UK] G8 - a deficiency on the UK path applies ISA UK 265 (ISA UK 265 paras 6 to 11)"
           alt="Names the revision of ISA UK 265 the classification and communication determination applied">
    <condition rel="deficiency of control" subject="%S" object="%C"/>
    <condition rel="has framework" subject="%C" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has attribute clearance" object="Performer Role" cf="100"
           name="[CORE] B2 - the performing role is stated (AS 2201 para 42, operated as prescribed by a person with authority and competence)"
           alt="The role that performs the control is recorded as {{%PR}}, so the performer attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has performer role" subject="%S" object="%PR" weight="1"/>
  </relinst>
  <relinst type="has attribute clearance" object="Performer Role" cf="100"
           name="[CORE] B2 B4 - an automated control establishes the performer attribute through the application it runs in (AS 2201 para B28)"
           alt="The control is automated and runs in an application, so it has no human performer and the attribute is established without one">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="relies on application" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Performer Role" cf="100"
           name="[CORE] B2 - no performing role is stated for a control that needs one (AS 2201 para 42)"
           alt="No performing role is recorded and the control is not an automated application control, so the performer attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance','Performer Role') is equal to 0" weight="1"
               alt="The performer attribute has not been established for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the performing role is not stated (AS 2201 para 42)"
           alt="States that the performing role is missing and why that defeats the design test">
    <condition rel="has missing attribute" subject="%S" object="Performer Role"/>
    <condition expression="'Missing design attribute: the role that performs the control. Design effectiveness is tested by asking whether the control, if operated as prescribed by a person with the necessary authority and competence, satisfies the control objective, AS 2201 paragraph 42. With no performing role recorded that test cannot be applied. Record the role, never a named person.'" value="%O"/>
  </relinst>
  <relinst type="has attribute clearance" object="Frequency" cf="100"
           name="[CORE] B2 - the frequency of operation is stated (AS 2201 para 46, frequency bears on the evidence needed)"
           alt="The control is recorded as operating {{%FR}}, so the frequency attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has frequency" subject="%S" object="%FR" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Frequency" cf="100"
           name="[CORE] B2 - no frequency of operation is stated (AS 2201 para 46)"
           alt="No frequency is recorded, so the frequency attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has frequency',*) is equal to 0" weight="1"
               alt="No frequency of operation has been recorded for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the frequency of operation is not stated (AS 2201 para 46)"
           alt="States that the frequency is missing and what downstream test it blocks">
    <condition rel="has missing attribute" subject="%S" object="Frequency"/>
    <condition expression="'Missing design attribute: how often the control operates. The nature, timing and extent of the evidence needed turns in part on the frequency with which the control operates, AS 2201 paragraph 46, so without it neither the design test nor the required extent of testing can be settled.'" value="%O"/>
  </relinst>
  <relinst type="has attribute clearance" object="Timing" cf="100"
           name="[CORE] B2 - the timing relative to the transaction is stated (AS 2201 para 42, prevent or detect on a timely basis)"
           alt="The control is recorded as operating {{%TM}}, so the timing attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has timing" subject="%S" object="%TM" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Timing" cf="100"
           name="[CORE] B2 - no timing relative to the transaction is stated (AS 2201 para 42)"
           alt="No timing is recorded, so the timing attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has timing',*) is equal to 0" weight="1"
               alt="No timing relative to the transaction has been recorded for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the timing relative to the transaction is not stated (AS 2201 para 42)"
           alt="States that the timing is missing and why the timeliness test needs it">
    <condition rel="has missing attribute" subject="%S" object="Timing"/>
    <condition expression="'Missing design attribute: when the control operates relative to the transaction. The design test asks whether the control can prevent, or detect and correct, a misstatement on a timely basis, AS 2201 paragraph 42, which cannot be judged without knowing whether the control acts before or after the transaction.'" value="%O"/>
  </relinst>
  <relinst type="has attribute clearance" object="Procedure Described" cf="100"
           name="[CORE] B2 - the procedure the performer carries out is described (AS 2201 paras 42 and 43, operated as prescribed)"
           alt="The documentation describes the procedure the performer carries out, so the procedure attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has procedure described" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Procedure Described" cf="100"
           name="[CORE] B2 - the procedure the performer carries out is not described (AS 2201 paras 42 and 43)"
           alt="The procedure is not described, or no answer was given, so the procedure attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance','Procedure Described') is equal to 0" weight="1"
               alt="The procedure attribute has not been established for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the procedure is not described (AS 2201 paras 42 and 43)"
           alt="States that the procedure is not described and why the design test cannot be applied without it">
    <condition rel="has missing attribute" subject="%S" object="Procedure Described"/>
    <condition expression="'Missing design attribute: a description of the procedure the performer carries out. Design effectiveness asks whether the control operated as prescribed would satisfy the control objective, AS 2201 paragraph 42, and the walkthrough that ordinarily establishes it inspects the relevant documentation, paragraph 43. Neither is possible where the prescribed procedure is not written down.'" value="%O"/>
  </relinst>
  <relinst type="has attribute clearance" object="Evidence Produced" cf="100"
           name="[CORE] B2 - the control produces evidence of its performance (AS 2201 para 43, inspection of relevant documentation)"
           alt="The control produces evidence of its performance, so the evidence attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="produces evidence" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Evidence Produced" cf="100"
           name="[CORE] B2 - the control produces no evidence of its performance (AS 2201 para 43)"
           alt="The control produces no evidence, or no answer was given, so the evidence attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance','Evidence Produced') is equal to 0" weight="1"
               alt="The evidence attribute has not been established for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the control produces no evidence of performance (AS 2201 paras 43 and 45)"
           alt="States that the control produces no evidence and what that costs on both decision points">
    <condition rel="has missing attribute" subject="%S" object="Evidence Produced"/>
    <condition expression="'Missing design attribute: evidence of performance. A walkthrough of the control inspects the relevant documentation, AS 2201 paragraph 43, and an operating effectiveness test uses a mix of procedures that includes re-performance, paragraph 45. A control that leaves no trace of its performance can be described but it cannot be tested, so the gap bears on design and on operating effectiveness alike.'" value="%O"/>
  </relinst>
  <relinst type="has attribute clearance" object="Precision Or Threshold" cf="100"
           name="[CORE] B2 - the precision or threshold at which the control operates is stated (AS 2201 para 42 and PCAOB Practice Alert 11 pp 20 to 21)"
           alt="The precision or threshold at which the control operates is recorded, so that attribute is established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="states precision threshold" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has missing attribute" object="Precision Or Threshold" cf="100"
           name="[CORE] B2 - the precision or threshold at which the control operates is not stated (AS 2201 para 42)"
           alt="No precision or threshold is recorded, or no answer was given, so that attribute is missing">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance','Precision Or Threshold') is equal to 0" weight="1"
               alt="The precision attribute has not been established for this control"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B2 B10 - finding that the precision or threshold is not stated (AS 2201 para 42 and PCAOB Practice Alert 11 p 21)"
           alt="States that the precision or threshold is missing and why it decides whether the control could meet its objective">
    <condition rel="has missing attribute" subject="%S" object="Precision Or Threshold"/>
    <condition expression="'Missing design attribute: the precision or threshold at which the control operates. Whether a control could satisfy its objective depends on how finely it operates, AS 2201 paragraph 42, and the criteria for investigating a difference are one of the factors bearing on the precision of a review, PCAOB Staff Audit Practice Alert 11 page 21. Without a stated threshold the control cannot be shown capable of catching what it is meant to catch.'" value="%O"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B2 B10 - statement of how many required design attributes are established (AS 2201 para 42)"
           alt="States how many of the required design attributes are established and how many the method requires">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="required attribute count" subject="%P" object="%RAC" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance',*)" value="%CLEARED" weight="1"
               alt="Counts the design attributes established for this control"/>
    <condition expression="'Design attribute coverage: ' + %CLEARED + ' of ' + %RAC + ' required attributes established. The required set is the performing role, the frequency, the timing relative to the transaction, the procedure described, the evidence produced and the precision or threshold stated. Each one not established is named separately above.'" value="%O"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B9 B9a - design and operating effectiveness are separate tests (AS 2201 paras 42 43 and 45)"
           alt="States that a design conclusion rests on a walkthrough and never carries an operating effectiveness conclusion with it">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'What a design conclusion does and does not say. Design effectiveness is established by determining whether the control, operated as prescribed by a person with the necessary authority and competence, would satisfy the control objective, AS 2201 paragraph 42; a walkthrough of inquiry, observation and inspection is ordinarily sufficient and re-performance is not required, paragraph 43. Operating effectiveness needs a mix of procedures that includes re-performance, paragraph 45. A design conclusion therefore says nothing about whether the control actually operated.'" value="%O"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B9c - less evidence is needed for an adverse conclusion than for a favourable one (AS 2201 para 47 Note)"
           alt="Explains the asymmetry: a design gap defeats the favourable conclusion even though the favourable one needs the full set">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has missing attribute',*) is greater than or equal to 1" weight="1"
               alt="At least one required design attribute is not established"/>
    <condition expression="'Why one gap is enough. Less evidence is needed to conclude that a control is not effective than to conclude that it is effective, AS 2201 paragraph 47 Note. A favourable design conclusion here requires every required attribute to be positively established; a single attribute left unestablished defeats it, and an unanswered question counts as unestablished rather than as a pass.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B1 - no risk is recorded for the control to address (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="No risk is recorded against the control, so whether it addresses its risk cannot be assessed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'addresses risk',*) is equal to 0" weight="1"
               alt="No risk has been recorded for this control to address"/>
    <condition expression="'No risk recorded. A design deficiency exists where a necessary control is missing, or where an existing control is so designed that the control objective would not be met even if the control operated as designed, AS 2201 paragraph A3 and SEC Release 33-8810 footnote 29. Both limbs are judged against the risk the control is there to address, so the risk must be recorded before design can be concluded on.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] B1 - the risk the control addresses has not been supplied (AS 2201 para A3)"
           alt="Asks for the risk the control addresses, which the design test is applied against">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'addresses risk',*) is equal to 0" weight="1"
               alt="No risk has been recorded for this control to address"/>
    <condition expression="'Which risk does this control address, as the bank records it. The design test asks whether the control as designed would meet its objective against that risk, AS 2201 paragraph A3, so no design conclusion is reached without it.'" value="%O"/>
  </relinst>
  <relinst type="has missing attribute" object="Risk Coverage" cf="100"
           name="[CORE] B1 B3 - the control is recorded as not addressing the risk it is there to address (AS 2201 para A3 second limb)"
           alt="The control is recorded as not addressing its stated risk, so the risk coverage attribute is not established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="addresses the stated risk" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B1 B3 - finding that the control would not meet its objective even if operated as designed (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="States that a control not addressing its stated risk is design deficient on the second limb of the definition">
    <condition rel="has missing attribute" subject="%S" object="Risk Coverage"/>
    <condition expression="'Design deficiency on risk coverage. The control is recorded as not addressing the risk it is there to address. A design deficiency exists where an existing control is so designed that the control objective would not be met even if the control operated as designed, AS 2201 paragraph A3 second limb and SEC Release 33-8810 footnote 29. No amount of evidence that the control was performed answers this: a control that would not meet its objective when operated exactly as described is deficient in design, and testing how often it was performed cannot cure that. The international text reaches the same place from the other side - a control designed such that it cannot prevent, or detect and correct, misstatements on a timely basis is a deficiency in internal control, ISA UK 265 paragraph 6 a i.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Second Line Controls Function" cf="100"
           name="[CORE] B1 G5 - whether the control as described addresses its risk is a judgement taken as an input (AS 2201 para A3)"
           alt="Names the role that should own the judgement that the control as described addresses the risk recorded against it">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="addresses risk" subject="%S" object="%RK" weight="1"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] B1 G5 - statement that the risk mapping was taken as given (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="States that the mapping of this control to the risk {{%RK}} was supplied rather than evaluated here">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="addresses risk" subject="%S" object="%RK" weight="1"/>
    <condition expression="'Judgement taken as an input: that this control is the one addressing the risk recorded against it, namely ' + %RK + '. No source turns a control description and a risk description into that mapping, so it is supplied by the bank. Whether a necessary control is missing altogether, AS 2201 paragraph A3 first limb, is a question about the bank s control framework and is outside what a single control assessment can answer.'" value="%O"/>
  </relinst>
  <relinst type="has confirmed control type" object="Automated" cf="100"
           name="[CORE] B4 - automated type confirmed by reliance on an application with no human performer (AS 2201 para B28)"
           alt="The control is recorded as automated and relies on an application with no performing role, so the type is confirmed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="relies on application" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has performer role',*) is equal to 0" weight="1"
               alt="No human performing role is recorded for this control"/>
  </relinst>
  <relinst type="has corrected control type" object="IT Dependent Manual" cf="100"
           name="[CORE] B4 - automated type corrected to IT dependent manual where a person performs it using an application (AS 2201 paras 39 to 41 and para B28)"
           alt="The control is recorded as automated but a person performs it using an application, which is the IT dependent manual type">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="relies on application" subject="%S" object="true" weight="1"/>
    <condition rel="has performer role" subject="%S" object="%PR" weight="1"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B4 B10 - statement that the automated type was corrected to IT dependent manual (AS 2201 paras 39 to 41 and para B28)"
           alt="States the type correction and why it matters for how the control must be tested">
    <condition rel="has corrected control type" subject="%S" object="IT Dependent Manual"/>
    <condition rel="has control type" subject="%S" object="Automated" weight="1"/>
    <condition expression="'Classification corrected: recorded as automated, assessed as IT dependent manual. A person performs this control using the output of an application. An entirely automated application control is treated differently because it is not subject to breakdown through human failure, AS 2201 paragraph B28, and the testing paragraphs treat an IT dependent manual control as a distinct type, paragraphs 39 to 41. The correction changes how the control must be tested and what general IT controls it depends on. It is not by itself a design deficiency.'" value="%O"/>
  </relinst>
  <relinst type="has confirmed control type" object="IT Dependent Manual" cf="100"
           name="[CORE] B4 - IT dependent manual type confirmed by a human performer using an application (AS 2201 paras 39 to 41)"
           alt="The control is recorded as IT dependent manual, relies on an application and has a performing role, so the type is confirmed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="IT Dependent Manual" weight="1"/>
    <condition rel="relies on application" subject="%S" object="true" weight="1"/>
    <condition rel="has performer role" subject="%S" object="%PR" weight="1"/>
  </relinst>
  <relinst type="has corrected control type" object="Manual" cf="100"
           name="[CORE] B4 - IT dependent manual type corrected to manual where no application is relied on (AS 2201 paras 39 to 41)"
           alt="The control is recorded as IT dependent manual but relies on no application, so it is a manual control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="IT Dependent Manual" weight="1"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B4 B10 - statement that the IT dependent manual type was corrected to manual (AS 2201 paras 39 to 41)"
           alt="States that the recorded IT dependency is absent, so the control is manual and no general IT control reliance arises">
    <condition rel="has corrected control type" subject="%S" object="Manual"/>
    <condition rel="has control type" subject="%S" object="IT Dependent Manual" weight="1"/>
    <condition expression="'Classification corrected: recorded as IT dependent manual, assessed as manual. The control relies on no application, so the dependency that defines the IT dependent manual type is absent, AS 2201 paragraphs 39 to 41. Reliance on general IT controls therefore does not arise for this control. The correction is a classification output and not by itself a design deficiency.'" value="%O"/>
  </relinst>
  <relinst type="has confirmed control type" object="Manual" cf="100"
           name="[CORE] B4 - manual type confirmed by a human performer with no application relied on (AS 2201 paras 39 to 41)"
           alt="The control is recorded as manual, has a performing role and relies on no application, so the type is confirmed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="Manual" weight="1"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
    <condition rel="has performer role" subject="%S" object="%PR" weight="1"/>
  </relinst>
  <relinst type="has corrected control type" object="IT Dependent Manual" cf="100"
           name="[CORE] B4 - manual type corrected to IT dependent manual where an application is relied on (AS 2201 paras 39 to 41)"
           alt="The control is recorded as manual but relies on an application, so it is an IT dependent manual control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has control type" subject="%S" object="Manual" weight="1"/>
    <condition rel="relies on application" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B4 B10 - statement that the manual type was corrected because an application is relied on (AS 2201 paras 39 to 41)"
           alt="States that the control relies on an application, so it is IT dependent manual and general IT control reliance arises">
    <condition rel="has corrected control type" subject="%S" object="IT Dependent Manual"/>
    <condition rel="has control type" subject="%S" object="Manual" weight="1"/>
    <condition expression="'Classification corrected: recorded as manual, assessed as IT dependent manual. The control relies on an application to perform part of what it does, which makes it the IT dependent manual type, AS 2201 paragraphs 39 to 41. The correction matters because the control now depends on the general IT controls over that application, and the reliance test applies.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] B4 - the control type has not been supplied (AS 2201 paras 39 to 41)"
           alt="No control type is recorded, and the type decides how the control must be tested">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has control type',*) is equal to 0" weight="1"
               alt="No control type has been recorded for this control"/>
    <condition expression="'Is this control manual, automated or IT dependent manual. The three types are tested differently, AS 2201 paragraphs 39 to 41, and only an entirely automated application control can be reached by benchmarking, paragraph B28, so the type is confirmed or corrected before testing is evaluated.'" value="%O"/>
  </relinst>
  <relinst type="has confirmed control nature" object="Preventive" cf="100"
           name="[CORE] B4 B5 - preventive nature confirmed by operation before the transaction (practice calibration, parameter timing consistency check)"
           alt="The control is recorded as preventive and operates before the transaction, so the recorded nature is consistent">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="timing consistency check enabled" subject="%P" object="true" weight="1"/>
    <condition rel="has control nature" subject="%S" object="Preventive" weight="1"/>
    <condition rel="has timing" subject="%S" object="Before Transaction" weight="1"/>
  </relinst>
  <relinst type="has confirmed control nature" object="Detective" cf="100"
           name="[CORE] B4 B5 - detective nature confirmed by operation after the transaction (practice calibration, parameter timing consistency check)"
           alt="The control is recorded as detective and operates after the transaction, so the recorded nature is consistent">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="timing consistency check enabled" subject="%P" object="true" weight="1"/>
    <condition rel="has control nature" subject="%S" object="Detective" weight="1"/>
    <condition rel="has timing" subject="%S" object="After Transaction" weight="1"/>
  </relinst>
  <relinst type="has corrected control nature" object="Detective" cf="100"
           name="[CORE] B4 B5 - preventive nature corrected to detective where the control operates after the transaction (practice calibration, parameter timing consistency check)"
           alt="The control is recorded as preventive but operates after the transaction, which practice reads as a detective control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="timing consistency check enabled" subject="%P" object="true" weight="1"/>
    <condition rel="has control nature" subject="%S" object="Preventive" weight="1"/>
    <condition rel="has timing" subject="%S" object="After Transaction" weight="1"/>
  </relinst>
  <relinst type="has corrected control nature" object="Preventive" cf="100"
           name="[CORE] B4 B5 - detective nature corrected to preventive where the control operates before the transaction (practice calibration, parameter timing consistency check)"
           alt="The control is recorded as detective but operates before the transaction, which practice reads as a preventive control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="timing consistency check enabled" subject="%P" object="true" weight="1"/>
    <condition rel="has control nature" subject="%S" object="Detective" weight="1"/>
    <condition rel="has timing" subject="%S" object="Before Transaction" weight="1"/>
  </relinst>
  <relinst type="has design statement" cf="100"
           name="[CORE] B5 B10 - statement that the recorded nature was corrected against the recorded timing (practice calibration, no primary source states the mapping)"
           alt="States the nature correction to {{%CN}} and says plainly that the mapping behind it is practice and not a standard">
    <condition rel="has corrected control nature" subject="%S" object="%CN"/>
    <condition rel="has control nature" subject="%S" object="%ON" weight="1"/>
    <condition expression="'Classification corrected: recorded as ' + %ON + ', assessed as ' + %CN + ' on the recorded timing. This correction rests on a practice calibration and not on a standard: a preventive control is ordinarily understood to operate before the transaction and a detective control after it, but no primary source located in this build defines the two terms by timing, and the standards use them throughout without defining them. The check is exposed as a calibration parameter and can be switched off. It is a classification correction and never by itself a design deficiency.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] B4 - the control nature has not been supplied (AS 2201 para 42 and practice calibration)"
           alt="No control nature is recorded, so the nature cannot be confirmed or corrected">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has control nature',*) is equal to 0" weight="1"
               alt="No control nature has been recorded for this control"/>
    <condition expression="'Is this control preventive or detective. The output confirms or corrects the recorded nature against the recorded timing, which is a practice calibration rather than a rule drawn from a standard, so the answer affects the classification statement and not the determination itself.'" value="%O"/>
  </relinst>
  <relinst type="has review precision conclusion" cf="100"
           name="[CORE] B6 B6a - the review investigation threshold is sufficiently below the materiality band (PCAOB Practice Alert 11 p 21, practice margin)"
           alt="The review threshold at band {{%RTB}} sits far enough below the materiality band {{%MBD}} by the calibrated margin">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="has review threshold band" subject="%S" object="%RTB" weight="1"/>
    <condition rel="has materiality band" subject="%S" object="%MBD" weight="1"/>
    <condition rel="band has rank" subject="%RTB" object="%RTR" weight="1"/>
    <condition rel="band has rank" subject="%MBD" object="%MBR" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="review precision margin ranks" subject="%P" object="%MARGIN" weight="1"/>
    <condition expression="%MBR - %RTR" value="%GAP" weight="1"
               alt="Measures how many bands the review threshold sits below the materiality band"/>
    <condition expression="%GAP is greater than or equal to %MARGIN" weight="1"
               alt="The gap of {{%GAP}} bands meets the calibrated margin of {{%MARGIN}}"/>
    <condition expression="'Review precision adequate on the investigation threshold. A review threshold set at or near financial statement materiality has less precision and a greater risk of failing to prevent or detect a misstatement, PCAOB Staff Audit Practice Alert 11 page 21. The threshold here sits below the materiality band at issue by the calibrated margin. The margin itself is a calibration parameter expressed in bands: the alert states the direction of the test and no public source located in this build states a numeric fraction of materiality.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B6a B10 - the review investigation threshold is not far enough below materiality (PCAOB Practice Alert 11 p 21, practice margin)"
           alt="The review threshold at band {{%RTB}} does not sit far enough below the materiality band {{%MBD}} to be precise enough">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="has review threshold band" subject="%S" object="%RTB" weight="1"/>
    <condition rel="has materiality band" subject="%S" object="%MBD" weight="1"/>
    <condition rel="band has rank" subject="%RTB" object="%RTR" weight="1"/>
    <condition rel="band has rank" subject="%MBD" object="%MBR" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="review precision margin ranks" subject="%P" object="%MARGIN" weight="1"/>
    <condition expression="%MBR - %RTR" value="%GAP2" weight="1"
               alt="Measures how many bands the review threshold sits below the materiality band"/>
    <condition expression="%GAP2 is less than %MARGIN" weight="1"
               alt="The gap of {{%GAP2}} bands falls short of the calibrated margin of {{%MARGIN}}"/>
    <condition expression="'Review precision insufficient on the investigation threshold. A threshold at or near financial statement materiality has less precision and a greater risk of failing to prevent or detect a misstatement, PCAOB Staff Audit Practice Alert 11 page 21. The threshold recorded here does not sit below the materiality band at issue by the calibrated margin, so the review could pass a misstatement that matters. The margin is a calibration parameter in bands, because the alert gives the direction of the test and no public source located in this build gives a figure.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B6b B10 - a sign off alone is little or no evidence of review effectiveness (PCAOB Practice Alert 11 p 20)"
           alt="The only evidence of performance is a signature, which on its own says little about whether the review worked">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="test evidenced only by sign off" subject="%S" object="true" weight="1"/>
    <condition expression="'Evidence limited to a sign off. Verifying that the reviewer signed off provides little or no evidence by itself of the effectiveness of the control, PCAOB Staff Audit Practice Alert 11 page 20. A review control is evidenced by what the reviewer did with what the review surfaced, not by the signature at the end of it.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B6c B10 - a budget comparison review over a complex account may not be precise enough alone (PCAOB Practice Alert 11 p 25)"
           alt="The control is a budget or forecast comparison over a complex or less predictable account, where one review may not be precise enough on its own">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="is budget comparison review" subject="%S" object="true" weight="1"/>
    <condition rel="account is complex or unpredictable" subject="%S" object="true" weight="1"/>
    <condition expression="'Precision of a budget comparison over a complex account. Where the account or disclosure is complex or less predictable, a review comparing actual results against budget or forecast may not be sufficiently precise on its own, and a combination of controls may be needed to address the risk, PCAOB Staff Audit Practice Alert 11 page 25. The alert is permissive, so this is reported for the bank s judgement and is not treated here as a design deficiency on its own.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Second Line Controls Function" cf="100"
           name="[CORE] B6c G5 - whether one review suffices over a complex account is a judgement (PCAOB Practice Alert 11 p 25)"
           alt="Names the role that should own the judgement on whether a single budget comparison is precise enough for a complex account">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="is budget comparison review" subject="%S" object="true" weight="1"/>
    <condition rel="account is complex or unpredictable" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B7 B10 - the review does not address the assessed assertion level risk (PCAOB Practice Alert 11 pp 21 to 22)"
           alt="The review is not recorded as addressing the assessed risk at the assertion level">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc addresses assertion level risk" subject="%S" object="false" weight="1"/>
    <condition expression="'Missing review design item: the review does not address the assessed risk at the assertion level. The design of a management review control is evaluated first on whether it addresses that risk, PCAOB Staff Audit Practice Alert 11 pages 21 to 22. A review that does not reach the assertion at risk cannot meet the objective it is relied on for.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B7 B10 - the review precision factors are not documented (PCAOB Practice Alert 11 pp 20 to 22)"
           alt="The level of aggregation and the predictability of what is reviewed are not documented">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc precision factors documented" subject="%S" object="false" weight="1"/>
    <condition expression="'Missing review design item: the precision factors are not documented. A review at a granular level is more precise than a review over a company wide total, and the predictability of the expectations used bears on precision too, PCAOB Staff Audit Practice Alert 11 pages 20 to 22. Without the level of aggregation and the predictability recorded, the precision of the review cannot be assessed.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B7 B10 - the steps to identify investigate and resolve differences are not documented (PCAOB Practice Alert 11 pp 21 to 22)"
           alt="The steps the reviewer takes to identify, investigate and resolve significant differences are not documented">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc investigation steps documented" subject="%S" object="false" weight="1"/>
    <condition expression="'Missing review design item: the steps to identify, investigate and resolve significant differences. The design evaluation of a management review control covers those steps expressly, PCAOB Staff Audit Practice Alert 11 pages 21 to 22. A review that surfaces a difference but prescribes nothing to do about it does not meet its objective.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B7 B3a B10 - the reviewer has no authority to act on what the review finds (PCAOB Practice Alert 11 pp 21 to 22 and AS 2201 para A3)"
           alt="The reviewer is not recorded as having the authority to act on what the review finds">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc performer authority attested" subject="%S" object="false" weight="1"/>
    <condition expression="'Missing review design item: the reviewer s authority. The design evaluation covers the performer s competence and authority, PCAOB Staff Audit Practice Alert 11 pages 21 to 22, and a control performed by a person who lacks the necessary authority or competence is a deficiency in its own right, AS 2201 paragraph A3. A reviewer who cannot act on what the review finds cannot discharge the control.'" value="%O"/>
  </relinst>
  <relinst type="has design finding" cf="100"
           name="[CORE] B7 B10 - the information used in the review is not identified (PCAOB Practice Alert 11 pp 21 to 22)"
           alt="The information the review uses is not identified, including whether it is system generated">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc information source identified" subject="%S" object="false" weight="1"/>
    <condition expression="'Missing review design item: the information used in the review is not identified. The design evaluation covers the information used, including whether it is system generated, PCAOB Staff Audit Practice Alert 11 pages 21 to 22. Where the review runs on a report produced inside the bank, the completeness and accuracy of that report is itself part of what has to hold.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] B7a - no evidence of the steps the reviewer performed (PCAOB Practice Alert 11 p 23)"
           alt="The test evidence does not show the steps the reviewer performed to identify and investigate significant differences">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc evidence of steps performed" subject="%S" object="false" weight="1"/>
    <condition expression="'Insufficient review evidence: the steps performed. Operating effectiveness of a management review control requires evidence of the steps the reviewer performed to identify and investigate significant differences, PCAOB Staff Audit Practice Alert 11 page 23. Without it the review cannot be shown to have operated, whatever the outcome of the period looked like.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] B7a - no evidence of the conclusions the reviewer reached (PCAOB Practice Alert 11 p 23)"
           alt="The test evidence does not show the conclusions the reviewer reached or the corrective action taken">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="mrc evidence of conclusions reached" subject="%S" object="false" weight="1"/>
    <condition expression="'Insufficient review evidence: the conclusions reached. Operating effectiveness of a management review control also requires evidence of the conclusions the reviewer reached, including whether potential misstatements were investigated and corrective action taken, PCAOB Staff Audit Practice Alert 11 page 23. Evidence of the steps without the conclusions does not establish that the review worked.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] B6 B7a - the follow up of identified outliers is not documented (PCAOB Practice Alert 11 pp 23 and 25)"
           alt="The follow up of items the review identified as outliers is not documented">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition rel="follow up of outliers documented" subject="%S" object="false" weight="1"/>
    <condition expression="'Insufficient review evidence: the follow up of outliers. Where a review identifies an item as an outlier, what was done about it is part of the evidence that the control operated, PCAOB Staff Audit Practice Alert 11 pages 23 and 25. An undocumented follow up leaves the most informative part of the review untested.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="The Second Line Controls Function" cf="100"
           name="[CORE] B6 G5 - the precision of a management review control is a judgement taken as an input (PCAOB Practice Alert 11 pp 20 to 21)"
           alt="Names the role that should own the precision judgement for a management review control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] B6 G5 - statement of which precision factors are judged outside the graph (PCAOB Practice Alert 11 pp 20 to 21)"
           alt="Names the precision factors the graph takes as supplied rather than evaluating itself">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is management review control" subject="%S" object="true" weight="1"/>
    <condition expression="'Judgements taken as inputs for this review control. Precision turns on six factors, PCAOB Staff Audit Practice Alert 11 pages 20 to 21: the objective of the review, the level of aggregation, the consistency of performance, the correlation to the relevant assertion, the predictability of the expectations used, and the criteria for investigation. This graph tests the criteria for investigation against the materiality bands and takes the other five as answered by the assessor, because reading a review and judging its aggregation or predictability is not something a fact about the control can settle.'" value="%O"/>
  </relinst>
  <relinst type="has design candidate" object="No Design Determination" cf="100"
           name="[CORE] B8 R4 - candidate no design determination where the record is internally inconsistent (AS 2201 paras B28 and 39 to 41)"
           alt="An input inconsistency has been found, so no design determination can be reached on this record">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is greater than or equal to 1" weight="1"
               alt="At least one inconsistency has been found in the control record itself"/>
  </relinst>
  <relinst type="has design candidate" object="Design Deficient" cf="100"
           name="[CORE] B3 - candidate design deficient where a design finding exists (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="At least one design finding has been raised, so design deficient is a candidate conclusion">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has design finding',*) is greater than or equal to 1" weight="1"
               alt="At least one design finding has been raised for this control"/>
  </relinst>
  <relinst type="has design candidate" object="Design Effective" cf="100"
           name="[CORE] B3 B9 - candidate design effective where every required attribute is established (AS 2201 paras 42 and 43)"
           alt="Every required design attribute is positively established and nothing is missing, so design effective is a candidate conclusion">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="required attribute count" subject="%P" object="%RAC" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has attribute clearance',*)" value="%CLR" weight="1"
               alt="Counts the design attributes positively established for this control"/>
    <condition expression="%CLR is greater than or equal to %RAC" weight="1"
               alt="All {{%RAC}} required design attributes are established"/>
    <condition expression="countRelationshipInstances(%S,'has missing attribute',*) is equal to 0" weight="1"
               alt="No required design attribute is missing"/>
    <condition rel="addresses risk" subject="%S" object="%RK" weight="1"/>
    <condition rel="addresses the stated risk" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has design assessment" object="No Design Determination" cf="100"
           name="[CORE] B8 R4 - no design determination governs an inconsistent record (AS 2201 paras B28 and 39 to 41)"
           alt="The record is internally inconsistent, which outranks every substantive design conclusion">
    <condition rel="has design candidate" subject="%S" object="No Design Determination"/>
  </relinst>
  <relinst type="has design assessment" object="Design Deficient" cf="100"
           name="[CORE] B3 - design deficient governs where no inconsistency outranks it (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="A design finding stands and the record is internally consistent, so the control is design deficient">
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is equal to 0" weight="1"
               alt="No inconsistency has been found in the control record itself"/>
    <condition rel="has design candidate" subject="%S" object="Design Deficient"/>
  </relinst>
  <relinst type="has design assessment" object="Design Effective" cf="100"
           name="[CORE] B3 B9 - design effective governs only where nothing outranks it (AS 2201 paras 42 and 43)"
           alt="Every required attribute is established, no design finding of substance stands and the record is consistent, so the design is effective">
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is equal to 0" weight="1"
               alt="No inconsistency has been found in the control record itself"/>
    <condition expression="countRelationshipInstances(%S,'has missing attribute',*) is equal to 0" weight="1"
               alt="No required design attribute is missing"/>
    <condition rel="has design candidate" subject="%S" object="Design Effective"/>
  </relinst>
  <relinst type="has design assessment" object="No Design Determination" cf="100"
           name="[CORE] B9 G6 - no design determination where no candidate could be derived (AS 2201 para 42)"
           alt="No design candidate could be derived from the facts supplied, so no determination is published">
    <condition rel="is a control under assessment" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has design candidate',*) is equal to 0" weight="1"
               alt="No design candidate could be derived from the facts supplied"/>
  </relinst>
  <relinst type="has deficiency trigger" object="Design Deficiency" cf="100"
           name="[CORE] D1 - a design failure gives rise to a deficiency for severity evaluation (AS 2201 paras A3 and 62)"
           alt="A design failure has been found, which is a deficiency to be evaluated for severity">
    <condition rel="has design candidate" subject="%S" object="Design Deficient"/>
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is equal to 0" weight="1"
               alt="No inconsistency has been found in the control record itself"/>
  </relinst>
  <relinst type="has design reason" cf="100"
           name="[CORE] B3 G3 - reason for a design deficient conclusion (AS 2201 para A3 and SEC Release 33-8810 fn 29)"
           alt="Explains the design deficient conclusion and counts the attributes that were not established">
    <condition rel="has design assessment" subject="%S" object="Design Deficient"/>
    <condition expression="countRelationshipInstances(%S,'has missing attribute',*)" value="%MISS" weight="1"
               alt="Counts the required design attributes that are not established"/>
    <condition expression="'Design deficient. A design deficiency exists where a necessary control is missing, or where an existing control is so designed that the control objective would not be met even if the control operated as designed, AS 2201 paragraph A3 and SEC Release 33-8810 footnote 29. Required design attributes not established: ' + %MISS + '. Each one is named separately in the findings, together with any classification correction. Less evidence is needed to reach this conclusion than to reach a favourable one, paragraph 47 Note.'" value="%O"/>
  </relinst>
  <relinst type="has design reason" cf="100"
           name="[CORE] B3 B9 G3 - reason for a design effective conclusion (AS 2201 paras 42 43 and 47)"
           alt="Explains what the design effective conclusion rests on and what it does not say">
    <condition rel="has design assessment" subject="%S" object="Design Effective"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="required attribute count" subject="%P" object="%RAC2" weight="1"/>
    <condition expression="'Design effective. All ' + %RAC2 + ' required design attributes are positively established, the control is recorded as addressing the risk it is mapped to, and no design finding of substance stands against it. The test applied is whether the control, if operated as prescribed by a person with the necessary authority and competence, would satisfy the control objective and could prevent or detect a material misstatement on a timely basis, AS 2201 paragraph 42. A walkthrough of inquiry, observation and inspection is ordinarily sufficient for this conclusion and re-performance is not required, paragraph 43. The conclusion says nothing about whether the control actually operated.'" value="%O"/>
  </relinst>
  <relinst type="has design reason" cf="100"
           name="[CORE] B8 R4 G3 - reason no design determination was reached on an inconsistent record (AS 2201 paras B28 and 39 to 41)"
           alt="Explains that an inconsistent record outranks every substantive conclusion and what has to be corrected">
    <condition rel="has design assessment" subject="%S" object="No Design Determination"/>
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is greater than or equal to 1" weight="1"
               alt="At least one inconsistency has been found in the control record itself"/>
    <condition expression="'No design determination. The control record contains an internal inconsistency, described in the findings above. A record that cannot be true of one control under the standard s own taxonomy is a data quality problem, not a judgement for this graph to resolve, so no determination is published either way. Correct the record and run the assessment again.'" value="%O"/>
  </relinst>
  <relinst type="has design reason" cf="100"
           name="[CORE] G6 - reason no design determination was reached for want of facts (AS 2201 para 42)"
           alt="Explains that the facts supplied were not enough to reach any design candidate, and points to the open questions">
    <condition rel="has design assessment" subject="%S" object="No Design Determination"/>
    <condition expression="countRelationshipInstances(%S,'has design record inconsistency',*) is equal to 0" weight="1"
               alt="No inconsistency has been found in the control record itself"/>
    <condition expression="countRelationshipInstances(%S,'has design candidate',*) is equal to 0" weight="1"
               alt="No design candidate could be derived from the facts supplied"/>
    <condition expression="'No design determination. The facts supplied do not reach either conclusion. A favourable conclusion requires every required design attribute to be positively established, AS 2201 paragraph 42, and an unanswered question is not a pass. The open questions listed with this result name what is still needed.'" value="%O"/>
  </relinst>
  <relinst type="has suppressed candidate" cf="100"
           name="[CORE] G3 - a design deficient candidate suppressed by an inconsistent record is still reported (AS 2201 para A3)"
           alt="Reports that a design failure was found even though the governing conclusion is that no determination can be reached">
    <condition rel="has design assessment" subject="%S" object="No Design Determination"/>
    <condition rel="has design candidate" subject="%S" object="Design Deficient" weight="1"/>
    <condition expression="'Suppressed candidate: design deficient. The design findings above would independently make this control design deficient, AS 2201 paragraph A3. They are not published as the determination because the record also contains an internal inconsistency, which outranks every substantive conclusion. Correcting the record will not make the design findings go away.'" value="%O"/>
  </relinst>
  <relinst type="has design summary" cf="100"
           name="[CORE] G7 - plain language summary of a design deficient conclusion (AS 2201 para A3)"
           alt="Gives a control owner the design deficient outcome in plain words with the count of gaps">
    <condition rel="has design assessment" subject="%S" object="Design Deficient"/>
    <condition expression="countRelationshipInstances(%S,'has missing attribute',*)" value="%M2" weight="1"
               alt="Counts the required design attributes that are not established"/>
    <condition expression="'In plain terms: as written, this control would not do its job even if everyone followed it exactly. Number of things a control needs in order to work that the description does not establish: ' + %M2 + '. The findings name each one. Fix the description first, then test the control; testing a control that is not properly designed cannot show it works.'" value="%O"/>
  </relinst>
  <relinst type="has design summary" cf="100"
           name="[CORE] G7 - plain language summary of a design effective conclusion (AS 2201 paras 42 and 43)"
           alt="Gives a control owner the design effective outcome in plain words and says what it does not cover">
    <condition rel="has design assessment" subject="%S" object="Design Effective"/>
    <condition expression="'In plain terms: as written, this control would do its job if it were followed exactly as described. Everything a control needs in order to work is recorded: who performs it, how often, when, what they do, what it leaves behind and how precisely it operates. This says nothing about whether it was actually performed during the year. That is the next question.'" value="%O"/>
  </relinst>
  <relinst type="has design summary" cf="100"
           name="[CORE] G7 - plain language summary where no design determination was reached (AS 2201 para 42)"
           alt="Tells a control owner in plain words that no design answer is available and what to do about it">
    <condition rel="has design assessment" subject="%S" object="No Design Determination"/>
    <condition expression="'In plain terms: no answer is available yet. Either the record describes something that cannot be true of one control, or key details are missing. Nothing has been found against the control and nothing has been found in its favour. The findings and open questions above say exactly what to correct or supply. Run the assessment again once the record is fixed.'" value="%O"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[CORE] G1 - the design determination on the umbrella surface (AS 2201 paras 42 and A3)"
           alt="Puts the design assessment {{%DA}} on the single relationship a caller can ask on a control">
    <condition rel="has design assessment" subject="%S" object="%DA"/>
    <condition expression="'Control design assessment: ' + %DA + '. This is decision point one and it rests on the control record alone, with no test evidence.'" value="%O"/>
  </relinst>
  <relinst type="has effective control type" cf="100"
           name="[CORE] B4 C2 - a confirmed control type is the effective type for extent purposes (AS 2201 paras 39 to 41 and para B28)"
           alt="The recorded control type was confirmed, so it is the type the extent of testing is set from">
    <condition rel="has confirmed control type" subject="%S" object="%O"/>
  </relinst>
  <relinst type="has effective control type" cf="100"
           name="[CORE] B4 C2 - a corrected control type is the effective type for extent purposes (AS 2201 paras 39 to 41 and para B28)"
           alt="The recorded control type was corrected, so the corrected type is the one the extent of testing is set from">
    <condition rel="has corrected control type" subject="%S" object="%O"/>
  </relinst>
  <relinst type="uses frequency based extent" object="true" cf="100"
           name="[CORE] C2 - a manual control is sampled on frequency and risk (AS 2201 paras 46 and 54)"
           alt="The control is manual, so the extent of testing is set from how often it operates and the risk associated with it">
    <condition rel="has effective control type" subject="%S" object="Manual"/>
  </relinst>
  <relinst type="uses frequency based extent" object="true" cf="100"
           name="[CORE] C2 - an IT dependent manual control is sampled on frequency and risk (AS 2201 paras 46 54 and B28)"
           alt="The control is IT dependent manual, so a person performs it and the extent of testing is set from frequency and risk">
    <condition rel="has effective control type" subject="%S" object="IT Dependent Manual"/>
  </relinst>
  <relinst type="uses automated single instance extent" object="true" cf="100"
           name="[CORE] C3f I2a - an automated control over effective and currently tested general IT controls takes the automated extent (AS 2201 para B28, practice calibration)"
           alt="The control is entirely automated and the general IT controls over it are effective and tested in the current period, so the automated extent applies">
    <condition rel="has effective control type" subject="%S" object="Automated"/>
    <condition rel="has itgc conclusion" subject="%S" object="Effective" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="uses automated fallback extent" object="true" cf="100"
           name="[CORE] C3f C20 - an automated control over deficient general IT controls falls back to the manual extent (AS 2201 para B29 b, practice calibration)"
           alt="The control is automated but the general IT controls over it are deficient, so the automated extent is unavailable and the manual extent with a floor applies">
    <condition rel="has effective control type" subject="%S" object="Automated"/>
    <condition rel="has itgc conclusion" subject="%S" object="Deficient" weight="1"/>
  </relinst>
  <relinst type="uses automated fallback extent" object="true" cf="100"
           name="[CORE] C3f C20 - an automated control over untested general IT controls falls back to the manual extent (AS 2201 para B29 b, practice calibration)"
           alt="The control is automated but the general IT controls over it have not been tested, so the automated extent is unavailable and the manual extent with a floor applies">
    <condition rel="has effective control type" subject="%S" object="Automated"/>
    <condition rel="has itgc conclusion" subject="%S" object="Not Tested" weight="1"/>
  </relinst>
  <relinst type="uses automated fallback extent" object="true" cf="100"
           name="[CORE] C3f C19 - an automated control with untested general IT controls falls back to the manual extent (AS 2201 para B29 c, practice)"
           alt="The general IT controls over this automated control were concluded effective but are not being tested in the current period, so the automated extent is unavailable">
    <condition rel="has effective control type" subject="%S" object="Automated"/>
    <condition rel="has itgc conclusion" subject="%S" object="Effective" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="sampling approach does not apply" object="true" cf="100"
           name="[CORE] C3a - a control leaving no documentary evidence of performance is not sampled (AS 2315 para 32)"
           alt="The control produces no evidence of its own performance, so there is no population of documented instances to sample">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="produces evidence" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="sampling approach does not apply" object="true" cf="100"
           name="[CORE] C3a - a control depending primarily on segregation of duties is not sampled (AS 2315 para 32)"
           alt="The control depends primarily on segregation of duties, which is a condition rather than a repeated operation, so a sampling approach does not apply">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="depends primarily on segregation of duties" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3a - statement that no sample size comparison is made (AS 2315 para 32)"
           alt="States that a sampling approach does not apply to this control and no sample size comparison was made">
    <condition rel="sampling approach does not apply" subject="%S" object="true"/>
    <condition expression="'No sample size comparison was made. A sampling approach applies to a defined population from which a representative selection can be drawn, AS 2315 paragraphs 17 and 23. It does not apply where the control leaves no documentary evidence of its performance, or where it depends primarily on segregation of duties, AS 2315 paragraph 32. Evidence of operating effectiveness for a control of this kind comes from observation and inquiry about the condition itself rather than from a sample, and the evidence sufficiency tests still apply in full.'" value="%O"/>
  </relinst>
  <relinst type="sample size comparison applies" object="true" cf="100"
           name="[CORE] C14 - the sample size comparison applies to a control tested by selection (AS 2315 paras 17 23 and 39)"
           alt="The control was tested by selecting items from a population, so the sample tested is compared with the size the frequency and risk require">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'sampling approach does not apply','true') is equal to 0" weight="1"
               alt="A sampling approach does apply to this control"/>
    <condition expression="countRelationshipInstances(%S,'has sampling method','Full Population') is equal to 0" weight="1"
               alt="The test was not a full population test"/>
    <condition expression="countRelationshipInstances(%S,'has sampling method','Sampling Not Applicable') is equal to 0" weight="1"
               alt="The tester did not record sampling as inapplicable to this control"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C14 - statement that a full population test needs no sample size comparison (AS 2315 paras 23 and 39)"
           alt="States that every item was examined, so no sampling risk arises and no sample size comparison is needed">
    <condition rel="has sampling method" subject="%S" object="Full Population"/>
    <condition expression="'Every item in the population was examined, so no sampling risk arises and no sample size comparison applies. A sample is tested so that a conclusion may be drawn about the population it was drawn from, AS 2315 paragraphs 23 and 39; where the population itself is tested there is nothing to extrapolate. The population completeness test still matters, because a full population test of an incomplete population is not a full population test.'" value="%O"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C2 C3 - the frequency and risk table figure for a control sampled on frequency (AS 2201 paras 46 and 54, practice table)"
           alt="Reads the required size for this control's frequency and risk from the calibrated sample size table">
    <condition rel="uses frequency based extent" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="has frequency" subject="%S" object="%F" weight="1"/>
    <condition rel="has risk level" subject="%S" object="%RL" weight="1"/>
    <condition rel="has sample size row" subject="%P" object="%ROW" weight="1"/>
    <condition rel="row frequency" subject="%ROW" object="%F" weight="1"/>
    <condition rel="row risk level" subject="%ROW" object="%RL" weight="1"/>
    <condition rel="row sample size" subject="%ROW" object="%O" weight="1"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C3f - the frequency and risk table figure also applies on the automated fallback route (AS 2201 para B29, practice table)"
           alt="The automated extent is unavailable, so the manual frequency and risk figure is offered as a candidate">
    <condition rel="uses automated fallback extent" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="has frequency" subject="%S" object="%F" weight="1"/>
    <condition rel="has risk level" subject="%S" object="%RL" weight="1"/>
    <condition rel="has sample size row" subject="%P" object="%ROW" weight="1"/>
    <condition rel="row frequency" subject="%ROW" object="%F" weight="1"/>
    <condition rel="row risk level" subject="%ROW" object="%RL" weight="1"/>
    <condition rel="row sample size" subject="%ROW" object="%O" weight="1"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C3f - the automated fallback floor applies where the automated extent is unavailable (AS 2201 para B29, practice floor)"
           alt="Reads the calibrated floor that applies to an automated control whose general IT controls cannot be relied on">
    <condition rel="uses automated fallback extent" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="automated fallback sample floor" subject="%P" object="%O" weight="1"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C3f I2a - the automated extent where the general IT controls can be relied on (AS 2201 para B28, practice calibration)"
           alt="Reads the calibrated automated extent for a control whose general IT controls are effective and currently tested">
    <condition rel="uses automated single instance extent" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="automated control sample size" subject="%P" object="%O" weight="1"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C3g I2c - several performers or sites are several populations each sampled (AS 2315 paras 17 and 31 d, practice split)"
           alt="The control is performed by {{%PC}} separate performers sites or systems, so the per population figure is multiplied across them">
    <condition rel="uses frequency based extent" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P"/>
    <condition rel="has performer population count" subject="%S" object="%PC" weight="1"/>
    <condition expression="%PC is greater than or equal to 2" weight="1"
               alt="The control is performed by two or more separate performers sites or systems"/>
    <condition rel="has frequency" subject="%S" object="%F" weight="1"/>
    <condition rel="has risk level" subject="%S" object="%RL" weight="1"/>
    <condition rel="has sample size row" subject="%P" object="%ROW" weight="1"/>
    <condition rel="row frequency" subject="%ROW" object="%F" weight="1"/>
    <condition rel="row risk level" subject="%ROW" object="%RL" weight="1"/>
    <condition rel="row sample size" subject="%ROW" object="%SZ" weight="1"/>
    <condition expression="%SZ * %PC" value="%O" weight="1"
               alt="Multiplies the per population figure of {{%SZ}} across {{%PC}} populations"/>
  </relinst>
  <relinst type="has required sample size candidate" cf="100"
           name="[CORE] C31 - a dual purpose test takes the larger of the two purposes required sizes (AS 2315 para 44)"
           alt="The test also served a substantive purpose, so the substantive required size is offered as a candidate alongside the control testing figure">
    <condition rel="test served dual purpose" subject="%S" object="true"/>
    <condition rel="dual purpose required size" subject="%S" object="%O" weight="1"/>
  </relinst>
  <relinst type="has dual purpose finding" cf="100"
           name="[CORE] C31 - statement that a dual purpose test is valid evidence of operating effectiveness (AS 2315 para 44)"
           alt="States that serving a substantive purpose does not reduce the standing of the test as evidence of operating effectiveness">
    <condition rel="test served dual purpose" subject="%S" object="true"/>
    <condition expression="'Dual purpose test accepted. A sample may be designed for two purposes at once, testing the operating effectiveness of a control and testing whether the recorded transactions are correct, AS 2315 paragraph 44. The test is not discounted for having served both purposes. The size required is the larger of the two purposes figures, and the substantive figure is supplied as an input because it is computed outside this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has required sample size" cf="100"
           name="[CORE] C2 C3h - the governing required size is the largest candidate and the figures are floors (AS 2201 para 54, practice rounding)"
           alt="Takes the largest of the required size candidates, because a published figure is a floor and not a target">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has required sample size candidate',*) is greater than or equal to 1" weight="1"
               alt="At least one required size candidate has been derived for this control"/>
    <condition expression="maxObjects(%S,'has required sample size candidate',*)" value="%O" weight="1"
               alt="The largest required size candidate governs"/>
  </relinst>
  <relinst type="extent of testing sufficient" object="true" cf="100"
           name="[CORE] C2 C4 - the sample tested meets the required size (AS 2201 para 54 and AS 2315 para 38)"
           alt="The sample tested of {{%ST}} instances meets the required size of {{%RS}}, so the extent of testing is sufficient">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition rel="has required sample size" subject="%S" object="%RS" weight="1"/>
    <condition rel="has sample size tested" subject="%S" object="%ST" weight="1"/>
    <condition expression="%ST is greater than or equal to %RS" weight="1"
               alt="The number of instances tested meets or exceeds the required size"/>
  </relinst>
  <relinst type="extent of testing sufficient" object="false" cf="100"
           name="[CORE] C4 - a sample smaller than the required size is not sufficient extent (AS 2201 para 54 and AS 2315 para 38)"
           alt="The sample tested of {{%ST2}} instances falls short of the required size of {{%RS2}}, so the extent of testing is not sufficient">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition rel="has required sample size" subject="%S" object="%RS2" weight="1"/>
    <condition rel="has sample size tested" subject="%S" object="%ST2" weight="1"/>
    <condition expression="%ST2 is less than %RS2" weight="1"
               alt="The number of instances tested falls short of the required size"/>
  </relinst>
  <relinst type="extent of testing sufficient" object="true" cf="100"
           name="[CORE] C3a - extent is not in issue where a sampling approach does not apply (AS 2315 para 32)"
           alt="A sampling approach does not apply to this control, so the extent of testing is not a ground for withholding a conclusion">
    <condition rel="sampling approach does not apply" subject="%S" object="true"/>
  </relinst>
  <relinst type="extent of testing sufficient" object="true" cf="100"
           name="[CORE] C14 - extent is not in issue where the whole population was tested (AS 2315 paras 23 and 39)"
           alt="Every item in the population was examined, so the extent of testing is sufficient by definition">
    <condition rel="has sampling method" subject="%S" object="Full Population"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition rel="has population size" subject="%S" object="%FPS" weight="1"/>
    <condition expression="%FPS is greater than or equal to 1" weight="1"
               alt="The population of {{%FPS}} instances contains at least one instance to examine"/>
  </relinst>
  <relinst type="extent of testing sufficient" object="false" cf="100"
           name="[CORE] C14 C4 - a full population test of an empty population is not sufficient extent (AS 2315 paras 23 and 39)"
           alt="The population recorded for this control is empty, so no instance of the control was examined and the extent of testing is not sufficient">
    <condition rel="has sampling method" subject="%S" object="Full Population"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition rel="has population size" subject="%S" object="%FPS2" weight="1"/>
    <condition expression="%FPS2 is less than 1" weight="1"
               alt="The population recorded for this control contains no instances at all"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C14 C4 - statement that an empty population supports no conclusion (AS 2315 paras 23 and 39)"
           alt="States that the population recorded is empty, so no conclusion about the operation of the control can rest on this test">
    <condition rel="has sampling method" subject="%S" object="Full Population"/>
    <condition rel="has population size" subject="%S" object="%FPS3" weight="1"/>
    <condition expression="%FPS3 is less than 1" weight="1"
               alt="The population recorded for this control contains no instances at all"/>
    <condition expression="'The population recorded for this control is empty. A test is performed so that a conclusion may be drawn about the population from which the items were selected, AS 2315 paragraphs 23 and 39; where there were no instances at all, every item was examined only in the vacuous sense and nothing is learned about how the control operated. Either the control did not operate in the period, which is itself a matter to evaluate, or the population figure is wrong.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3 C25 - statement of the required and tested sizes and the basis of the figure (AS 2201 para 54, practice table)"
           alt="States the required size, the number tested, and that the figure is a calibrated practice parameter rather than a figure from a standard">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition rel="has required sample size" subject="%S" object="%RSB" weight="1"/>
    <condition rel="has sample size tested" subject="%S" object="%STB" weight="1"/>
    <condition expression="'Extent of testing: ' + %STB + ' instances tested against a required size of ' + %RSB + '. The standards set the direction and not the number. Evidence needed increases as the risk associated with the control increases, AS 2201 paragraph 46; the more frequently a control operates the more operations should be tested, paragraph 54; and sample size rises as the tolerable deviation rate falls and the expected rate rises, AS 2315 paragraph 38. No primary source consulted states a sample size, so the figure above comes from the calibrated practice table, which is a parameter of this assessment and not a requirement of any standard.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C4 - statement that a short sample is insufficient evidence rather than a control failure (AS 2201 para 54)"
           alt="States that a sample short of the required size is a shortfall in the test and not a finding against the control">
    <condition rel="extent of testing sufficient" subject="%S" object="false"/>
    <condition rel="has required sample size" subject="%S" object="%RSS" weight="1"/>
    <condition expression="'The sample tested is smaller than the required size of ' + %RSS + '. This is a shortfall in the test and not a finding against the control: nothing adverse has been established about the control itself. Test the remaining instances and assess again. A conclusion on operating effectiveness drawn from a sample below the required extent would not be supported, AS 2201 paragraph 54.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3f I2a - statement of the automated extent and what it depends on (AS 2201 para B28, practice calibration)"
           alt="States that the reduced automated extent was applied and that it rests on the general IT controls">
    <condition rel="uses automated single instance extent" subject="%S" object="true"/>
    <condition expression="'Automated extent applied. An entirely automated control operates the same way every time and is not subject to breakdown through human failure, which is the reasoning AS 2201 paragraph B28 gives for treating such a control differently. The reduced extent therefore rests entirely on the general IT controls over program changes, access to programs and computer operations being effective and tested in the current period. If that conclusion changes, this extent is withdrawn and the manual figure applies. The reduced figure itself is a practice calibration and appears in no standard.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3f C20 - statement that the automated extent was withdrawn and the manual figure applied (AS 2201 para B29)"
           alt="States that the general IT controls could not carry the reduced automated extent, so the manual figure with a floor applies">
    <condition rel="uses automated fallback extent" subject="%S" object="true"/>
    <condition expression="'Automated extent unavailable. The reduced extent for an automated control depends on the general IT controls over it being effective and tested in the current period, AS 2201 paragraph B29. That condition is not met here, so the control is tested at the manual frequency and risk figure subject to a calibrated floor, and the larger of the two governs. Both figures are practice calibrations.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3g I2c - statement of the multi population split (AS 2315 paras 17 and 31 d, practice split)"
           alt="States that the control was treated as several populations and how many">
    <condition rel="has performer population count" subject="%S" object="%PCB"/>
    <condition expression="%PCB is greater than or equal to 2" weight="1"
               alt="The control is performed by two or more separate performers sites or systems"/>
    <condition expression="'Multi population split applied across ' + %PCB + ' performers, sites or systems. A sample is drawn so that it may be expected to be representative of the population it comes from, AS 2315 paragraph 17, and the characteristics of the population are a factor in determining the sample, paragraph 31 d. Several performers of one control are several populations on that reasoning, but no primary source consulted prescribes the split, so treating each as a separate population is a practice calibration and switchable.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] I36 - statement that the table figures assume no expected deviations (AS 2315 para 38, practice basis)"
           alt="States the expected deviation rate the calibrated figures assume, so an institution expecting deviations knows to raise the figure">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition rel="has required sample size" subject="%S" object="%RSE" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%PE" weight="1"/>
    <condition rel="expected deviation rate percent" subject="%PE" object="%EDR" weight="1"/>
    <condition expression="'The required size assumes an expected deviation rate of ' + %EDR + ' per cent. Sample size rises as the expected deviation rate rises, AS 2315 paragraph 38, so where deviations are expected the figure must be raised rather than the published figure accepted. The expected rate is a parameter of this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C5 - frequency must be known before an extent can be set (AS 2201 para 54 and para 42)"
           alt="No frequency has been supplied, so no required extent exists and no sufficiency conclusion can be formed">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has frequency',*) is equal to 0" weight="1"
               alt="No frequency has been recorded for this control"/>
    <condition expression="'How often is the control performed. The extent of testing depends on it - the more frequently a control operates, the more operations should be tested, AS 2201 paragraph 54 - so with frequency unknown there is no required extent to compare the sample against and no conclusion on operating effectiveness is available. Frequency is also one of the six design attributes, paragraph 42.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C2 - the risk associated with the control must be known before an extent can be set (AS 2201 para 46)"
           alt="No risk level has been supplied, so the required extent cannot be read from the table">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has risk level',*) is equal to 0" weight="1"
               alt="No risk level has been recorded for this control"/>
    <condition expression="'What is the risk associated with the control. The evidence needed increases as the risk associated with the control increases, AS 2201 paragraph 46, so the required extent cannot be set without it. This is a judgement the bank makes in its risk assessment, which sits outside this assessment, and it is taken here as an input.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C4 - how many instances were tested must be known before extent can be judged (AS 2201 para 54)"
           alt="No number of instances tested has been supplied, so the extent of testing cannot be judged either way">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has sample size tested',*) is equal to 0" weight="1"
               alt="No number of instances tested has been recorded for this control"/>
    <condition expression="'How many instances of the control were tested. Without it the extent of testing cannot be compared with the required size, and an untested extent is not a sufficient one. Nothing adverse is implied about the control by this question.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C2 B4 - the control type must be resolved before an extent route can be chosen (AS 2201 paras 39 to 41 and para B28)"
           alt="The control type has not been resolved, so no extent route applies and no required size can be derived">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has effective control type',*) is equal to 0" weight="1"
               alt="No control type has been resolved for this control"/>
    <condition expression="'Is the control manual, automated or IT dependent manual, and does it rely on an application. The extent of testing differs by type - an entirely automated control is treated differently because it is not subject to breakdown through human failure, AS 2201 paragraph B28 - so no required extent can be derived until the type is resolved.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C3f C20 - the general IT control conclusion is needed before an automated extent can be set (AS 2201 para B29 b and c)"
           alt="The control is automated but no conclusion on the general IT controls has been supplied, so neither automated route can be chosen">
    <condition rel="has effective control type" subject="%S" object="Automated"/>
    <condition expression="countRelationshipInstances(%S,'has itgc conclusion',*) is equal to 0" weight="1"
               alt="No conclusion on the general IT controls has been recorded for this automated control"/>
    <condition expression="'What is the conclusion on the general IT controls over the application this automated control runs in, and are they being tested in the current period. The reduced extent for an automated control depends on both, AS 2201 paragraph B29, so without them the extent cannot be set and the control cannot be concluded on.'" value="%O"/>
  </relinst>
  <relinst type="has sample size basis" cf="100"
           name="[CORE] C3d - statement that a deviation is not a misstatement (AS 2315 para 35)"
           alt="States that the deviation counts in this assessment are not misstatement conclusions">
    <condition rel="sample size comparison applies" subject="%S" object="true"/>
    <condition expression="'Note on what the figures mean. A deviation found in a sample is not a misstatement. Deviations increase the risk of misstatement but do not necessarily produce one, and ordinarily produce misstatements at a lower rate than the deviation rate itself, AS 2315 paragraph 35. Nothing in this assessment converts an exception count into a conclusion about the financial statements.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Retained" cf="100"
           name="[CORE] C13 - evidence of performance was retained (SEC Release 33-8810 II A 1 e and II A 2 c)"
           alt="Evidence of the performance of the tested instances was retained, so there is support for a conclusion">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence retained" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C13 - no evidence of performance was retained (SEC Release 33-8810 II A 1 e and II A 2 c)"
           alt="No evidence of performance was retained, so no conclusion on operating effectiveness is available either way">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence retained" subject="%S" object="false" weight="1"/>
    <condition expression="'Evidence not retained. Evidential matter, including documentation, must be maintained to provide reasonable support for the assessment, SEC Release 33-8810 sections II A 1 e and II A 2 c. With no retained evidence there is no support, so no conclusion on operating effectiveness is available - not effective, and equally not ineffective. This is insufficient evidence regardless of what the sample results say, because an unsupported favourable result is not a result.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Procedures Above Inquiry Only" cf="100"
           name="[CORE] C1b - observation takes the test above inquiry alone (AS 2201 para 50 and Note)"
           alt="The test included observing the control being performed, so it rises above inquiry alone">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="test includes observation" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Procedures Above Inquiry Only" cf="100"
           name="[CORE] C1b - inspection of documentation takes the test above inquiry alone (AS 2201 para 50 and Note)"
           alt="The test included inspection of documentation, so it rises above inquiry alone">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="test includes inspection" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Procedures Above Inquiry Only" cf="100"
           name="[CORE] C1b - re-performance takes the test above inquiry alone (AS 2201 para 50 and Note)"
           alt="The test included re-performance of the control, so it rises above inquiry alone">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="test includes reperformance" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C1b I17 - the test was inquiry alone which is never sufficient (AS 2201 para 50 and Note)"
           alt="The only procedure performed was inquiry, which does not by itself provide sufficient evidence of operating effectiveness">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="evidence floor requires more than inquiry" subject="%P" object="true" weight="1"/>
    <condition rel="test includes inquiry" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has sufficiency clearance','Procedures Above Inquiry Only') is equal to 0" weight="1"
               alt="No procedure above inquiry was performed in this test"/>
    <condition expression="'Inquiry alone. Inquiry alone does not provide sufficient evidence to support a conclusion about the effectiveness of a control, AS 2201 paragraph 50 Note. The hierarchy runs inquiry, then observation, then inspection of relevant documentation, then re-performance, and the evidence obtained rises as the test moves up it. Perform at least one procedure above inquiry and assess again. Note the divergence recorded in the calibration guide: the SEC management guidance is more permissive than the auditor standard here, and this assessment applies the auditor standard as its conservative default.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] I22 - statement of the evidence hierarchy expected at this risk level (AS 2201 para 50, practice tiering)"
           alt="States which procedures practice expects at this control's risk level, while the sourced floor remains more than inquiry alone">
    <condition rel="has risk level" subject="%S" object="High"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'test includes reperformance','true') is equal to 0" weight="1"
               alt="The test of this high risk control did not include re-performance"/>
    <condition expression="'Practice note on the evidence tier. The risk associated with this control is recorded as high, and practice expects re-performance at that level; the test performed did not include it. The sourced requirement is only that the test rise above inquiry alone, AS 2201 paragraph 50, so this is a practice observation and not a finding against the control. The risk tiering is a parameter of this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] I22 - statement of the evidence hierarchy expected at a medium risk level (AS 2201 para 50, practice tiering)"
           alt="States that practice expects inspection of documentation at a moderate risk level, while the sourced floor remains more than inquiry alone">
    <condition rel="has risk level" subject="%S" object="Medium"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'test includes inspection','true') is equal to 0" weight="1"
               alt="The test of this medium risk control did not include inspection of documentation"/>
    <condition expression="'Practice note on the evidence tier. The risk associated with this control is recorded as medium, and practice expects inspection of relevant documentation at that level; the test performed did not include it. The sourced requirement is only that the test rise above inquiry alone, AS 2201 paragraph 50, so this is a practice observation and not a finding against the control. The risk tiering is a parameter of this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] I22 - statement of the evidence hierarchy expected at a low risk level (AS 2201 para 50, practice tiering)"
           alt="States that practice expects observation or inquiry combined with inspection at a low risk level, while the sourced floor remains more than inquiry alone">
    <condition rel="has risk level" subject="%S" object="Low"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'test includes inspection','true') is equal to 0" weight="1"
               alt="The test of this low risk control did not include inspection of documentation"/>
    <condition expression="'Practice note on the evidence tier. The risk associated with this control is recorded as low, and practice expects observation or inquiry combined with inspection at that level; the test performed did not include inspection. The sourced requirement is only that the test rise above inquiry alone, AS 2201 paragraph 50, so this is a practice observation and not a finding against the control. The risk tiering is a parameter of this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Shows What Was Done" cf="100"
           name="[CORE] C12 - the evidence shows what the performer actually did (SEC Release 33-8810 II A 1 e and II A 2 c)"
           alt="The retained evidence shows what the performer actually did, not merely that the control was signed off">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence shows what was done" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 - the evidence does not show what the performer did (SEC Release 33-8810 II A 2 c and PCAOB Practice Alert 11 p 20)"
           alt="The retained evidence does not show what the performer actually did, so it does not support a conclusion about how the control operated">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence shows what was done" subject="%S" object="false" weight="1"/>
    <condition expression="'The evidence does not show what was done. The documentation obligation covers the methods and procedures applied and the basis for the conclusion reached, SEC Release 33-8810 section II A 2 c, and evidence recording only that someone signed evidences very little about how the control operated - a point PCAOB Staff Audit Practice Alert 11 page 20 records as an inspection finding. Evidence of the steps performed is needed, not only of completion.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 - evidence consisting only of a signature or sign off (PCAOB Practice Alert 11 p 20)"
           alt="The only evidence of performance is a signature, which does not show what the performer did">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="test evidenced only by sign off" subject="%S" object="true" weight="1"/>
    <condition expression="'Sign off only. The sole evidence of performance is a signature or initials. A sign off records that someone accepted the output; it does not record what they examined, what they compared it against, what differences they found or what they did about them. On that evidence the operation of the control cannot be evaluated, PCAOB Staff Audit Practice Alert 11 page 20. This is a shortfall in the evidence rather than proof the control failed.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Performer Independent Of Preparer" cf="100"
           name="[CORE] C12 - the performer is independent of the preparer (SEC Release 33-8810 II A 2 fn 40 and II A 2 b)"
           alt="The person performing the control is independent of the person who prepared what is being controlled">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="performer independent of preparer" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 I24 - the performer is not independent of the preparer (SEC Release 33-8810 II A 2 fn 40 and II A 2 b)"
           alt="The person performing the control also prepared what is being controlled, which is a self review">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="performer independent of preparer" subject="%S" object="false" weight="1"/>
    <condition expression="'Performer not independent of the preparer. The same person prepared the item and performed the control over it, so the control is a self review. The objectivity of the person who performs an evaluation affects how much the evidence it produces can be relied on, SEC Release 33-8810 section II A 2 and its footnote 40. The direction is sourced; the particular separation required here is a practice calibration of this assessment, and it is reported as a sufficiency finding rather than treated as an automatic failure of the control.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Shows Performer" cf="100"
           name="[CORE] C12 I29 - the evidence shows who performed the control (practice calibration, parameter evidence practice legs)"
           alt="The retained evidence identifies who performed the control">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence shows performer" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Shows Performer" cf="100"
           name="[CORE] C12 I29 - the performer leg does not apply where the practice legs are switched off (practice calibration, parameter evidence practice legs)"
           alt="The institution has switched off the practice evidence legs, so this test is cleared as not applicable">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P2" weight="1"/>
    <condition rel="evidence practice legs required" subject="%P2" object="false" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 I29 - the evidence does not show who performed the control (practice calibration, parameter evidence practice legs)"
           alt="The retained evidence does not identify who performed the control, which is a practice test and not a sourced requirement">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P3" weight="1"/>
    <condition rel="evidence practice legs required" subject="%P3" object="true" weight="1"/>
    <condition rel="evidence shows performer" subject="%S" object="false" weight="1"/>
    <condition expression="'The evidence does not identify the performer. Operating effectiveness includes whether the person performing the control has the necessary authority and competence, and that cannot be assessed where the evidence does not say who performed it. Stated plainly: no primary source located in this build requires the performer to be recorded on the evidence. This is a practice test, it ships on by default, and an institution may switch it off without changing any rule.'" value="%O"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Dated Within Period" cf="100"
           name="[CORE] C12 I29 - the evidence is dated within the period under review (practice calibration, parameter evidence practice legs)"
           alt="The retained evidence is dated within the period under assessment">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="evidence dated within period" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has sufficiency clearance" object="Evidence Dated Within Period" cf="100"
           name="[CORE] C12 I29 - the dating leg does not apply where the practice legs are switched off (practice calibration, parameter evidence practice legs)"
           alt="The institution has switched off the practice evidence legs, so the dating test is cleared as not applicable">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P4" weight="1"/>
    <condition rel="evidence practice legs required" subject="%P4" object="false" weight="1"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 I29 - the evidence is not dated within the period under review (practice calibration, parameter evidence practice legs)"
           alt="The retained evidence is not dated within the period under assessment, which is a practice test and not a sourced requirement">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P5" weight="1"/>
    <condition rel="evidence practice legs required" subject="%P5" object="true" weight="1"/>
    <condition rel="evidence dated within period" subject="%S" object="false" weight="1"/>
    <condition expression="'The evidence is not dated within the period under review. Evidence of a performance outside the period does not evidence the control operating during the period, which is what the conclusion is about. Stated plainly: no primary source located in this build requires the test date to be recorded. This is a practice test, it ships on by default, and an institution may switch it off without changing any rule.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C1c - an interim test needs evidence for the remaining period to reach the period end (SEC Release 33-8810 II A 2 b)"
           alt="The test was performed at an interim date, so evidence covering the remaining period is needed before a period end conclusion can be reached">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has interim test date" subject="%S" object="%IT" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition expression="'Interim evidence. The evidence should ordinarily cover a reasonable period of time that includes the period end, SEC Release 33-8810 section II A 2 b, because the conclusion being supported is a conclusion as at the period end. This test was performed at an interim date, so the further evidence needed for the remaining period must be determined, AS 2201 paragraphs 55 and 56. The roll forward assessment reported with this result states which further procedure applies.'" value="%O"/>
  </relinst>
  <relinst type="has sampling method finding" cf="100"
           name="[CORE] C14 I30 - the sampling method sits at or above the calibrated minimum rank (AS 2315 paras 17 23 and 39, practice ranking)"
           alt="The selection method used ranks at or above the minimum this assessment is calibrated to accept">
    <condition rel="has sampling method" subject="%S" object="%SM"/>
    <condition rel="applies testing policy" subject="%S" object="%P6" weight="1"/>
    <condition rel="sampling method has rank" subject="%SM" object="%MR" weight="1"/>
    <condition rel="minimum sampling method rank" subject="%P6" object="%MIN" weight="1"/>
    <condition expression="%MR is greater than or equal to %MIN" weight="1"
               alt="The method rank of {{%MR}} meets the calibrated minimum of {{%MIN}}"/>
    <condition expression="'Selection method accepted. A sample must be expected to be representative of the population it is drawn from so that a conclusion may reasonably be drawn about that population, AS 2315 paragraphs 17, 23 and 39. The standards require a representative selection but rank no method against another, so the ranking applied here is a practice calibration of this assessment and the method is reported rather than refused.'" value="%O"/>
  </relinst>
  <relinst type="has sampling method finding" cf="100"
           name="[CORE] C14 I30 - the sampling method falls below the calibrated minimum rank (AS 2315 paras 17 23 and 39, practice ranking)"
           alt="The selection method used ranks below the minimum this assessment is calibrated to accept">
    <condition rel="has sampling method" subject="%S" object="%SM2"/>
    <condition rel="applies testing policy" subject="%S" object="%P7" weight="1"/>
    <condition rel="sampling method has rank" subject="%SM2" object="%MR2" weight="1"/>
    <condition rel="minimum sampling method rank" subject="%P7" object="%MIN2" weight="1"/>
    <condition expression="%MR2 is less than %MIN2" weight="1"
               alt="The method rank of {{%MR2}} falls below the calibrated minimum of {{%MIN2}}"/>
    <condition expression="'Selection method below the calibrated minimum. The requirement the sources state is that the sample be expected to be representative of the population, AS 2315 paragraphs 17 and 23; no source located in this build bars any particular selection method outright. The method is therefore reported as a finding whose weight the institution decides through its own parameter, and it never produces an adverse determination on its own.'" value="%O"/>
  </relinst>
  <relinst type="has sampling method finding" cf="100"
           name="[CORE] C14 I30 - a judgemental selection with no recorded rationale (AS 2315 paras 17 and 31 d, practice calibration)"
           alt="The selection was judgemental and the rationale for it is not recorded, so its representativeness cannot be assessed">
    <condition rel="has sampling method" subject="%S" object="Judgemental"/>
    <condition rel="sampling rationale recorded" subject="%S" object="false" weight="1"/>
    <condition expression="'Judgemental selection with no recorded rationale. Where items are selected by judgement rather than by a method that gives every item a chance of selection, the basis of the judgement is what shows the sample could be expected to be representative, AS 2315 paragraphs 17 and 31 d. With no rationale recorded that cannot be assessed. Recording the basis is a practice calibration of this assessment and not a requirement stated in the sources.'" value="%O"/>
  </relinst>
  <relinst type="has sampling method finding" cf="100"
           name="[CORE] C3g - population completeness was not established before the sample was drawn (AS 2315 paras 17 and 31 d)"
           alt="The completeness of the population was not established before the sample was drawn, so the sample cannot be known to be representative">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="population completeness established" subject="%S" object="false" weight="1"/>
    <condition expression="'Population completeness not established. A sample is drawn so that it may be expected to be representative of the population, AS 2315 paragraph 17, and the characteristics of the population are a factor in determining the sample, paragraph 31 d. If the population from which the sample was drawn was not known to be complete, the sample cannot be known to be representative of the real population and the extent of testing cannot be relied on. Establish completeness first, then select.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C3b - selected items that could not be tested are counted as deviations (AS 2315 para 40)"
           alt="{{%UIC}} selected items could not be tested, and such items are counted as deviations rather than dropped from the sample">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has untestable item count" subject="%S" object="%UIC" weight="1"/>
    <condition expression="%UIC is greater than or equal to 1" weight="1"
               alt="At least one selected item could not be tested"/>
    <condition expression="'Untestable items in the sample: ' + %UIC + '. Where neither the planned procedure nor a suitable alternative procedure can be applied to a selected item, that item is ordinarily counted as a deviation, AS 2315 paragraph 40. Such items are never quietly dropped from the sample and replaced, because dropping them would change the population the conclusion rests on. They are included in the exception figures reported with this result.'" value="%O"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C3c - a combination of controls is treated as a single procedure for deviation counting (AS 2315 para 36)"
           alt="This record describes a combination of controls achieving one objective, so a deviation from any one of them counts as a deviation">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="is combination of controls" subject="%S" object="true" weight="1"/>
    <condition expression="'Combination of controls. Where two or more controls are necessary together to achieve one control objective, they are treated as a single control procedure and a deviation from any one of them is a deviation from the whole, AS 2315 paragraph 36. The exception figures reported with this result are counted on that basis, so an instance where one limb was performed and another was not counts once as a deviation and not as a partial pass.'" value="%O"/>
  </relinst>
  <relinst type="evidence is sufficient" object="true" cf="100"
           name="[CORE] C12 - evidence is sufficient where every required sufficiency test cleared (AS 2201 para 50 and SEC Release 33-8810 II A 2)"
           alt="All {{%RSTC}} required sufficiency tests returned an explicit pass, so the evidence supports a conclusion">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P8" weight="1"/>
    <condition rel="required sufficiency test count" subject="%P8" object="%RSTC" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has sufficiency clearance',*)" value="%CLEARED" weight="1"
               alt="Counts the sufficiency tests that returned an explicit pass"/>
    <condition expression="%CLEARED is greater than or equal to %RSTC" weight="1"
               alt="Every required sufficiency test has returned an explicit pass"/>
  </relinst>
  <relinst type="evidence is sufficient" object="false" cf="100"
           name="[CORE] C12 C13 - evidence is not sufficient where a required sufficiency test did not clear (AS 2201 para 50 and SEC Release 33-8810 II A 2)"
           alt="Only {{%CLEARED2}} of the {{%RSTC2}} required sufficiency tests returned an explicit pass, so the evidence does not support a conclusion">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%P9" weight="1"/>
    <condition rel="required sufficiency test count" subject="%P9" object="%RSTC2" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has sufficiency clearance',*)" value="%CLEARED2" weight="1"
               alt="Counts the sufficiency tests that returned an explicit pass"/>
    <condition expression="%CLEARED2 is less than %RSTC2" weight="1"
               alt="At least one required sufficiency test did not return an explicit pass"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] C12 C25 - statement of how many sufficiency tests cleared (AS 2201 para 50 and SEC Release 33-8810 II A 2)"
           alt="States in numbers how many of the required sufficiency tests the evidence passed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="applies testing policy" subject="%S" object="%PA" weight="1"/>
    <condition rel="required sufficiency test count" subject="%PA" object="%RSTC3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has sufficiency clearance',*)" value="%CLEARED3" weight="1"
               alt="Counts the sufficiency tests that returned an explicit pass"/>
    <condition expression="'Evidence sufficiency: ' + %CLEARED3 + ' of ' + %RSTC3 + ' tests passed. The six tests are that evidence of performance was retained, that the test rose above inquiry alone, that the evidence shows what the performer did, that the performer was independent of the preparer, that the evidence identifies the performer and that it is dated within the period. The first four rest on the standards and the SEC guidance; the last two are practice tests of this assessment and are labelled as such wherever they are reported. Each test not passed is named separately above.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C13 G6 - whether evidence was retained is needed before any conclusion (SEC Release 33-8810 II A 1 e)"
           alt="No answer has been given on whether evidence of performance was retained, and without it no conclusion is available">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'evidence retained',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether evidence of performance was retained"/>
    <condition expression="'Was evidence of performance retained for the instances tested. Evidential matter must be maintained to provide reasonable support for the assessment, SEC Release 33-8810 section II A 1 e, so with this unanswered no conclusion on operating effectiveness is available. An unanswered question is not a pass.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C1b G6 - which procedures the test comprised is needed before any conclusion (AS 2201 para 50)"
           alt="No test procedure has been recorded, so it cannot be established that the test rose above inquiry alone">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'test includes inquiry',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether the test included inquiry"/>
    <condition expression="countRelationshipInstances(%S,'has sufficiency clearance','Procedures Above Inquiry Only') is equal to 0" weight="1"
               alt="No procedure above inquiry has been recorded for this test"/>
    <condition expression="'Which procedures did the test comprise - inquiry, observation, inspection of documentation, re-performance. Inquiry alone never provides sufficient evidence of operating effectiveness, AS 2201 paragraph 50 Note, so the procedures performed must be known before the evidence can be judged sufficient.'" value="%O"/>
  </relinst>
  <relinst type="has effective exception count" cf="100"
           name="[CORE] C3b - untestable selected items are added to the exception count (AS 2315 paras 40 and 41)"
           alt="Adds the {{%UIC}} untestable selected items to the {{%EC}} exceptions found, because an untestable item counts as a deviation">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has exception count" subject="%S" object="%EC" weight="1"/>
    <condition rel="has untestable item count" subject="%S" object="%UIC" weight="1"/>
    <condition expression="%UIC is greater than or equal to 1" weight="1"
               alt="At least one selected item could not be tested"/>
    <condition expression="%EC + %UIC" value="%O" weight="1"
               alt="The effective exception count is the exceptions found plus the untestable items"/>
  </relinst>
  <relinst type="has effective exception count" cf="100"
           name="[CORE] C10 - the exception count stands where every selected item was testable (AS 2315 para 41)"
           alt="Every selected item could be tested, so the effective exception count is the {{%EC2}} exceptions reported">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has exception count" subject="%S" object="%EC2"/>
    <condition expression="countRelationshipInstances(%S,'has untestable item count',*) is equal to 0" weight="1"
               alt="No untestable items have been recorded for this control"/>
    <condition expression="%EC2" value="%O" weight="1"
               alt="The effective exception count is the exceptions reported"/>
  </relinst>
  <relinst type="has effective exception count" cf="100"
           name="[CORE] C3b - a recorded zero untestable items leaves the exception count unchanged (AS 2315 para 40)"
           alt="No selected item was untestable, so the effective exception count is the {{%EC3}} exceptions reported">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has exception count" subject="%S" object="%EC3"/>
    <condition rel="has untestable item count" subject="%S" object="%UIZ" weight="1"/>
    <condition expression="%UIZ is equal to 0" weight="1"
               alt="The recorded count of untestable items is zero"/>
    <condition expression="%EC3" value="%O" weight="1"
               alt="The effective exception count is the exceptions reported"/>
  </relinst>
  <relinst type="has deviation rate percent" cf="100"
           name="[CORE] C10a - the sample deviation rate is the best estimate of the population rate (AS 2315 para 41)"
           alt="Computes the deviation rate as {{%EEC}} deviations in {{%ST}} items tested">
    <condition rel="has effective exception count" subject="%S" object="%EEC"/>
    <condition rel="has sample size tested" subject="%S" object="%ST" weight="1"/>
    <condition expression="%ST is greater than or equal to 1" weight="1"
               alt="At least one instance of the control was tested"/>
    <condition expression="%EEC / %ST" value="%FRACTION" weight="1"
               alt="Divides the deviations by the items tested"/>
    <condition expression="%FRACTION * 100" value="%O" weight="1"
               alt="Expresses the deviation rate as a percentage"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C10a C25 - statement of the deviation rate and what it is compared against (AS 2315 paras 34 38 and 41)"
           alt="States the deviation rate found and the tolerable rate it is compared with">
    <condition rel="has deviation rate percent" subject="%S" object="%DR"/>
    <condition rel="applies testing policy" subject="%S" object="%P" weight="1"/>
    <condition rel="tolerable deviation rate percent" subject="%P" object="%TDR" weight="1"/>
    <condition expression="'Deviation rate: ' + %DR + ' per cent against a tolerable rate of ' + %TDR + ' per cent. The comparison is made on the rate and not on a raw count, because the deviation rate in the sample is the best estimate of the deviation rate in the population, AS 2315 paragraph 41, and the sample size itself is set against a tolerable rate rather than a tolerable number, paragraphs 34 and 38. The tolerable rate is a parameter of this assessment: AS 2315 paragraph 34 speaks of five per cent or possibly less where a low control risk is assessed, and ten per cent or more where assurance comes from other tests, but the figure applied is a calibration and not a requirement.'" value="%O"/>
  </relinst>
  <relinst type="has effective exception nature" cf="100"
           name="[CORE] C9 - a stated exception nature is taken as supplied (AS 2315 para 42)"
           alt="The nature of the exceptions is recorded as {{%EN}}, so it is taken as supplied">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="has exception nature" subject="%S" object="%EN" weight="1"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has exception nature','Unknown Nature') is equal to 0" weight="1"
               alt="The nature of the exceptions is not recorded as unknown"/>
    <condition expression="%EN" value="%O" weight="1"
               alt="The effective nature is the nature recorded"/>
  </relinst>
  <relinst type="has effective exception nature" object="Systemic" cf="100"
           name="[CORE] C9 I5 - an exception of unknown nature is treated as systemic (AS 2315 para 42, conservative default)"
           alt="The nature of the exceptions is unknown, and the conservative default treats an unknown nature as systemic">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="has exception nature" subject="%S" object="Unknown Nature" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P2" weight="1"/>
    <condition rel="unknown exception nature treated as systemic" subject="%P2" object="true" weight="1"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C9 I5 - statement that the unknown nature default was applied (AS 2315 para 42, conservative default)"
           alt="States that the nature of the exception is unknown and that the conservative default was applied">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="has exception nature" subject="%S" object="Unknown Nature" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P3" weight="1"/>
    <condition rel="unknown exception nature treated as systemic" subject="%P3" object="true" weight="1"/>
    <condition expression="'Exception of unknown nature treated as systemic. The qualitative aspects of a deviation, including its nature and its cause, must be considered, AS 2315 paragraph 42, so an unknown cause cannot be resolved in the control s favour: an exception that might be systemic is treated as systemic until the cause is established. This is a conservative default of this assessment and it is exposed as a parameter. Establishing the root cause may change the determination, and that is the work to do next.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C9 - the root cause of the exceptions has not been established (AS 2315 para 42)"
           alt="The root cause of the exceptions has not been established, so their nature cannot be assessed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has effective exception count" subject="%S" object="%EEC2" weight="1"/>
    <condition expression="%EEC2 is greater than or equal to 1" weight="1"
               alt="At least one exception was found"/>
    <condition rel="root cause identified" subject="%S" object="false" weight="1"/>
    <condition expression="'Root cause not established. Whether a deviation is isolated or systemic turns on its cause, and the cause has not been established. The nature and cause of a deviation are qualitative aspects that must be considered, AS 2315 paragraph 42. Until the cause is known the exception cannot be shown to be isolated, which is why the conservative treatment applies. Establishing the cause is also what makes a remediation plan meaningful.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C11 - a deviation classed as a control failure (AS 2315 paras 35 and 42)"
           alt="The deviation is classed as a control failure, so the control did not operate on the instances concerned">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="has deviation class" subject="%S" object="Control Failure" weight="1"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="'Deviation class: control failure. The control did not operate as designed on the instances concerned. Note what this does not mean: a deviation is not itself a misstatement, and deviations ordinarily produce misstatements at a lower rate than the deviation rate itself, AS 2315 paragraph 35. The likelihood and magnitude of what could have gone undetected are judgements taken as inputs to the severity evaluation, not conclusions this assessment reaches from the count.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C11 - a deviation classed as a documentation gap (AS 2315 paras 35 and 42 and ISA UK 330 para 17 a)"
           alt="The deviation is classed as a documentation gap, which is evaluated and never discarded">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="has deviation class" subject="%S" object="Documentation Gap" weight="1"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="'Deviation class: documentation gap. The control may have been performed but the evidence does not show it. The distinction between a documentation gap and a control failure is sourced - the nature and cause of a deviation must be considered, AS 2315 paragraphs 35 and 42, and specific inquiries are required to understand a deviation and its potential consequences - but what the distinction does to the conclusion is stated by neither text. This assessment therefore evaluates a documentation gap as a deviation like any other and never silently downgrades it. Where the gap means the operation cannot be verified, the evidence is insufficient on that instance.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C11 - the deviation class has not been recorded (AS 2315 para 42)"
           alt="Exceptions were found but their class was not recorded, so both readings remain open">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has effective exception count" subject="%S" object="%EEC3" weight="1"/>
    <condition expression="%EEC3 is greater than or equal to 1" weight="1"
               alt="At least one exception was found"/>
    <condition expression="countRelationshipInstances(%S,'has deviation class',*) is equal to 0" weight="1"
               alt="No deviation class has been recorded for the exceptions found"/>
    <condition expression="'Deviation class not recorded. Whether each deviation is a failure of the control or a gap in its documentation has not been stated, and the qualitative aspects of a deviation must be considered, AS 2315 paragraph 42. Both readings remain open and neither is assumed. The deviations are carried into the severity evaluation on their face.'" value="%O"/>
  </relinst>
  <relinst type="exception position clear" object="true" cf="100"
           name="[CORE] C6 - zero exceptions in the sample is a clear exception position (AS 2315 para 41)"
           alt="The effective exception count is zero, so no deviation stands against the control in this sample">
    <condition rel="has effective exception count" subject="%S" object="%ZC"/>
    <condition expression="%ZC is equal to 0" weight="1"
               alt="The effective exception count is zero"/>
  </relinst>
  <relinst type="exception position clear" object="false" cf="100"
           name="[CORE] C7 - one or more exceptions is not a clear exception position (AS 2201 para 48 and AS 2315 para 41)"
           alt="The effective exception count is {{%NZC}}, so the exception position is not clear">
    <condition rel="has effective exception count" subject="%S" object="%NZC"/>
    <condition expression="%NZC is greater than or equal to 1" weight="1"
               alt="At least one deviation stands against the control"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C7 C8 - a single exception is a deficiency pending evaluation and the sample is not extended (AS 2201 para 48, conservative default)"
           alt="One deviation was found, which is a deficiency to be evaluated rather than something to be cleared by testing more items">
    <condition rel="has effective exception count" subject="%S" object="%ONE"/>
    <condition expression="%ONE is equal to 1" weight="1"
               alt="Exactly one deviation stands against the control"/>
    <condition rel="applies testing policy" subject="%S" object="%P4" weight="1"/>
    <condition rel="sample extension permitted" subject="%P4" object="false" weight="1"/>
    <condition expression="'One exception found. It is a deficiency pending evaluation, and the sample is not extended to clear it. A deviation from a control means the testing approach must be reassessed rather than the result averaged away, AS 2201 paragraph 48, and no primary source located in this build permits enlarging a sample in order to dilute a deviation. This is the conservative default of this assessment and it is exposed as a parameter: the recorded disagreement is that one public practice source publishes an escalation ladder of larger samples while another calls that dilution the commonest error challenged on inspection. A sample may still be extended to establish how far a failure extends, which is a different purpose and is recorded as such.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C8 I21 - statement where the institution has switched sample extension on (AS 2201 para 48, parameter sample extension permitted)"
           alt="The institution has enabled sample extension, and the statement records what extension may and may not establish">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="applies testing policy" subject="%S" object="%P5" weight="1"/>
    <condition rel="sample extension permitted" subject="%P5" object="true" weight="1"/>
    <condition expression="'Sample extension is enabled in this institution s calibration. Note the limit on what an extension can establish: testing further items may show how far a failure extends, but it does not unmake the deviation already found, and a deviation requires the testing approach to be reassessed, AS 2201 paragraph 48. The deviations found are carried into the severity evaluation whatever the extended sample shows.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C10 C10a - the deviation rate exceeds the tolerable rate (AS 2315 paras 34 38 and 41)"
           alt="The deviation rate of {{%DR2}} per cent exceeds the tolerable rate of {{%TDR2}} per cent">
    <condition rel="has deviation rate percent" subject="%S" object="%DR2"/>
    <condition rel="applies testing policy" subject="%S" object="%P6" weight="1"/>
    <condition rel="tolerable deviation rate percent" subject="%P6" object="%TDR2" weight="1"/>
    <condition expression="%DR2 is greater than %TDR2" weight="1"
               alt="The observed deviation rate exceeds the tolerable rate"/>
    <condition expression="'The deviation rate exceeds the tolerable rate. The rate observed in the sample is the best estimate of the rate in the population, AS 2315 paragraph 41, so a rate above the tolerable rate means the control cannot be relied on to operate within the limits the test was designed around. The tolerable rate itself is a parameter of this assessment.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C10 - systemic exceptions mean the control cannot be relied on (AS 2315 paras 41 and 42)"
           alt="The exceptions are systemic, so they are expected to recur across the population rather than being confined to the instances tested">
    <condition rel="has effective exception nature" subject="%S" object="Systemic"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="'Systemic exceptions. A systemic deviation arises from the way the control operates rather than from the particular instances selected, so it is expected to recur across the population. The sample rate is the best estimate of the population rate, AS 2315 paragraph 41, and a systemic cause means the deviations found are not confined to the items tested. The control is not operating effectively on this evidence, whatever the arithmetic of the rate.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C10 - isolated exceptions are still evaluated (AS 2315 paras 35 41 and 42, AS 2201 para 48)"
           alt="The exceptions are recorded as isolated, which lightens neither the deficiency nor the reassessment the standard requires">
    <condition rel="has effective exception nature" subject="%S" object="Isolated"/>
    <condition rel="framework is bound" subject="%S" object="true" weight="1"/>
    <condition expression="'Exceptions recorded as isolated. An isolated deviation is still a deviation: it is a deficiency to be evaluated for severity, and it still requires the testing approach to be reassessed, AS 2201 paragraph 48. What isolated means is that the cause is confined to the instances found rather than inherent in how the control operates, which bears on the likelihood judgement in the severity evaluation. It does not make the deviation disappear.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] I35 - statement of the tolerable deviation basis at this sample size (AS 2315 para 38, practice calibration)"
           alt="States the sample size at which the calibration treats one deviation as within the tolerable rate">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="applies testing policy" subject="%S" object="%P7" weight="1"/>
    <condition rel="tolerable deviation sample threshold" subject="%P7" object="%TST" weight="1"/>
    <condition expression="'Basis of the rate arithmetic. This assessment is calibrated so that one deviation sits within the tolerable rate only at a sample of ' + %TST + ' items or more; below that size the tolerable position is zero deviations. AS 2315 paragraph 38 requires the deviation rate to be compared with the tolerable rate but states no figure, so this threshold is a practice calibration. It governs only the arithmetic reported above: by the conservative single exception default, one deviation is a deficiency pending evaluation whatever the rate shows.'" value="%O"/>
  </relinst>
  <relinst type="has exception finding" cf="100"
           name="[CORE] C3d - statement that no exception count is converted into a misstatement conclusion (AS 2315 para 35)"
           alt="States that the exception figures are not a conclusion about the financial statements">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition expression="'Note on what the exception figures mean. Deviations increase the risk of misstatement but do not necessarily produce one, and ordinarily produce misstatements at a lower rate than the deviation rate itself, AS 2315 paragraph 35. Nothing in this assessment converts an exception count into a conclusion that the financial statements are misstated. Whether anything was in fact misstated is a separate question answered by substantive work, not by this result.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency trigger" object="Operating Deficiency" cf="100"
           name="[CORE] D1 C7 - a deviation gives rise to a deficiency for severity evaluation (AS 2201 paras 48 62 and A3)"
           alt="At least one deviation stands against the control, which is a deficiency to be evaluated for severity">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C10 G6 - how many exceptions were found is needed before a conclusion (AS 2315 para 41)"
           alt="No exception count has been supplied, so no conclusion on operating effectiveness is available">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has exception count',*) is equal to 0" weight="1"
               alt="No exception count has been recorded for this control"/>
    <condition expression="'How many exceptions were found in the sample. The deviation rate in the sample is the estimate of the rate in the population, AS 2315 paragraph 41, so with the count unknown there is no rate to compare and no conclusion is available. Zero is an answer and must be recorded as one; an unanswered question is not zero.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C9 G6 - the nature of the exceptions is needed before severity can be judged (AS 2315 para 42)"
           alt="Exceptions were found but their nature has not been recorded, and the conservative default will apply until it is">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition expression="countRelationshipInstances(%S,'has exception nature',*) is equal to 0" weight="1"
               alt="No exception nature has been recorded for the deviations found"/>
    <condition expression="'What is the nature of the exceptions found - isolated, systemic, or not yet established. The qualitative aspects of a deviation, including its nature and cause, must be considered, AS 2315 paragraph 42. Until the nature is recorded the conservative treatment applies and the exceptions are taken as systemic, which is the least favourable reading. Establishing the cause may change the determination.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward gap months" cf="100"
           name="[CORE] C15 C17 - the roll forward gap is the months from the interim test date to the period end (AS 2201 para 56)"
           alt="Measures the length of the remaining period after the interim test, which is the third of the four roll forward factors">
    <condition rel="has interim test date" subject="%S" object="%IT"/>
    <condition rel="has period end" subject="%S" object="%PE" weight="1"/>
    <condition expression="isAfterDate(%IT,%PE) is equal to false" weight="1"
               alt="The interim test date {{%IT}} falls on or before the period end {{%PE}}"/>
    <condition expression="monthsBetween(%IT,%PE)" value="%O" weight="1"
               alt="Counts the months of the period that remain after the interim test"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C15 - the roll forward obligation and its four factors (AS 2201 paras 55 and 56)"
           alt="States the obligation to determine the further evidence needed for the remaining period, and names the four factors that govern it">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has roll forward gap months" subject="%S" object="%GAP"/>
    <condition expression="'Evidence was obtained at an interim date, so the further evidence needed for the remaining period must be determined, AS 2201 paragraph 55. The remaining period measured here is ' + %GAP + ' months. Four factors govern what is needed, paragraph 56: the specific control tested, including the risks associated with it and its nature, and the results of the interim test; the sufficiency of the evidence obtained at interim; the length of the remaining period; and whether there were significant changes in internal control after the interim date. Each of the four is reported separately below.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Inquiry" cf="100"
           name="[CORE] C15a - inquiry alone is a candidate roll forward procedure only on all four conditions (AS 2201 para 56 Note, practice calibration of the gap)"
           alt="The control is low risk, substantially all the evidence was obtained at interim with no exceptions, the remaining period is within the calibrated maximum and nothing changed, so inquiry alone is a candidate">
    <!-- The roll-forward gap is read FIRST, as the sibling candidate rules  -->
    <!-- below already do. It is derived, never askable, and exists only     -->
    <!-- where an interim test date was recorded, so leading on it prunes     -->
    <!-- the whole branch for a control tested at the period end - which     -->
    <!-- otherwise got asked whether substantially all its evidence was      -->
    <!-- obtained at an interim date it never had. AS 2201 paragraph 56 is   -->
    <!-- expressly about the period between an interim test and the period    -->
    <!-- end, so the gap is the precondition of the passage, not a detail     -->
    <!-- of it. Every limb below remains mandatory: the logic is unchanged.  -->
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has roll forward gap months" subject="%S" object="%GAP2" weight="1"/>
    <condition rel="has risk level" subject="%S" object="Low" weight="1"/>
    <condition rel="substantially all evidence at interim" subject="%S" object="true" weight="1"/>
    <condition rel="interim exceptions noted" subject="%S" object="false" weight="1"/>
    <condition rel="changes since interim" subject="%S" object="false" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P1" weight="1"/>
    <condition rel="maximum roll forward gap months" subject="%P1" object="%MAXG" weight="1"/>
    <condition expression="%GAP2 is less than or equal to %MAXG" weight="1"
               alt="The remaining period of {{%GAP2}} months is within the calibrated maximum of {{%MAXG}} months"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Limited Retest" cf="100"
           name="[CORE] C15b - a medium risk control needs more than inquiry over the remaining period (AS 2201 paras 46 and 56)"
           alt="The risk associated with the control is medium, so inquiry alone is not enough for the remaining period and a retest of some instances is a candidate">
    <condition rel="has roll forward gap months" subject="%S" object="%G3"/>
    <condition rel="has risk level" subject="%S" object="Medium" weight="1"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Limited Retest" cf="100"
           name="[CORE] C15b - a high risk control needs more than inquiry over the remaining period (AS 2201 paras 46 and 56)"
           alt="The risk associated with the control is high, so inquiry alone is not enough for the remaining period and a retest of some instances is a candidate">
    <condition rel="has roll forward gap months" subject="%S" object="%G4"/>
    <condition rel="has risk level" subject="%S" object="High" weight="1"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Limited Retest" cf="100"
           name="[CORE] C15b - thin interim evidence needs more than inquiry over the remaining period (AS 2201 para 56 b)"
           alt="Substantially all the evidence was not obtained at the interim date, so the sufficiency factor points away from inquiry alone">
    <condition rel="has roll forward gap months" subject="%S" object="%G5"/>
    <condition rel="substantially all evidence at interim" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Limited Retest" cf="100"
           name="[CORE] C15b - exceptions at interim need more than inquiry over the remaining period (AS 2201 paras 48 and 56 a)"
           alt="Exceptions were noted when the control was tested at interim, so the results of the interim test point away from inquiry alone">
    <condition rel="has roll forward gap months" subject="%S" object="%G6"/>
    <condition rel="interim exceptions noted" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Full Retest" cf="100"
           name="[CORE] C16 - a significant change after the interim date requires the control to be tested afresh (AS 2201 para 56 d)"
           alt="There were significant changes in the control or the controls around it after the interim test, so what was tested at interim is no longer what operates">
    <condition rel="has roll forward gap months" subject="%S" object="%G7"/>
    <condition rel="changes since interim" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has roll forward candidate" object="Full Retest" cf="100"
           name="[CORE] C16 C17 - a remaining period beyond the calibrated maximum requires the control to be tested afresh (AS 2201 para 56 c, practice calibration)"
           alt="The remaining period exceeds the calibrated maximum gap, so the interim evidence does not carry to the period end on its own">
    <condition rel="has roll forward gap months" subject="%S" object="%G8"/>
    <condition rel="applies testing policy" subject="%S" object="%P2" weight="1"/>
    <condition rel="maximum roll forward gap months" subject="%P2" object="%MAXG2" weight="1"/>
    <condition expression="%G8 is greater than %MAXG2" weight="1"
               alt="The remaining period of {{%G8}} months exceeds the calibrated maximum of {{%MAXG2}} months"/>
  </relinst>
  <relinst type="has roll forward candidate" object="No Further Procedure Required" cf="100"
           name="[CORE] C15 - no roll forward procedure is needed where no evidence was obtained at an interim date (AS 2201 para 55)"
           alt="A period end is recorded and no interim test date is, so the testing was not interim and paragraph 55 does not engage">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="has period end" subject="%S" object="%PE2" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has interim test date',*) is equal to 0" weight="1"
               alt="No interim test date is recorded for this control"/>
  </relinst>
  <relinst type="has roll forward requirement" object="Full Retest" cf="100"
           name="[CORE] C16 - a full retest governs where any fresh test trigger applies (AS 2201 para 56)"
           alt="A change after the interim date or a remaining period beyond the calibrated maximum outranks every lighter procedure">
    <condition rel="has roll forward candidate" subject="%S" object="Full Retest"/>
  </relinst>
  <relinst type="has roll forward requirement" object="Limited Retest" cf="100"
           name="[CORE] C15b - a limited retest governs where no fresh test trigger outranks it (AS 2201 paras 46 and 56)"
           alt="Some instances must be retested over the remaining period and no fresh test trigger applies">
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Full Retest') is equal to 0" weight="1"
               alt="No fresh test trigger applies to this control"/>
    <condition rel="has roll forward candidate" subject="%S" object="Limited Retest"/>
  </relinst>
  <relinst type="has roll forward requirement" object="Inquiry" cf="100"
           name="[CORE] C15a - inquiry alone governs only where nothing heavier outranks it (AS 2201 para 56 Note)"
           alt="All four conditions for inquiry alone are met and neither a retest trigger nor a fresh test trigger applies">
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Full Retest') is equal to 0" weight="1"
               alt="No fresh test trigger applies to this control"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Limited Retest') is equal to 0" weight="1"
               alt="No ground for retesting instances over the remaining period applies"/>
    <condition rel="has roll forward candidate" subject="%S" object="Inquiry"/>
  </relinst>
  <relinst type="has roll forward requirement" object="No Further Procedure Required" cf="100"
           name="[CORE] C15 - no further procedure governs where there was no interim test (AS 2201 para 55)"
           alt="There was no interim test, so no procedure is owed for a remaining period and nothing heavier can apply">
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Full Retest') is equal to 0" weight="1"
               alt="No fresh test trigger applies to this control"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Limited Retest') is equal to 0" weight="1"
               alt="No ground for retesting instances over the remaining period applies"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Inquiry') is equal to 0" weight="1"
               alt="The conditions for inquiry alone do not apply"/>
    <condition rel="has roll forward candidate" subject="%S" object="No Further Procedure Required"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C16a - roll forward sufficiency may not be inferred from the absence of misstatements (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="Sufficiency over the remaining period has been inferred from substantive work, which neither framework permits">
    <condition rel="roll forward sufficiency inferred from substantive work" subject="%S" object="true"/>
    <condition expression="'Sufficiency over the remaining period has been inferred from the absence of misstatements found by substantive procedures. Neither framework permits that inference. The absence of misstatements detected by substantive procedures does not provide evidence that the controls related to the assertion tested are effective, AS 2201 paragraph B9 and ISA UK 330 paragraph 16. The control must be tested directly over the remaining period. This assessment therefore treats the roll forward as unsatisfied however clean the substantive work was.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C16a - standing note that the remaining period must be covered by testing the control itself (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="States for every interim test that the remaining period has to be covered by evidence about the control and not by substantive results">
    <condition rel="has roll forward gap months" subject="%S" object="%G9"/>
    <condition expression="'Note on what will not cover the remaining period. Whatever procedure is required below has to be evidence about the control itself. Clean substantive results over the remaining months are not a substitute: the absence of misstatements detected by substantive procedures does not provide evidence that the related controls are effective, AS 2201 paragraph B9 and ISA UK 330 paragraph 16. Nor does the absence of complaints, incidents or audit findings, for the same reason.'" value="%O"/>
  </relinst>
  <relinst type="substantive inference position" object="true" cf="100"
           name="[CORE] C16a - a stated reliance on substantive results is taken as supplied (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="The institution has recorded that roll forward sufficiency rests on the absence of misstatements found by substantive work">
    <condition rel="roll forward sufficiency inferred from substantive work" subject="%S" object="true"/>
  </relinst>
  <relinst type="substantive inference position" object="false" cf="100"
           name="[CORE] C16a - a stated absence of reliance on substantive results is taken as supplied (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="The institution has recorded that roll forward sufficiency does not rest on substantive results">
    <condition rel="roll forward sufficiency inferred from substantive work" subject="%S" object="false"/>
  </relinst>
  <relinst type="substantive inference position" object="false" cf="100"
           name="[CORE] C16a - absent any statement no reliance on substantive results is assumed (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="Nothing was supplied about reliance on substantive results, so the assessment proceeds on the basis that none was claimed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'roll forward sufficiency inferred from substantive work',*) is equal to 0" weight="1"
               alt="Nothing has been supplied about whether sufficiency rests on substantive results"/>
  </relinst>
  <relinst type="roll forward sufficient" object="true" cf="100"
           name="[CORE] C15 - the roll forward is satisfied where no procedure is owed (AS 2201 para 55)"
           alt="No evidence was obtained at an interim date, so there is no remaining period to cover and nothing is outstanding">
    <condition rel="has roll forward requirement" subject="%S" object="No Further Procedure Required"/>
  </relinst>
  <relinst type="roll forward sufficient" object="true" cf="100"
           name="[CORE] C15a - the roll forward is satisfied where inquiry alone is enough and inquiry was performed (AS 2201 para 56 Note)"
           alt="Inquiry alone is enough for this control and remaining period, and roll forward work was performed">
    <condition rel="has roll forward requirement" subject="%S" object="Inquiry"/>
    <condition rel="roll forward performed" subject="%S" object="true" weight="1"/>
    <condition rel="substantive inference position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="true" cf="100"
           name="[CORE] C15b C17 C16d - the roll forward is satisfied where a limited retest was required and instances were retested (AS 2201 para 56 and ISA UK 330 para A35)"
           alt="A retest of instances over the remaining period was required and work beyond inquiry was performed on at least the calibrated minimum number of instances">
    <condition rel="has roll forward requirement" subject="%S" object="Limited Retest"/>
    <condition rel="roll forward performed" subject="%S" object="true" weight="1"/>
    <condition rel="roll forward procedure was inquiry only" subject="%S" object="false" weight="1"/>
    <condition rel="roll forward sample size" subject="%S" object="%RFS" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P3" weight="1"/>
    <condition rel="minimum roll forward sample size" subject="%P3" object="%MINRF" weight="1"/>
    <condition expression="%RFS is greater than or equal to %MINRF" weight="1"
               alt="The {{%RFS}} instances retested meet the calibrated minimum of {{%MINRF}}"/>
    <condition rel="substantive inference position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="true" cf="100"
           name="[CORE] C16 - the roll forward is satisfied where a fresh test was required and a test at full extent was performed (AS 2201 paras 54 and 56)"
           alt="A fresh test was required and the control was retested beyond inquiry at an extent the sampling layer accepts">
    <condition rel="has roll forward requirement" subject="%S" object="Full Retest"/>
    <condition rel="roll forward performed" subject="%S" object="true" weight="1"/>
    <condition rel="roll forward procedure was inquiry only" subject="%S" object="false" weight="1"/>
    <condition rel="extent of testing sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="substantive inference position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C15 - the roll forward is unsatisfied where a procedure is owed and no roll forward work was performed (AS 2201 para 55)"
           alt="A procedure is required for the remaining period and no roll forward work was performed at all">
    <condition rel="has roll forward requirement" subject="%S" object="%RFR1"/>
    <condition rel="roll forward performed" subject="%S" object="false" weight="1"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G10" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C15b - the roll forward is unsatisfied where a limited retest was required and the work was inquiry only (AS 2201 para 56 and APA 11 pages 28 to 29)"
           alt="A retest of instances was required over the remaining period and the work performed was inquiry only">
    <condition rel="has roll forward requirement" subject="%S" object="Limited Retest"/>
    <condition rel="roll forward procedure was inquiry only" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Inquiry') is equal to 0" weight="1"
               alt="The conditions that would allow inquiry alone do not apply to this control"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G11" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C15b C16 - the roll forward is unsatisfied where a fresh test was required and the work was inquiry only (AS 2201 para 56 and APA 11 pages 28 to 29)"
           alt="A fresh test was required over the remaining period and the work performed was inquiry only">
    <condition rel="has roll forward requirement" subject="%S" object="Full Retest"/>
    <condition rel="roll forward procedure was inquiry only" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Inquiry') is equal to 0" weight="1"
               alt="The conditions that would allow inquiry alone do not apply to this control"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G11b" weight="1"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C17 - the roll forward is unsatisfied where the instances retested fall below the calibrated minimum (AS 2201 para 54, practice calibration)"
           alt="Roll forward work was performed but on fewer instances than the calibrated minimum for the remaining period">
    <condition rel="roll forward sample size" subject="%S" object="%RFS2"/>
    <condition rel="applies testing policy" subject="%S" object="%P4" weight="1"/>
    <condition rel="minimum roll forward sample size" subject="%P4" object="%MINRF2" weight="1"/>
    <condition expression="%RFS2 is less than %MINRF2" weight="1"
               alt="The {{%RFS2}} instances retested fall below the calibrated minimum of {{%MINRF2}}"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','Inquiry') is equal to 0" weight="1"
               alt="The conditions that would allow inquiry alone do not apply to this control"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C16a - the roll forward is unsatisfied where sufficiency rests on substantive results (AS 2201 para B9 and ISA UK 330 para 16)"
           alt="Sufficiency over the remaining period rests on the absence of misstatements found by substantive work, which is not evidence about the control">
    <condition rel="roll forward sufficiency inferred from substantive work" subject="%S" object="true"/>
  </relinst>
  <relinst type="roll forward sufficient" object="false" cf="100"
           name="[CORE] C15 G6 - the roll forward is unsatisfied while the procedure for the remaining period is undetermined (AS 2201 para 55)"
           alt="An interim test is recorded but the facts needed to determine the procedure for the remaining period have not been supplied">
    <condition rel="has roll forward gap months" subject="%S" object="%G12"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward requirement',*) is equal to 0" weight="1"
               alt="No roll forward procedure has been determined for this control"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C15a - basis for accepting inquiry alone over the remaining period (AS 2201 para 56 Note, practice calibration of the gap)"
           alt="Records each of the four conditions that together allow inquiry alone, and the calibrated gap it was measured against">
    <condition rel="has roll forward requirement" subject="%S" object="Inquiry"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G13" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P5" weight="1"/>
    <condition rel="maximum roll forward gap months" subject="%P5" object="%MAXG3" weight="1"/>
    <condition expression="'Inquiry alone is accepted for the remaining period, and only because all four conditions hold: the control is low risk; substantially all the evidence was obtained at interim; no exceptions were noted at interim; and nothing significant changed afterwards. The remaining period is ' + %G13 + ' months against a calibrated maximum of ' + %MAXG3 + ' months. AS 2201 paragraph 56 Note allows inquiry in these circumstances. Remove any one of the four conditions and instances must be retested.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C15b - ground for requiring a retest of instances over the remaining period (AS 2201 paras 46 and 56, APA 11 pages 28 to 29)"
           alt="Explains that inquiry alone will not cover the remaining period for this control and what the retest has to achieve">
    <condition rel="has roll forward requirement" subject="%S" object="Limited Retest"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G14" weight="1"/>
    <condition expression="'Instances must be retested over the remaining ' + %G14 + ' months. Inquiry alone is not enough here: either the risk associated with the control is above low, or substantially all the evidence was not obtained at interim, or exceptions were noted at interim. The evidence needed increases as the risk associated with the control increases, AS 2201 paragraph 46, and the results of the interim test and the sufficiency of the interim evidence are two of the four roll forward factors, paragraph 56. The further evidence may be obtained by extending the tests over the remaining period or by testing the monitoring the bank performs over the control, and this assessment does not prescribe which.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C16 - ground for requiring a fresh test where the control changed after interim (AS 2201 para 56 d and ISA UK 330 para A34)"
           alt="Explains that a change after the interim date means what was tested is no longer what operates, so the interim evidence does not carry">
    <condition rel="has roll forward requirement" subject="%S" object="Full Retest"/>
    <condition rel="changes since interim" subject="%S" object="true" weight="1"/>
    <condition expression="'The control must be tested afresh over the remaining period because something significant changed after the interim date. Whether there were significant changes in internal control after the interim date is the fourth roll forward factor, AS 2201 paragraph 56. The international text names the kinds of change that matter, including changes in the information system, in the processes and in the personnel who apply the control, ISA UK 330 paragraph A34. Evidence about a control as it was before a change is not evidence about the control as it now operates, so the interim result does not carry forward.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C16 C17 - ground for requiring a fresh test where the remaining period is long (AS 2201 para 56 c, practice calibration)"
           alt="Explains that the remaining period exceeds the calibrated maximum and states plainly that the figure is practice and not standard">
    <condition rel="has roll forward requirement" subject="%S" object="Full Retest"/>
    <condition rel="has roll forward gap months" subject="%S" object="%G15" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P6" weight="1"/>
    <condition rel="maximum roll forward gap months" subject="%P6" object="%MAXG4" weight="1"/>
    <condition expression="%G15 is greater than %MAXG4" weight="1"
               alt="The remaining period of {{%G15}} months exceeds the calibrated maximum of {{%MAXG4}} months"/>
    <condition expression="'The remaining period of ' + %G15 + ' months exceeds the calibrated maximum of ' + %MAXG4 + ' months, so the control must be tested afresh rather than rolled forward. The length of the remaining period is the third roll forward factor, AS 2201 paragraph 56, but the standard sets no limit and the international text quantifies none either. The figure applied here is this assessment s own calibration and is the weakest sourced number in the pack: only one public practice source gives an explicit numeric trigger and two others corroborate a one to three month gap as typical without stating a maximum. An institution whose remaining periods routinely run longer should set its own figure and record the reasoning.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C17 I8 - a remaining period beyond the point where roll forward is unavailable (AS 2201 para 56 c, practice calibration)"
           alt="Records that the remaining period is past the point at which this calibration treats roll forward as unavailable altogether">
    <condition rel="has roll forward gap months" subject="%S" object="%G16"/>
    <condition rel="applies testing policy" subject="%S" object="%P7" weight="1"/>
    <condition rel="roll forward unavailable gap months" subject="%P7" object="%UNAVG" weight="1"/>
    <condition expression="%G16 is greater than %UNAVG" weight="1"
               alt="The remaining period of {{%G16}} months is past the calibrated point of {{%UNAVG}} months at which roll forward is unavailable"/>
    <condition expression="'The remaining period of ' + %G16 + ' months is past the point of ' + %UNAVG + ' months at which this calibration treats roll forward as unavailable altogether. At that distance the interim test covers so little of the period that it is better described as a prior test than an interim one, and the sensible course is to test the control over the period actually being reported on. Both month figures are practice calibration, not standard: AS 2201 paragraph 56 leaves the length of the remaining period an uncapped judgement.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C17 - the minimum number of instances a roll forward retest must cover (AS 2201 para 54, practice calibration)"
           alt="States the calibrated minimum number of instances a retest over the remaining period must cover, and that the figure is practice">
    <condition rel="has roll forward requirement" subject="%S" object="%RFR2"/>
    <condition rel="applies testing policy" subject="%S" object="%P8" weight="1"/>
    <condition rel="minimum roll forward sample size" subject="%P8" object="%MINRF3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','No Further Procedure Required') is equal to 0" weight="1"
               alt="A procedure is owed for a remaining period, so the retest floor is relevant"/>
    <condition expression="'Floor for a retest over the remaining period: at least ' + %MINRF3 + ' instances. The more extensively a control is tested the greater the evidence obtained, and the more frequently a control operates the more operations should be tested, AS 2201 paragraph 54, but no fetched source states a figure for a roll forward sample. The floor is this assessment s calibration and an institution testing a daily control over a long remaining period should normally set it well above the floor.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[CORE] C15 G6 - statement that no roll forward procedure could be determined (AS 2201 paras 55 and 56)"
           alt="States that the four factors cannot be applied on the facts given, so no procedure is published either way">
    <condition rel="has roll forward gap months" subject="%S" object="%G17"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward requirement',*) is equal to 0" weight="1"
               alt="No roll forward procedure has been determined for this control"/>
    <condition expression="'No roll forward procedure has been determined. Evidence was obtained at an interim date and the remaining period is ' + %G17 + ' months, but the answers needed to apply the four factors of AS 2201 paragraph 56 have not all been given. The procedure is a judgement on those factors, so neither the lightest nor the heaviest procedure is assumed. The remaining period counts as uncovered until the open questions below are answered.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C15 G6 - whether anything changed after the interim date is needed before a roll forward procedure can be set (AS 2201 para 56 d)"
           alt="No answer has been given about significant changes after the interim date, which is one of the four factors">
    <condition rel="has roll forward gap months" subject="%S" object="%G18"/>
    <condition expression="countRelationshipInstances(%S,'changes since interim',*) is equal to 0" weight="1"
               alt="No answer has been recorded about changes after the interim test date"/>
    <condition expression="'Whether there were significant changes in the control, or in the controls around it, after the interim test date. This is the fourth roll forward factor, AS 2201 paragraph 56, and it is the one that decides between carrying the interim evidence forward and testing the control afresh. The international text treats changes in the information system, in the processes and in the personnel applying the control as the changes that matter, ISA UK 330 paragraph A34. No answer is treated as no change.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C15a G6 - whether exceptions were noted at interim is needed before a roll forward procedure can be set (AS 2201 para 56 a)"
           alt="No answer has been given about exceptions at the interim test, which bears on whether inquiry alone can suffice">
    <condition rel="has roll forward gap months" subject="%S" object="%G19"/>
    <condition expression="countRelationshipInstances(%S,'interim exceptions noted',*) is equal to 0" weight="1"
               alt="No answer has been recorded about exceptions at the interim test"/>
    <condition expression="'Whether any exceptions were noted when the control was tested at interim. The results of the interim test are the first roll forward factor, AS 2201 paragraph 56, and inquiry alone over the remaining period is available only where there were no exceptions, paragraph 56 Note. Zero is an answer and has to be recorded as one.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C15a G6 - whether substantially all the evidence was obtained at interim is needed before a roll forward procedure can be set (AS 2201 para 56 b)"
           alt="No answer has been given about how much of the test evidence was obtained at the interim date">
    <condition rel="has roll forward gap months" subject="%S" object="%G20"/>
    <condition expression="countRelationshipInstances(%S,'substantially all evidence at interim',*) is equal to 0" weight="1"
               alt="No answer has been recorded about how much of the evidence was obtained at interim"/>
    <condition expression="'Whether substantially all of the test evidence was obtained at the interim date. The sufficiency of the evidence obtained at interim is the second roll forward factor, AS 2201 paragraph 56. Where the interim test covered only part of what the control does, the remaining period needs more than inquiry whatever else is true.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C15 G6 - whether roll forward work was performed is needed before the remaining period can be treated as covered (AS 2201 para 55)"
           alt="A procedure is owed for the remaining period and no answer has been given about whether any roll forward work was done">
    <condition rel="has roll forward requirement" subject="%S" object="%RFR3"/>
    <condition expression="countRelationshipInstances(%S,'roll forward performed',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether roll forward work was performed"/>
    <condition expression="countRelationshipInstances(%S,'has roll forward candidate','No Further Procedure Required') is equal to 0" weight="1"
               alt="A procedure is owed for a remaining period, so whether it was performed is load bearing"/>
    <condition expression="'Whether the roll forward work was actually performed, and if so on how many instances and by what procedure. A procedure is owed for the remaining period under AS 2201 paragraph 55, and until the work is recorded the remaining period counts as uncovered. Clean substantive results over those months are not an answer to this question, AS 2201 paragraph B9 and ISA UK 330 paragraph 16.'" value="%O"/>
  </relinst>
  <relinst type="has itgc reliance candidate" object="Reliance Not Applicable" cf="100"
           name="[CORE] C20 - no general IT control reliance arises where the control uses no IT application (AS 2201 para 36 and ISA UK 315 para 26 b)"
           alt="The control does not depend on an IT application, so there is no general IT control reliance to judge">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="relies on application" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance candidate" object="Reliance Available" cf="100"
           name="[CORE] C20 - reliance available where general IT controls are effective and tested this period (AS 1105 para 10 a, ISA UK 315 para 12 d)"
           alt="The control depends on an IT application and the general IT controls over it are concluded effective and are being tested in the current period">
    <condition rel="relies on application" subject="%S" object="true"/>
    <condition rel="has itgc conclusion" subject="%S" object="Effective" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C20 - general IT control reliance is not available where the general IT controls are deficient (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="The general IT controls over the application this control depends on are deficient, so nothing about this control may rest on them">
    <condition rel="relies on application" subject="%S" object="true"/>
    <condition rel="has itgc conclusion" subject="%S" object="Deficient" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C20 - general IT control reliance is not available where the general IT controls have not been tested (AS 1105 para 10 a and ISA UK 315 para 26 b)"
           alt="The general IT controls over the application this control depends on have not been tested, so there is no conclusion for this control to rely on">
    <condition rel="relies on application" subject="%S" object="true"/>
    <condition rel="has itgc conclusion" subject="%S" object="Not Tested" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C20 - no reliance where the general IT controls are not being tested in the current period (AS 1105 para 10 a, ISA UK 330 para A39)"
           alt="The general IT controls were concluded effective but are not being tested in the current period, so the conclusion does not cover the period being reported on">
    <condition rel="relies on application" subject="%S" object="true"/>
    <condition rel="has itgc conclusion" subject="%S" object="Effective" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance availability" object="Reliance Not Available" cf="100"
           name="[CORE] C20 - general IT control reliance is withheld where any defeating fact is established (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="A fact defeating general IT control reliance has been established, which outranks any favourable candidate">
    <condition rel="has itgc reliance candidate" subject="%S" object="Reliance Not Available"/>
  </relinst>
  <relinst type="has itgc reliance availability" object="Reliance Available" cf="100"
           name="[CORE] C20 - general IT control reliance governs where every leg is established and nothing defeats it (AS 1105 para 10 a and ISA UK 315 para 12 d)"
           alt="The general IT controls are effective and currently tested and no defeating fact has been established">
    <condition expression="countRelationshipInstances(%S,'has itgc reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No fact defeating general IT control reliance has been established"/>
    <condition rel="has itgc reliance candidate" subject="%S" object="Reliance Available"/>
  </relinst>
  <relinst type="has itgc reliance availability" object="Reliance Not Applicable" cf="100"
           name="[CORE] C20 - general IT control reliance does not apply where nothing engages it (AS 2201 para 36 and ISA UK 315 para 26 b)"
           alt="The control uses no IT application and no fact about general IT controls has been established either way">
    <condition expression="countRelationshipInstances(%S,'has itgc reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No fact defeating general IT control reliance has been established"/>
    <condition expression="countRelationshipInstances(%S,'has itgc reliance candidate','Reliance Available') is equal to 0" weight="1"
               alt="General IT control reliance has not been positively established"/>
    <condition rel="has itgc reliance candidate" subject="%S" object="Reliance Not Applicable"/>
  </relinst>
  <relinst type="has itgc reliance finding" cf="100"
           name="[CORE] C20 - a test of one instance is not permitted where general IT control reliance is withheld (AS 1105 para 10 a, AS 2201 para 54 and ISA UK 330 para A39)"
           alt="States that the automated shortcut is unavailable and the control must be tested at the extent a person performed control requires">
    <condition rel="has itgc reliance availability" subject="%S" object="Reliance Not Available"/>
    <condition expression="'General IT control reliance is withheld, so testing a single instance of this control is not permitted and the evidence is insufficient pending testing of the control itself at the extent a control performed by a person would require. The reason the single instance shortcut exists at all is that the general IT controls are relied on to show the program has not changed; where those controls are deficient, untested, or not tested in the period being reported on, that support is absent. Either the information itself must be tested directly or the controls over its accuracy and completeness must be tested, AS 1105 paragraph 10 a, and deficient general IT controls are an explicit factor defeating reliance, ISA UK 330 paragraph A39.'" value="%O"/>
  </relinst>
  <relinst type="has itgc reliance finding" cf="100"
           name="[CORE] C20 - basis for relying on the general IT controls over this control (AS 1105 para 10 a and ISA UK 315 paras 12 d and 26 b)"
           alt="Records what the favourable general IT control reliance conclusion rests on and what it does not extend to">
    <condition rel="has itgc reliance availability" subject="%S" object="Reliance Available"/>
    <condition expression="'General IT control reliance is available. The general IT controls over the application this control depends on are concluded effective and are being tested in the current period, so the controls over the integrity of the information the control uses are established rather than assumed, AS 1105 paragraph 10 a and ISA UK 315 paragraph 12 d. The conclusion reaches only the applications and processes actually within the scope of that general IT control testing. It is not extended by implication to data, queries or spreadsheets produced outside that scope, and it says nothing about whether this control itself operated.'" value="%O"/>
  </relinst>
  <relinst type="has itgc reliance finding" cf="100"
           name="[CORE] C20 - statement that general IT control reliance does not arise for this control (AS 2201 para 36 and ISA UK 315 para 26 b)"
           alt="Records that the control engages no IT application, so the general IT control question is not open against it">
    <condition rel="has itgc reliance availability" subject="%S" object="Reliance Not Applicable"/>
    <condition expression="'General IT control reliance does not arise. This control is recorded as using no IT application, so there are no general IT controls for its result to depend on. The IT applications subject to risks arising from the use of IT are identified from the controls actually identified, ISA UK 315 paragraph 26 b, and identifying risks arising from IT is part of working down from the financial statements to the controls rather than a separate exercise, AS 2201 paragraph 36. If the control in fact uses a report, a query or a spreadsheet, the record is wrong and should be corrected before this result is relied on.'" value="%O"/>
  </relinst>
  <relinst type="report reliance available" object="true" cf="100"
           name="[CORE] C22 - a report tested directly for accuracy and completeness is reliable (AS 1105 para 10 a first limb and ISA UK 315 para 12 d)"
           alt="The accuracy and completeness of this report were tested directly, which satisfies the first limb of the obligation">
    <condition rel="report completeness and accuracy tested" subject="%S" object="true"/>
  </relinst>
  <relinst type="report reliance available" object="true" cf="100"
           name="[CORE] C22 - a report inside effective and tested general IT controls is reliable (AS 1105 para 10 a second limb and ISA UK 315 paras 12 d and 26 b)"
           alt="The controls over this report's accuracy and completeness are effective and the report falls inside the scope that was tested">
    <condition rel="report has itgc conclusion" subject="%S" object="Effective"/>
    <condition rel="report within tested itgc scope" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="report reliance available" object="false" cf="100"
           name="[CORE] C22 - a report neither tested directly nor covered by effective general IT controls is not reliable (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="This report was not tested directly and the general IT controls over it are deficient, so neither limb of the obligation is met">
    <condition rel="report has itgc conclusion" subject="%S" object="Deficient"/>
    <condition expression="countRelationshipInstances(%S,'report completeness and accuracy tested','true') is equal to 0" weight="1"
               alt="Nothing records that the accuracy and completeness of this report were tested directly"/>
  </relinst>
  <relinst type="report reliance available" object="false" cf="100"
           name="[CORE] C22 - a report neither tested directly nor covered by tested general IT controls is not reliable (AS 1105 para 10 a and ISA UK 315 para 26 b)"
           alt="This report was not tested directly and the general IT controls over it have not been tested, so neither limb of the obligation is met">
    <condition rel="report has itgc conclusion" subject="%S" object="Not Tested"/>
    <condition expression="countRelationshipInstances(%S,'report completeness and accuracy tested','true') is equal to 0" weight="1"
               alt="Nothing records that the accuracy and completeness of this report were tested directly"/>
  </relinst>
  <relinst type="report reliance available" object="false" cf="100"
           name="[CORE] C22 - a report outside the scope of the general IT controls tested is not reliable on that conclusion alone (AS 1105 para 10 a and ISA UK 315 para 26 b)"
           alt="This report falls outside the scope of the general IT control testing performed and was not tested directly either">
    <condition rel="report has itgc conclusion" subject="%S" object="%RIC9"/>
    <condition expression="countRelationshipInstances(%S,'report within tested itgc scope','true') is equal to 0" weight="1"
               alt="Nothing records that this report falls inside the scope of the general IT controls tested"/>
    <condition expression="countRelationshipInstances(%S,'report completeness and accuracy tested','true') is equal to 0" weight="1"
               alt="Nothing records that the accuracy and completeness of this report were tested directly"/>
  </relinst>
  <relinst type="has unreliable relied on report" cf="100"
           name="[CORE] C22 - projects an unreliable relied on report onto the control that uses it (AS 1105 para 10 and ISA UK 315 para 12 d)"
           alt="Carries an unreliable report onto the control that relies on it, so the control can be judged on the reports it actually uses">
    <condition rel="has relied on report" subject="%S" object="%O"/>
    <condition rel="report reliance available" subject="%O" object="false" weight="1"/>
  </relinst>
  <relinst type="has reliable relied on report" cf="100"
           name="[CORE] C22 - projects a reliable relied on report onto the control that uses it (AS 1105 para 10 and ISA UK 315 para 12 d)"
           alt="Carries a report whose reliability is established onto the control that relies on it">
    <condition rel="has relied on report" subject="%S" object="%O"/>
    <condition rel="report reliance available" subject="%O" object="true" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Applicable" cf="100"
           name="[CORE] C22 - no entity information reliance arises where the control uses no internally produced information (AS 1105 para 10 and ISA UK 315 para 12 d)"
           alt="The control is recorded as using no information produced inside the bank, so there is no reliance on such information to judge">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has relied on report',*) is equal to 0" weight="1"
               alt="No relied on report is recorded against this control"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Available" cf="100"
           name="[CORE] C22 - entity information reliance is available where both limbs of the obligation are established (AS 1105 para 10 a and b, ISA UK 315 para 12 g)"
           alt="The accuracy and completeness of the information were established and the information was evaluated as sufficiently precise and detailed for what the control does with it">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition rel="ipe completeness and accuracy tested" subject="%S" object="true" weight="1"/>
    <condition rel="ipe sufficiently precise and detailed" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has unreliable relied on report',*) is equal to 0" weight="1"
               alt="No report this control relies on has been found unreliable"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C22 - entity information reliance is not available where accuracy and completeness are untested (AS 1105 para 10 a and ISA UK 315 para 12 d)"
           alt="The control relies on information produced inside the bank and the accuracy and completeness of that information were not established">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition rel="ipe completeness and accuracy tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C22 - entity information reliance is not available where the information is not sufficiently precise and detailed (AS 1105 para 10 b and ISA UK 315 para 12 g)"
           alt="The information the control relies on was not evaluated as sufficiently precise and detailed for the purpose the control puts it to">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition rel="ipe sufficiently precise and detailed" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[CORE] C22 - entity information reliance is not available where a report the control uses is unreliable (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="At least one report this control relies on has been found unreliable, so the information the control acts on is not established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has unreliable relied on report',*) is greater than or equal to 1" weight="1"
               alt="At least one report this control relies on has been found unreliable"/>
  </relinst>
  <relinst type="has ipe reliance availability" object="Reliance Not Available" cf="100"
           name="[CORE] C22 - entity information reliance is withheld where any defeating fact is established (AS 1105 para 10 and ISA UK 330 para A39)"
           alt="A fact defeating reliance on the internally produced information has been established, which outranks any favourable candidate">
    <condition rel="has ipe reliance candidate" subject="%S" object="Reliance Not Available"/>
  </relinst>
  <relinst type="has ipe reliance availability" object="Reliance Available" cf="100"
           name="[CORE] C22 - entity information reliance governs where both limbs are established and nothing defeats them (AS 1105 para 10 a and b, ISA UK 315 para 12 g)"
           alt="Both limbs of the obligation are established and no defeating fact has been found">
    <condition expression="countRelationshipInstances(%S,'has ipe reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No fact defeating reliance on the internally produced information has been established"/>
    <condition rel="has ipe reliance candidate" subject="%S" object="Reliance Available"/>
  </relinst>
  <relinst type="has ipe reliance availability" object="Reliance Not Applicable" cf="100"
           name="[CORE] C22 - entity information reliance does not apply where nothing engages it (AS 1105 para 10 and ISA UK 315 para 26 b)"
           alt="The control uses no internally produced information and no report is recorded against it">
    <condition expression="countRelationshipInstances(%S,'has ipe reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No fact defeating reliance on the internally produced information has been established"/>
    <condition expression="countRelationshipInstances(%S,'has ipe reliance candidate','Reliance Available') is equal to 0" weight="1"
               alt="Reliance on internally produced information has not been positively established"/>
    <condition rel="has ipe reliance candidate" subject="%S" object="Reliance Not Applicable"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C22 - untested internally produced information is insufficient evidence rather than a clean result (AS 1105 para 10 a and ISA UK 315 para 12 d)"
           alt="States that an untested report or data set makes the evidence insufficient however clean the sample results were">
    <condition rel="has ipe reliance availability" subject="%S" object="Reliance Not Available"/>
    <condition rel="ipe completeness and accuracy tested" subject="%S" object="false" weight="1"/>
    <condition expression="'The accuracy and completeness of the information this control relies on were not established. Where information produced inside the bank is used as evidence, either the information itself must be tested for accuracy and completeness or the controls over its accuracy and completeness must be tested, including general IT controls and automated application controls, AS 1105 paragraph 10 a; the integrity of the information in the information system is what general IT controls exist to support, ISA UK 315 paragraph 12 d. A clean sample proves nothing if the population the sample was drawn from is unestablished, so this is insufficient evidence rather than a favourable result. The control is not shown ineffective either.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C22 - information that is not sufficiently precise and detailed cannot support the control (AS 1105 para 10 b and ISA UK 315 para 12 g)"
           alt="States that the second limb of the obligation failed and what it means in practice">
    <condition rel="has ipe reliance availability" subject="%S" object="Reliance Not Available"/>
    <condition rel="ipe sufficiently precise and detailed" subject="%S" object="false" weight="1"/>
    <condition expression="'The information this control relies on is not sufficiently precise and detailed for the purpose the control puts it to. Accuracy and completeness are only the first limb of the obligation; the information must also be evaluated as sufficiently precise and detailed for the purpose it is used for, AS 1105 paragraph 10 b. A report can be entirely accurate and still be too summarised, too aggregated or too stale for the control to detect what the control exists to detect. Reliance is therefore withheld, and a report at the level of detail the control actually needs is required.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C22 - an unreliable relied on report named against the control that uses it (AS 1105 para 10 a and ISA UK 315 para 26 b)"
           alt="Names a report whose reliability is not established, so the control owner knows which one to deal with">
    <condition rel="has unreliable relied on report" subject="%S" object="%R"/>
    <condition expression="'A report this control relies on has no established reliability: ' + %R + '. Neither limb of the obligation is met for it - its accuracy and completeness were not tested directly, and it is not covered by general IT controls that were both concluded effective and within the scope actually tested, AS 1105 paragraph 10 a and ISA UK 315 paragraph 26 b. A general IT control conclusion covers the applications and processes it was scoped over and is not extended by implication to data, queries or spreadsheets outside that scope. Either test this report directly or bring it inside the scope of the controls tested.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C22 - basis for relying on the internally produced information this control uses (AS 1105 para 10 a and b, ISA UK 315 paras 12 d and 12 g)"
           alt="Records what the favourable conclusion on internally produced information rests on">
    <condition rel="has ipe reliance availability" subject="%S" object="Reliance Available"/>
    <condition expression="'Reliance on the internally produced information is available. Both limbs are established: the accuracy and completeness of the information are supported, either by testing the information itself or by testing the controls over it, and the information has been evaluated as sufficiently precise and detailed for the purpose the control puts it to, AS 1105 paragraph 10 a and b. Where reports are recorded against this control, each one has an established basis. This conclusion is about the information the control acts on, not about whether the control itself operated.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C22 - statement that no internally produced information is relied on by this control (AS 1105 para 10 and ISA UK 315 para 26 b)"
           alt="Records that the control engages no internally produced information, and says plainly what counts as such information">
    <condition rel="has ipe reliance availability" subject="%S" object="Reliance Not Applicable"/>
    <condition expression="'No reliance on internally produced information arises. This control is recorded as acting on no report, extract, query or data set produced inside the bank. That category is wider than a formal report: a spreadsheet, a system extract, an ad hoc query result and a manually compiled schedule all count, and a control that compares two internally produced figures relies on both. If any of those are in fact used, the record is wrong and should be corrected before this result is relied on.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[CORE] C24a - terminology note on information produced by the entity (AS 1105 para 10)"
           alt="Explains the term the graph uses and why the common practice abbreviation is not treated as a source">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition expression="'Terminology. This assessment says information produced by the entity, which tracks the wording of the requirement it rests on, AS 1105 paragraph 10. The three letter abbreviation in common use appears in no primary source checked in this build: the US staff practice alert speaks of system generated data and reports, and the international text speaks of the integrity of information in the information system. The obligation cited above is the standard s, not a practice abbreviation s, and nothing here is cited to a practice alert for the obligation itself.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] C22a - the US authority for the information reliability obligation (AS 1105 paras 10 and 10A)"
           alt="States the US instrument the information reliability obligation rests on, and that the depth tests beyond it are practice">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true" weight="1"/>
    <condition expression="'Authority on this path. The obligation applied above is AS 1105 paragraph 10: information produced by the company and used as evidence requires procedures that test either the information or the controls over its accuracy and completeness, including general IT controls and automated application controls, and an evaluation that the information is sufficiently precise and detailed for the purpose. Paragraph 10A adds a separate route for information the company obtained from an external source and supplied electronically. The further depth tests this assessment can apply - report class, query logic, report parameters and two way testing - come from the regulator s staff inspection guidance rather than from the standard, and are reported as such.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[UK] C22a - the international authority for the information reliability obligation (ISA UK 315 paras 12 d 12 g and 26 b, ISA UK 330 para A39)"
           alt="States the international instruments the information reliability obligation rests on, and that the US depth tests are offered only as practice here">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true" weight="1"/>
    <condition expression="'Authority on this path. The obligation applied above rests on the international text: general IT controls are the controls over the bank s IT processes that support the integrity of information, meaning its completeness, accuracy and validity, in the information system, ISA UK 315 paragraph 12 d; the IT applications and other aspects of the IT environment subject to risks arising from the use of IT are identified from the controls identified, paragraph 26 b; and deficient general IT controls are an express factor defeating reliance on a control, ISA UK 330 paragraph A39. The US inspection guidance on report class, query logic and report parameters binds nothing here; where this assessment applies those tests on this path it does so as a labelled practice recommendation under its own calibration and never as authority.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[UK] C22a I32 - the depth tests are offered as practice on the international path (parameter ipe depth offered as practice)"
           alt="Records that the deeper report tests are switched on as a practice recommendation on this path, and that failing one is a recommendation and not a breach">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%P1" weight="1"/>
    <condition rel="ipe depth offered as practice" subject="%P1" object="true" weight="1"/>
    <condition expression="'Practice recommendation on this path. The deeper report tests - whether the report is a standard report, a customised one or an ad hoc query, whether the query logic was tested, and whether the parameters used to run it were checked - are switched on in this calibration as a recommendation. They come from US inspection guidance that binds no engagement here, so on this path a gap in one of them is reported as a recommendation and never as a failure of the standard. An institution that does not want them can switch them off, and the determination will not change.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C20 G6 - whether the control uses an IT application is needed before general IT control reliance can be judged (AS 2201 para 36 and ISA UK 315 para 26 b)"
           alt="No answer has been given about whether the control depends on an IT application">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'relies on application',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control depends on an IT application"/>
    <condition expression="'Whether this control depends on an IT application. Identifying the risks that arise from the use of IT is part of working down from the financial statements to the controls, AS 2201 paragraph 36, and the applications in scope are identified from the controls identified, ISA UK 315 paragraph 26 b. Until this is answered there is no way to tell whether a general IT control conclusion is needed at all.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C20 G6 - the general IT control conclusion is needed before reliance can be judged (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="The control depends on an IT application and no general IT control conclusion has been supplied">
    <condition rel="relies on application" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has itgc conclusion',*) is equal to 0" weight="1"
               alt="No general IT control conclusion has been supplied for this control"/>
    <condition expression="'What the conclusion is on the general IT controls over the application this control depends on - effective, deficient, or not tested. Reliance on a control can rest on the controls over the accuracy and completeness of the information it uses, AS 1105 paragraph 10 a, and deficient general IT controls are an express factor defeating reliance, ISA UK 330 paragraph A39. Not tested is an answer and must be recorded as one; it is not the same as effective.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C20 G6 - whether the general IT controls are tested in the current period is needed before reliance can be judged (AS 1105 para 10 a)"
           alt="A general IT control conclusion has been supplied and it is not known whether those controls are being tested in the current period">
    <condition rel="has itgc conclusion" subject="%S" object="Effective"/>
    <condition expression="countRelationshipInstances(%S,'itgc currently tested',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the general IT controls are tested in the current period"/>
    <condition expression="'Whether the general IT controls relevant to this control are being tested in the current period. A conclusion carried over from an earlier period is not a test of the controls over the information used in the period being reported on, so the answer decides whether the effective conclusion above can be relied on here, AS 1105 paragraph 10 a.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C22 G6 - whether the control uses internally produced information is needed before its evidence can be judged (AS 1105 para 10)"
           alt="No answer has been given about whether the control acts on information produced inside the bank">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'relies on information produced by the entity',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control relies on internally produced information"/>
    <condition expression="'Whether this control acts on a report, extract, query result, spreadsheet or data set produced inside the bank. Where such information is used as evidence, its accuracy and completeness must be supported and its precision evaluated, AS 1105 paragraph 10. The category is wider than formal reports, and a control that compares two internally produced figures relies on both of them.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C22 G6 - whether the accuracy and completeness of the information were established is needed before the evidence can be judged (AS 1105 para 10 a)"
           alt="The control relies on internally produced information and no answer has been given about testing its accuracy and completeness">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'ipe completeness and accuracy tested',*) is equal to 0" weight="1"
               alt="No answer has been recorded about testing the accuracy and completeness of the information"/>
    <condition expression="'Whether the accuracy and completeness of that information were established, either by testing the information itself or by testing the controls over it including the general IT controls, AS 1105 paragraph 10 a. This is the first limb of the obligation and no favourable result is available without it. An unanswered question is not a pass.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C22 G6 - whether the information is sufficiently precise and detailed is needed before the evidence can be judged (AS 1105 para 10 b)"
           alt="The control relies on internally produced information and no answer has been given about its precision and detail">
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'ipe sufficiently precise and detailed',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the information is sufficiently precise and detailed"/>
    <condition expression="'Whether that information is sufficiently precise and detailed for the purpose this control puts it to, AS 1105 paragraph 10 b. This is the second limb of the obligation and it is separate from accuracy: a report can be wholly accurate and still be too summarised or too stale for the control to detect what it exists to detect.'" value="%O"/>
  </relinst>
  <relinst type="has operating candidate" object="No Operating Determination" cf="100"
           name="[CORE] C1 R4 - candidate no operating determination where the record is internally inconsistent (AS 2201 paras 39 to 41)"
           alt="An inconsistency has been found in the control record, so no operating conclusion can be reached on it">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is greater than or equal to 1" weight="1"
               alt="At least one input inconsistency has been found for this control"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[CORE] C4 - candidate insufficient evidence where the extent of testing is not sufficient (AS 2201 para 54 and AS 2315 para 38)"
           alt="The number of instances tested does not meet the required extent, so the evidence does not support a conclusion either way">
    <condition rel="extent of testing sufficient" subject="%S" object="false"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[CORE] C12 C13 - candidate insufficient evidence where a required sufficiency test did not clear (AS 2201 para 50 and SEC Release 33-8810 II A 2)"
           alt="A required evidence sufficiency test did not clear, so the evidence does not support a conclusion either way">
    <condition rel="evidence is sufficient" subject="%S" object="false"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[CORE] C15 C16 - candidate insufficient evidence where the remaining period is not covered (AS 2201 paras 55 and 56)"
           alt="The procedure the remaining period requires has not been satisfied, so the evidence does not reach the period end">
    <condition rel="roll forward sufficient" subject="%S" object="false"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[CORE] C20 - candidate insufficient evidence where general IT control reliance is withheld (AS 1105 para 10 a and ISA UK 330 para A39)"
           alt="Reliance on the general IT controls is not available, so the result of a test that rests on them is not supported">
    <condition rel="has itgc reliance availability" subject="%S" object="Reliance Not Available"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[CORE] C22 - candidate insufficient evidence where reliance on internally produced information is withheld (AS 1105 para 10 and ISA UK 315 para 12 d)"
           alt="Reliance on the information the control acts on is not available, so a clean sample drawn from it proves nothing">
    <condition rel="has ipe reliance availability" subject="%S" object="Reliance Not Available"/>
  </relinst>
  <relinst type="has operating candidate" object="Not Operating Effectively" cf="100"
           name="[CORE] C10 - candidate not operating effectively where the deviations are systemic (AS 2315 paras 41 and 42)"
           alt="The deviations found arise from the way the control operates, so they are expected to recur across the population">
    <condition rel="has effective exception nature" subject="%S" object="Systemic"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Not Operating Effectively" cf="100"
           name="[CORE] C10 C10a - candidate not operating effectively where the deviation rate exceeds the tolerable rate (AS 2315 paras 34 38 and 41)"
           alt="The deviation rate observed in the sample exceeds the tolerable rate, and the sample rate is the estimate of the population rate">
    <condition rel="has deviation rate percent" subject="%S" object="%DR"/>
    <condition rel="applies testing policy" subject="%S" object="%P1" weight="1"/>
    <condition rel="tolerable deviation rate percent" subject="%P1" object="%TDR" weight="1"/>
    <condition expression="%DR is greater than %TDR" weight="1"
               alt="The deviation rate of {{%DR}} per cent exceeds the tolerable rate of {{%TDR}} per cent"/>
  </relinst>
  <relinst type="has operating candidate" object="Not Operating Effectively" cf="100"
           name="[CORE] C1a - candidate not operating effectively where the performer lacks the necessary authority (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="The person performing the control does not have the authority to perform it as designed, which is part of the definition of operating effectiveness">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="performer authority attested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Not Operating Effectively" cf="100"
           name="[CORE] C1a - candidate not operating effectively where the performer lacks the necessary competence (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="The competence of the person performing the control is not attested, which is part of the definition of operating effectiveness">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition rel="reviewer competence attested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Exception Requiring Evaluation" cf="100"
           name="[CORE] C7 B9b - candidate exception requiring evaluation where deviations stand against the control (AS 2201 para 48 and Note, and AS 2315 para 41)"
           alt="At least one deviation stands against the control, so it is a deficiency to be evaluated rather than a cleared result">
    <condition rel="exception position clear" subject="%S" object="false"/>
    <condition rel="extent of testing sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="evidence is sufficient" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Operating Effective" cf="100"
           name="[CORE] C1 C6 - candidate operating effective where every gate is explicitly cleared (SEC Release 33-8810 II A 2 and AS 2201 paras 48 50 and A3)"
           alt="Every operating effectiveness gate is positively cleared for this control and no adverse ground has been established">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is equal to 0" weight="1"
               alt="No input inconsistency has been found for this control"/>
    <condition rel="exception position clear" subject="%S" object="true" weight="1"/>
    <condition rel="extent of testing sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="evidence is sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="roll forward sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="performer authority attested" subject="%S" object="true" weight="1"/>
    <condition rel="reviewer competence attested" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has itgc reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="Nothing defeats reliance on the general IT controls over this control"/>
    <condition expression="countRelationshipInstances(%S,'has ipe reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="Nothing defeats reliance on the information this control acts on"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="No Operating Determination" cf="100"
           name="[CORE] C1 - no operating determination governs an inconsistent record (AS 2201 paras 39 to 41)"
           alt="The control record is internally inconsistent, which outranks every substantive operating conclusion">
    <condition rel="has operating candidate" subject="%S" object="No Operating Determination"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="Testing Not Required" cf="100"
           name="[US] C29 - testing not required governs a control superseded in the period (AS 2201 para 53)"
           alt="The control was superseded during the period by a successor achieving the same objectives, so it need not be tested for this conclusion">
    <condition expression="countRelationshipInstances(%S,'has operating candidate','No Operating Determination') is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition rel="has operating candidate" subject="%S" object="Testing Not Required"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="Insufficient Evidence" cf="100"
           name="[CORE] C4 C12 C13 - insufficient evidence governs where a gate is not satisfied and nothing outranks it (AS 2201 paras 50 and 54)"
           alt="At least one evidence gate is not satisfied, which outranks any substantive conclusion about how the control operated">
    <condition expression="countRelationshipInstances(%S,'has operating candidate','No Operating Determination') is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Testing Not Required') is equal to 0" weight="1"
               alt="This control is not one that need not be tested"/>
    <condition rel="has operating candidate" subject="%S" object="Insufficient Evidence"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="Not Operating Effectively" cf="100"
           name="[CORE] C1a C10 - not operating effectively governs where an adverse ground stands on sufficient evidence (AS 2315 paras 41 and 42, SEC Release 33-8810 II A 2)"
           alt="A substantive adverse ground stands against the control and the evidence is sufficient to support that conclusion">
    <condition expression="countRelationshipInstances(%S,'has operating candidate','No Operating Determination') is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Testing Not Required') is equal to 0" weight="1"
               alt="This control is not one that need not be tested"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Insufficient Evidence') is equal to 0" weight="1"
               alt="Every evidence gate is satisfied for this control"/>
    <condition rel="has operating candidate" subject="%S" object="Not Operating Effectively"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="Exception Requiring Evaluation" cf="100"
           name="[CORE] C7 - exception requiring evaluation governs where deviations stand but no adverse ground outranks them (AS 2201 para 48)"
           alt="Deviations stand against the control but they are neither systemic nor above the tolerable rate, so they are a deficiency pending evaluation">
    <condition expression="countRelationshipInstances(%S,'has operating candidate','No Operating Determination') is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Testing Not Required') is equal to 0" weight="1"
               alt="This control is not one that need not be tested"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Insufficient Evidence') is equal to 0" weight="1"
               alt="Every evidence gate is satisfied for this control"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Not Operating Effectively') is equal to 0" weight="1"
               alt="No substantive adverse ground stands against this control"/>
    <condition rel="has operating candidate" subject="%S" object="Exception Requiring Evaluation"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="Operating Effective" cf="100"
           name="[CORE] C6 - operating effective governs only where nothing outranks it (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="Every gate is explicitly cleared and no adverse ground, evidence gap or inconsistency stands against the control">
    <condition expression="countRelationshipInstances(%S,'has operating candidate','No Operating Determination') is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Testing Not Required') is equal to 0" weight="1"
               alt="This control is not one that need not be tested"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Insufficient Evidence') is equal to 0" weight="1"
               alt="Every evidence gate is satisfied for this control"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Not Operating Effectively') is equal to 0" weight="1"
               alt="No substantive adverse ground stands against this control"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate','Exception Requiring Evaluation') is equal to 0" weight="1"
               alt="No deviation stands against this control"/>
    <condition rel="has operating candidate" subject="%S" object="Operating Effective"/>
  </relinst>
  <relinst type="has operating effectiveness conclusion" object="No Operating Determination" cf="100"
           name="[CORE] C1 G6 - no operating determination where no candidate could be derived (AS 2201 para 50)"
           alt="No operating effectiveness candidate could be derived from the facts supplied, so no determination is published">
    <condition rel="is a control under assessment" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate',*) is equal to 0" weight="1"
               alt="No operating effectiveness candidate could be derived from the facts supplied"/>
  </relinst>
  <relinst type="has deficiency trigger" object="Operating Deficiency" cf="100"
           name="[CORE] D1 C1a - a failure of authority or competence gives rise to a deficiency for severity evaluation (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="The control fails on the authority or competence limb of operating effectiveness, which is a deficiency to be evaluated for severity">
    <condition rel="has operating candidate" subject="%S" object="Not Operating Effectively"/>
    <condition expression="countRelationshipInstances(%S,'exception position clear','false') is equal to 0" weight="1"
               alt="No deviation stands against this control, so the adverse ground is not an exception"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is equal to 0" weight="1"
               alt="The control record is internally consistent"/>
  </relinst>
  <relinst type="has evidence sufficiency finding" cf="100"
           name="[CORE] B3 C1 - a design deficient control that operated as described is still design deficient (AS 2201 paras A3 42 and 43)"
           alt="States that a favourable operating conclusion on a design deficient control does not cure the design deficiency">
    <condition rel="has design assessment" subject="%S" object="Design Deficient"/>
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Operating Effective" weight="1"/>
    <condition expression="'Read this operating conclusion with the design conclusion. The control was performed as described and the test found nothing against it, but as described the control would not meet its objective even if everyone followed it exactly, AS 2201 paragraph A3. Faithful performance of an inadequate control is not an effective control. The design deficiency stands, it is carried into the severity evaluation in its own right, and a favourable operating result does not reduce it.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C25 - the four items the operating effectiveness output must state (AS 2201 paras 50 54 and 55)"
           alt="Gathers the required extent, the sufficiency count, the roll forward procedure and the two reliance conclusions into one line">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="%OC1"/>
    <condition rel="has required sample size" subject="%S" object="%RSS" weight="1"/>
    <condition rel="has roll forward requirement" subject="%S" object="%RFR" weight="1"/>
    <condition rel="has itgc reliance availability" subject="%S" object="%IA" weight="1"/>
    <condition rel="has ipe reliance availability" subject="%S" object="%PA" weight="1"/>
    <condition expression="'Operating effectiveness: ' + %OC1 + '. Required instances for this frequency and risk: ' + %RSS + '. Procedure required for the remaining period: ' + %RFR + '. General IT control reliance: ' + %IA + '. Reliance on internally produced information: ' + %PA + '. Each evidence sufficiency test is reported separately above with the result it returned.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C6 G3 - reason for an operating effective conclusion (SEC Release 33-8810 II A 2 and AS 2201 paras 48 50 and A3)"
           alt="Explains what the favourable operating conclusion rests on and the limits of what it says">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Operating Effective"/>
    <condition expression="'Operating effective. Every gate is positively cleared, not merely unchallenged: the sample met the required extent, every required evidence sufficiency test returned a pass, no deviation stands against the control, the remaining period after any interim test is covered, and the authority and competence of the performer are attested. Operating effectiveness means the control operates as designed and the person performing it possesses the necessary authority and competence, SEC Release 33-8810 II A 2 and AS 2201 paragraph A3; both limbs are met. The conclusion covers the period and population tested and nothing else.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C7 B9b G3 - reason for an exception requiring evaluation conclusion (AS 2201 para 48 and Note, and AS 2315 para 41)"
           alt="Explains that deviations stand within tolerance, which is a deficiency pending evaluation rather than a failed control">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Exception Requiring Evaluation"/>
    <condition expression="'Exception requiring evaluation. One or more deviations stand against the control on evidence sufficient to support a conclusion, but neither the systemic ground nor the tolerable rate ground is made out. The deviation is a deficiency to be evaluated for severity, and the finding of a deviation requires the testing approach to be reassessed rather than the result averaged away, AS 2201 paragraph 48. This assessment does not extend the sample to clear it. The severity of the deficiency is the next question and it is answered at decision point three.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C1a C10 G3 - reason for a not operating effectively conclusion (AS 2315 paras 41 and 42, SEC Release 33-8810 II A 2)"
           alt="Explains the adverse conclusion and that it rests on evidence sufficient to support it">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Not Operating Effectively"/>
    <condition expression="'Not operating effectively. A substantive ground stands against the control on evidence sufficient to support the conclusion: either the deviations arise from the way the control operates rather than from the instances selected, or the deviation rate exceeds the tolerable rate, or the person performing the control lacks the attested authority or competence that is part of the definition of operating effectiveness. The sample deviation rate is the best estimate of the population rate, AS 2315 paragraph 41, and the authority and competence limb comes from SEC Release 33-8810 II A 2 and AS 2201 paragraph A3. The findings above name the ground that applied.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C4 C12 G3 - reason for an insufficient evidence conclusion (AS 2201 paras 50 and 54)"
           alt="Explains that an evidence gate failed, that this is not a finding against the control, and what to do about it">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Insufficient Evidence"/>
    <condition expression="'Insufficient evidence. At least one evidence gate is not satisfied, so no conclusion about how the control operated is available in either direction. This is not a finding against the control: nothing has been established against it and nothing in its favour. An evidence gap outranks a substantive conclusion here because concluding on insufficient evidence is the error the standards guard against most firmly, and inquiry alone is never sufficient, AS 2201 paragraph 50. The findings above name the gate that failed, and the open questions name what would close it.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[US] C29 G3 - reason for a testing not required conclusion (AS 2201 para 53)"
           alt="Explains that a superseded control need not be tested for this conclusion, and what that outcome does not mean">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Testing Not Required"/>
    <condition expression="'Testing not required. This control was superseded during the period by a successor that achieves the same objectives, and the successor has been in place long enough for its design to be assessed and its operation tested, so the superseded control need not be tested for this conclusion, AS 2201 paragraph 53. This is not a favourable result and it is not an evidence gap: it is a statement that the question has moved to the successor control, which must be assessed on its own facts. The superseded control must still be tested where it matters to the control risk assessment for the financial statement audit.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] R4 G3 - reason no operating determination was reached on an inconsistent record (AS 2201 paras 39 to 41)"
           alt="Explains that an inconsistent record outranks every substantive operating conclusion">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="No Operating Determination"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is greater than or equal to 1" weight="1"
               alt="At least one input inconsistency has been found for this control"/>
    <condition expression="'No operating determination. The control record contains an internal inconsistency, described in the findings above. A record that cannot be true of one control is a data quality problem rather than a judgement for this assessment to resolve, so no conclusion is published either way. Correct the record and run the assessment again. Any adverse candidate that the facts would otherwise support is reported separately as a suppressed candidate and does not disappear.'" value="%O"/>
  </relinst>
  <relinst type="has operating reason" cf="100"
           name="[CORE] C1 G6 G3 - reason no operating determination was reached for want of facts (AS 2201 para 50)"
           alt="Explains that the facts supplied do not reach any operating candidate, and points to the open questions">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="No Operating Determination"/>
    <condition expression="countRelationshipInstances(%S,'has input inconsistency',*) is equal to 0" weight="1"
               alt="No input inconsistency has been found for this control"/>
    <condition expression="countRelationshipInstances(%S,'has operating candidate',*) is equal to 0" weight="1"
               alt="No operating effectiveness candidate could be derived from the facts supplied"/>
    <condition expression="'No operating determination. The facts supplied do not reach any operating conclusion. A favourable conclusion requires every gate to be positively cleared, and an unanswered question is never a pass; an adverse conclusion requires a ground actually established. Neither is present. The open questions listed with this result name exactly what is still needed, and they are listed in the order the assessment needs them.'" value="%O"/>
  </relinst>
  <relinst type="has suppressed candidate" cf="100"
           name="[CORE] G3 - an adverse operating candidate suppressed by an evidence gap is still reported (AS 2315 paras 41 and 42)"
           alt="Reports that a substantive adverse ground was found even though the governing conclusion is that the evidence is insufficient">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Insufficient Evidence"/>
    <condition rel="has operating candidate" subject="%S" object="Not Operating Effectively" weight="1"/>
    <condition expression="'Suppressed candidate: not operating effectively. The grounds found above would independently make this control not operating effectively. They are not published as the determination because an evidence gate also failed, and an evidence gap outranks a substantive conclusion. Closing the evidence gap will not make these grounds go away, and the likely result once it is closed is an adverse conclusion rather than a favourable one. Treat this as a control in trouble, not a control awaiting paperwork.'" value="%O"/>
  </relinst>
  <relinst type="has suppressed candidate" cf="100"
           name="[CORE] G3 - a deviation candidate suppressed by an adverse conclusion is still reported (AS 2201 para 48)"
           alt="Reports that deviations were found and remain to be evaluated even though a stronger adverse ground governs the outcome">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Not Operating Effectively"/>
    <condition rel="has operating candidate" subject="%S" object="Exception Requiring Evaluation" weight="1"/>
    <condition expression="'Suppressed candidate: exception requiring evaluation. Deviations stand against this control and each one remains a deficiency to be evaluated for severity, AS 2201 paragraph 48. They are not published as the determination because a stronger ground governs. The deviations are still carried into the severity evaluation, so nothing is lost by the stronger conclusion taking precedence here.'" value="%O"/>
  </relinst>
  <relinst type="has suppressed candidate" cf="100"
           name="[CORE] G3 - an operating candidate suppressed by an inconsistent record is still reported (AS 2201 paras 39 to 41)"
           alt="Reports that an adverse ground was found even though the record is too inconsistent for a determination">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="No Operating Determination"/>
    <condition rel="has operating candidate" subject="%S" object="Not Operating Effectively" weight="1"/>
    <condition expression="'Suppressed candidate: not operating effectively. The grounds found above would independently make this control not operating effectively. They are not published as the determination because the record also contains an internal inconsistency, which outranks every substantive conclusion. Correcting the record will not make these grounds go away.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary of an operating effective conclusion (SEC Release 33-8810 II A 2)"
           alt="Gives a control owner the favourable operating outcome in plain words and says what it does not cover">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Operating Effective"/>
    <condition expression="'In plain terms: the control was done, it was done properly, and there is paperwork to prove it. Enough instances were checked, nothing went wrong in them, the right person did the work, and the evidence holds up. This covers the period and the population that were checked. It does not promise anything about instances nobody looked at.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary of an exception requiring evaluation conclusion (AS 2201 para 48)"
           alt="Gives a control owner the middle outcome in plain words and says what happens next">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Exception Requiring Evaluation"/>
    <condition expression="'In plain terms: the control slipped. Something went wrong in the instances checked, though not often enough or badly enough to say the control does not work. One slip is still a deficiency and it has to be weighed for how serious it is. The sample is not enlarged to make it go away. Find out why it happened; the cause decides the severity.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary of a not operating effectively conclusion (SEC Release 33-8810 II A 2)"
           alt="Gives a control owner the adverse outcome in plain words and says what it rests on">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Not Operating Effectively"/>
    <condition expression="'In plain terms: the control is not working. Either the problem is in how the control itself runs rather than in the particular instances looked at, or it went wrong too often, or the person doing it does not have the standing or the skills the job needs. There is enough evidence to say so. This now goes forward to be weighed for how serious it is.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary of an insufficient evidence conclusion (AS 2201 para 50)"
           alt="Tells a control owner that no answer is available and that it is not a finding against the control">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Insufficient Evidence"/>
    <condition expression="'In plain terms: there is not enough to go on. Nothing has been found against the control and nothing in its favour. Something is missing from the test: too few instances, missing paperwork, an untested report the control depends on, or months of the year nobody covered. The findings and open questions say exactly what. Fix those and run this again.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary of a testing not required conclusion (AS 2201 para 53)"
           alt="Tells a control owner that the question has moved to the replacement control">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Testing Not Required"/>
    <condition expression="'In plain terms: this control was replaced during the year, and the replacement does the same job and has been running long enough to test. So this one does not need testing for this purpose. Assess the replacement on its own facts. If the old control still matters to the external audit s view of risk, it has to be tested anyway.'" value="%O"/>
  </relinst>
  <relinst type="has operating summary" cf="100"
           name="[CORE] G7 - plain language summary where no operating determination was reached (AS 2201 para 50)"
           alt="Tells a control owner that no operating answer is available and what to do about it">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="No Operating Determination"/>
    <condition expression="'In plain terms: no answer yet. Either the record describes something that cannot be true of one control, or the facts the assessment needs have not been given. Nothing has been found for or against the control. The findings and open questions above say what to correct or supply, and the assessment will reach a conclusion once they are.'" value="%O"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[CORE] G1 - the operating effectiveness determination on the umbrella surface (AS 2201 paras 50 and A3)"
           alt="Puts the operating effectiveness conclusion {{%OC2}} on the single relationship a caller can ask on a control">
    <condition rel="has operating effectiveness conclusion" subject="%S" object="%OC2"/>
    <condition expression="'Operating effectiveness adjudication: ' + %OC2 + '. This is decision point two and it rests on the test evidence as well as the control record.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C1a G6 - the performer authority attestation is needed before an operating conclusion (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="No answer has been given about whether the performer has the authority to perform the control as designed">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'performer authority attested',*) is equal to 0" weight="1"
               alt="No answer has been recorded about the authority of the person performing the control"/>
    <condition expression="'Whether the person who performs this control has the authority to perform it as designed. Operating effectiveness means the control operates as designed AND the person performing it possesses the necessary authority and competence, SEC Release 33-8810 II A 2 and AS 2201 paragraph A3. This is part of the definition and not an extra quality test, so a clean sample cannot substitute for it and no favourable conclusion is available until it is answered.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] C1a G6 - the performer competence attestation is needed before an operating conclusion (SEC Release 33-8810 II A 2 and AS 2201 para A3)"
           alt="No answer has been given about whether the competence of the person performing the control is attested">
    <condition rel="framework is bound" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'reviewer competence attested',*) is equal to 0" weight="1"
               alt="No answer has been recorded about the competence of the person performing the control"/>
    <condition expression="'Whether the competence of the person who performs this control has been attested. Competence is the second half of the authority and competence limb of operating effectiveness, SEC Release 33-8810 II A 2 and AS 2201 paragraph A3. A control performed faithfully by someone without the knowledge to recognise what they are looking for is not an effective control, so this is asked of every control and not only of review controls.'" value="%O"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19a - benchmarking is not available to a control that is not entirely automated (AS 2201 para B28)"
           alt="Benchmarking rests on an entirely automated control not being subject to breakdown through human failure, which does not hold where a person performs any part of the control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Manual" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19a - benchmarking is not available to an IT dependent manual control (AS 2201 para B28)"
           alt="An IT dependent manual control is performed by a person using a system, so it is subject to breakdown through human failure and benchmarking does not reach it">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="IT Dependent Manual" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19 - benchmarking is not available in an initial year assessment (AS 2201 para 60)"
           alt="Benchmarking is available only in a subsequent year, because there is no established baseline in the first year a control is assessed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="is initial year assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19 - benchmarking is not available where the general IT controls are deficient (AS 2201 para B29 b)"
           alt="Benchmarking depends on effective general controls over program changes, access to programs and computer operations, and those controls are concluded deficient">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="has itgc conclusion" subject="%S" object="Deficient" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19 - benchmarking is not available where the general IT controls have not been tested (AS 2201 para B29 b)"
           alt="Benchmarking depends on general controls that have been tested and found effective, and those controls have not been tested at all">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="has itgc conclusion" subject="%S" object="Not Tested" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19 - benchmarking is not available where the general IT controls are not tested in the current period (AS 2201 para B29 b)"
           alt="Benchmarking depends on the general controls continuing to be tested, and they are not being tested in the period under review">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19 - benchmarking is not available where the control is not verified unchanged since the baseline (AS 2201 para B29 c)"
           alt="Benchmarking depends on verifying that the automated control has not changed since the baseline was established, and that verification is absent">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="control unchanged since baseline" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19c - benchmarking is not available once the baseline has aged beyond the calibrated maximum (AS 2201 para B33, practice calibration of the period)"
           alt="The baseline is {{%BA}} months old against a calibrated maximum of {{%MAXB}} months, so it must be re-established before the control can be concluded effective on it">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has baseline age months" subject="%S" object="%BA" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%BP" weight="1"/>
    <condition rel="maximum baseline age months" subject="%BP" object="%MAXB" weight="1"/>
    <condition expression="%BA is greater than %MAXB" weight="1"
               alt="The baseline is older than the calibrated maximum age"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C19b - benchmarking the program logic alone is not available where related data integrity is unaddressed (AS 2201 para B30)"
           alt="The control depends on a related file table rate or parameter held outside the program logic and the integrity of that data was not addressed, so testing the logic alone proves nothing about the control's continued operation">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="depends on related data table" subject="%S" object="true" weight="1"/>
    <condition rel="related data integrity addressed" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="baseline age within maximum" object="true" cf="100"
           name="[US] C19c - the baseline is within the calibrated maximum age (AS 2201 para B33, practice calibration of the period)"
           alt="The recorded baseline age is within the calibrated maximum, so the baseline need not be re-established for this assessment">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has baseline age months" subject="%S" object="%BAW" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%BPW" weight="1"/>
    <condition rel="maximum baseline age months" subject="%BPW" object="%MAXBW" weight="1"/>
    <condition expression="%BAW is less than or equal to %MAXBW" weight="1"
               alt="The baseline age does not exceed the calibrated maximum"/>
  </relinst>
  <relinst type="baseline age within maximum" object="false" cf="100"
           name="[US] C19c - the baseline has aged beyond the calibrated maximum (AS 2201 para B33, practice calibration of the period)"
           alt="The recorded baseline age exceeds the calibrated maximum, so the baseline must be re-established before it can carry a conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has baseline age months" subject="%S" object="%BAX" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%BPX" weight="1"/>
    <condition rel="maximum baseline age months" subject="%BPX" object="%MAXBX" weight="1"/>
    <condition expression="%BAX is greater than %MAXBX" weight="1"
               alt="The baseline age exceeds the calibrated maximum"/>
  </relinst>
  <relinst type="related data integrity cleared" object="true" cf="100"
           name="[US] C19b - the related data question does not arise where the control depends on no related data (AS 2201 para B30)"
           alt="The automated control depends on no related file table rate or parameter outside the program logic, so there is no related data integrity question to answer">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="depends on related data table" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="related data integrity cleared" object="true" cf="100"
           name="[US] C19b - the integrity of the related data the control depends on was addressed (AS 2201 para B30)"
           alt="The control depends on related data outside the program logic and the integrity of that data was addressed, so the logic and the data it reads are both covered">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="depends on related data table" subject="%S" object="true" weight="1"/>
    <condition rel="related data integrity addressed" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="related data integrity cleared" object="false" cf="100"
           name="[US] C19b - the integrity of the related data the control depends on was not addressed (AS 2201 para B30)"
           alt="The control depends on related data outside the program logic and the integrity of that data was not addressed, so the related data leg is not cleared">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="depends on related data table" subject="%S" object="true" weight="1"/>
    <condition rel="related data integrity addressed" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="false" cf="100"
           name="[US] C21 - benchmarking is not available where the institution has switched the route off (AS 2201 para 60, parameter benchmarking permitted)"
           alt="The institution's own calibration does not permit the benchmarking route, so it is unavailable whatever the facts about the control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%BP2" weight="1"/>
    <condition rel="benchmarking permitted" subject="%BP2" object="false" weight="1"/>
  </relinst>
  <relinst type="benchmarking available" object="true" cf="100"
           name="[US] C19 C19a C19b C19c - benchmarking is available where every condition is positively established (AS 2201 paras 60 B28 B29 B30 and B33)"
           alt="Every benchmarking condition is positively established for this entirely automated control, so the prior period's specific tests need not be repeated">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%BP3" weight="1"/>
    <condition rel="benchmarking permitted" subject="%BP3" object="true" weight="1"/>
    <condition rel="is initial year assessment" subject="%S" object="false" weight="1"/>
    <condition rel="has itgc conclusion" subject="%S" object="Effective" weight="1"/>
    <condition rel="itgc currently tested" subject="%S" object="true" weight="1"/>
    <condition rel="control unchanged since baseline" subject="%S" object="true" weight="1"/>
    <condition rel="baseline age within maximum" subject="%S" object="true" weight="1"/>
    <condition rel="related data integrity cleared" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[US] C19 - a reduced automated extent is not supported where benchmarking is unavailable (AS 2201 paras 60 B29 and B30)"
           alt="The extent of testing was reduced on the automated footing but a benchmarking condition is not met, so the reduced extent is not supported and the evidence does not reach a conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="uses automated single instance extent" subject="%S" object="true" weight="1"/>
    <condition rel="benchmarking available" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has itgc reliance finding" cf="100"
           name="[US] C20a - a deficient general IT control is assessed in the aggregate and not control by control (PCAOB Staff Audit Practice Alert 11 pp 27 to 28)"
           alt="States that the severity of a deficient general IT control is judged across every control and account it affects, which is wider than this one control assessment">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has itgc conclusion" subject="%S" object="Deficient"/>
    <condition expression="'Scope of this answer, and what is still owed. The general IT controls over this control are concluded deficient. A deficient general IT control does not of itself misstate an account: its effect is that it impairs every IT dependent control that relies on it. Its severity is therefore evaluated in the aggregate, across all the controls and all the accounts it affects, rather than control by control, PCAOB Staff Audit Practice Alert 11 pages 27 to 28. This determination covers this one control only. The aggregate evaluation is a separate exercise over the full population of controls that depend on the same general IT controls, and nothing here should be read as having performed it or as having concluded that the aggregate effect is no greater than what is reported for this control.'" value="%O"/>
  </relinst>
  <relinst type="has benchmarking finding" cf="100"
           name="[US] C19 C19c - the benchmarking conditions were not met and the reduced extent falls away (AS 2201 paras 60 B29 B30 and B33)"
           alt="Explains which standard the benchmarking conditions come from, that failure of any one defeats the route, and the provenance caveat on the paragraphs">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="benchmarking available" subject="%S" object="false"/>
    <condition expression="'Benchmarking is not available for this control. Benchmarking lets an entirely automated application control be concluded still effective without repeating the prior period specific tests, and it requires all of: a subsequent year rather than an initial year, AS 2201 paragraph 60; effective general controls over program changes, access to programs and computer operations; those general controls continuing to be tested in the current period; and verification that the control has not changed since the baseline, paragraph B29. Where the control depends on a related file, table, rate or parameter, the integrity of that data must be addressed too, paragraph B30, and a baseline must be re-established after a period whose length depends on the circumstances, paragraph B33. Failure of any one condition defeats the route. Provenance note: paragraphs B28 to B33 were recovered from a third-party reproduction during this build and must be checked against the PCAOB original before any reliance is placed on this route.'" value="%O"/>
  </relinst>
  <relinst type="has benchmarking finding" cf="100"
           name="[US] C19 C19a - the benchmarking conditions are met and what the route does and does not cover (AS 2201 paras 60 B28 and B29)"
           alt="Records what the favourable benchmarking conclusion rests on and the limits of what it permits">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="benchmarking available" subject="%S" object="true"/>
    <condition expression="'Benchmarking is available for this control. It is entirely automated, which is the whole basis of the route: such a control is generally not subject to breakdown through human failure, AS 2201 paragraph B28. The general controls over program changes, access to programs and computer operations are effective and continue to be tested, and the control is verified unchanged since the baseline, paragraph B29. The route permits the prior period specific tests not to be repeated. It does not conclude that the control is effective on its own: the evidence sufficiency, information reliability and roll forward questions still apply, and a change to the program, to a related data table, or to the general IT controls ends the reliance immediately. Provenance note: paragraphs B28 to B33 were recovered from a third-party reproduction during this build and must be checked against the PCAOB original.'" value="%O"/>
  </relinst>
  <relinst type="has benchmarking finding" cf="100"
           name="[US] C19b - the related data integrity leg of the benchmarking route (AS 2201 para B30)"
           alt="States that benchmarking the program logic does not reach the data the program acts on, with the standard's own rate table example">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="depends on related data table" subject="%S" object="true"/>
    <condition expression="'Related data integrity. The consistent operation of an automated control may depend on related files, tables, data and parameters: the standard s own example is an automated interest calculation that depends on the continued integrity of a rate table, AS 2201 paragraph B30. Testing the program logic says nothing about the table the program reads. Where a control of this kind is relied on, the integrity of that related data has to be addressed as well, and a change to a rate, a threshold or a mapping table can defeat the control while the program itself is untouched.'" value="%O"/>
  </relinst>
  <relinst type="has benchmarking finding" cf="100"
           name="[US] C19c - the baseline must be re-established after a period the circumstances decide (AS 2201 para B33, practice calibration of the period)"
           alt="States that the maximum baseline age is a calibrated figure and names the factors the standard says decide it">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has baseline age months" subject="%S" object="%BA2"/>
    <condition rel="applies testing policy" subject="%S" object="%BP4" weight="1"/>
    <condition rel="maximum baseline age months" subject="%BP4" object="%MAXB2" weight="1"/>
    <condition expression="'Baseline age: ' + %BA2 + ' months against a calibrated maximum of ' + %MAXB2 + ' months. The standard requires the baseline to be re-established after a period of time but states no figure, saying the length depends on the circumstances, AS 2201 paragraph B33. The maximum above is a calibration parameter of this assessment and not a requirement of the standard. The factors the paragraph names are the effectiveness of the IT control environment including software acquisition and maintenance, access controls and computer operations; the understanding of any changes to the specific programs holding the controls; the nature and timing of other related tests; the consequences of errors in the control that was benchmarked; and whether the control is sensitive to business factors that may have changed, the example being a control built to assume all amounts are positive where credits later begin to be posted.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[US] C23 - reliance is not available where the logic of the query or extract was not tested (PCAOB Staff Audit Practice Alert 11 pages 26 and 27)"
           alt="The information the control uses came from a query or extract whose logic was not tested, so its completeness cannot be established from the report itself">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true" weight="1"/>
    <condition rel="ipe query logic tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[US] C23 - reliance is not available where the report parameters were not checked (PCAOB Staff Audit Practice Alert 11 pages 26 and 27)"
           alt="The parameters used to run the report the control relies on were not checked, so the report may cover the wrong period, entity or population">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true" weight="1"/>
    <condition rel="ipe report parameters checked" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[US] C23a - no reliance where the control was tested but the IT controls over its data were not (PCAOB APA 11 page 27, AS 2201 paras 39 to 41)"
           alt="The control is IT dependent and the IT controls over the completeness and accuracy of the data it uses were not tested, so testing the control alone is not sufficient">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="IT Dependent Manual" weight="1"/>
    <condition rel="it dependent control it controls tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] C23 C23a - the depth tests the US path applies to internally produced information (PCAOB Staff Audit Practice Alert 11 pages 26 and 27)"
           alt="Names the depth tests the US path applies and says they are inspection-identified failures rather than optional refinements">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="relies on information produced by the entity" subject="%S" object="true"/>
    <condition expression="'Depth of testing for internally produced information. On this path three further tests apply beyond establishing accuracy and completeness: the general IT controls important to the applications generating the data or reports must be tested; the logic of the queries or parameters used to extract the data must be tested; and identified general IT control deficiencies over those applications must be addressed, PCAOB Staff Audit Practice Alert 11 pages 26 and 27. Where an IT dependent control is selected for testing, both the control and the IT controls over the completeness and accuracy of the data it uses must be tested, page 27. These are recorded in the alert as inspection-identified failures requiring remedy, not as refinements.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] C23b - a general IT control conclusion does not extend to data or queries outside the scope tested (PCAOB Staff Audit Practice Alert 11 page 27)"
           alt="States that customised data and queries outside the general IT control scope actually tested are not covered by that conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has unreliable relied on report" subject="%S" object="%UR"/>
    <condition rel="report within tested itgc scope" subject="%UR" object="false" weight="1"/>
    <condition expression="'Outside the general IT control scope. A report, query or spreadsheet that falls outside the general IT controls actually tested is not covered by that conclusion, and the alert records firms testing general IT controls for IT dependent controls that in fact used customised data or queries outside the scope tested, PCAOB Staff Audit Practice Alert 11 page 27. The scope of the general IT control conclusion is recorded in this assessment and is never extended by implication. Either the item is brought inside the tested scope or it is tested directly.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] C24 - other procedures required over a report whose application has ineffective general IT controls (PCAOB APA 11 pages 26 and 27)"
           alt="States that where the general IT controls over the generating application are ineffective, other procedures over the report writer or system are required">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has unreliable relied on report" subject="%S" object="%UR2"/>
    <condition rel="report has itgc conclusion" subject="%UR2" object="Deficient" weight="1"/>
    <condition expression="'Ineffective general IT controls over the generating application. A system generated report inherits the general IT control conclusion for the system that produced it. Where those controls are ineffective, other procedures over the report writer and the systems producing the spreadsheets, queries or reports are required: the alert records firms identifying ineffective general IT controls and then performing no other procedures at all, PCAOB Staff Audit Practice Alert 11 pages 26 and 27. Reconciling the report to an independent source, or testing the items it contains directly, are the usual answers.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance candidate" object="Reliance Not Available" cf="100"
           name="[US] C32 - no reliance on externally sourced electronic information neither tested for modification nor covered by tested controls (AS 1105 para 10A)"
           alt="The bank supplied information it obtained from an external source in electronic form, and neither a test of whether it was modified nor a test of the related controls was performed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="external information supplied electronically" subject="%S" object="true" weight="1"/>
    <condition rel="external information modification tested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has reliability finding" cf="100"
           name="[US] C32 - the externally sourced electronic information obligation (AS 1105 para 10A)"
           alt="States the two things the standard requires where the bank supplies externally sourced information in electronic form">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="external information supplied electronically" subject="%S" object="true"/>
    <condition expression="'Externally sourced information supplied in electronic form. Where the institution supplies information it obtained from an external source in electronic form, reliability requires an understanding of that external source and of the institution s process for receiving, maintaining and processing the information, including any modification made before delivery; and either a test of whether the information was modified, with the effect of any modification evaluated, or a test of the related controls including general IT controls and automated application controls, AS 1105 paragraph 10A. A feed is not reliable because it originated outside the institution. What matters is what happened to it in between.'" value="%O"/>
  </relinst>
  <relinst type="has reliability finding" cf="100"
           name="[US] C32 - internally sourced evidence stands lower in the reliability hierarchy (AS 1105 para 08)"
           alt="Records that the evidence came from the bank's own records rather than from a knowledgeable independent source">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%RP" weight="1"/>
    <condition rel="reliability hierarchy enabled" subject="%RP" object="true" weight="1"/>
    <condition rel="has evidence source class" subject="%S" object="Entity Internal" weight="1"/>
    <condition expression="'Reliability hierarchy: the evidence is internal. Evidence from knowledgeable sources independent of the institution is more reliable than evidence from internal sources, AS 1105 paragraph 08. Internal evidence is not thereby rejected; its reliability rises where the controls over it, including general IT controls and automated application controls, operate effectively. This is the reason the information reliability questions in this assessment matter more for an internally produced report than for a counterparty confirmation.'" value="%O"/>
  </relinst>
  <relinst type="has reliability finding" cf="100"
           name="[US] C32 - a copy or converted document stands lower in the reliability hierarchy (AS 1105 para 08)"
           alt="Records that the evidence was held as a copy or a converted document rather than as an original">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%RP2" weight="1"/>
    <condition rel="reliability hierarchy enabled" subject="%RP2" object="true" weight="1"/>
    <condition rel="has evidence form" subject="%S" object="Copy Or Conversion" weight="1"/>
    <condition expression="'Reliability hierarchy: the evidence is a copy or a conversion. An original document is more reliable than a photocopy, a facsimile or a document that has been filmed, digitised or otherwise converted, and the reliability of a converted document depends on the controls over its preparation and maintenance, AS 1105 paragraph 08. Where a conclusion rests on converted evidence the controls over the conversion and the repository are part of what supports it, and a scanned file with no controlled repository behind it is weaker evidence than it looks.'" value="%O"/>
  </relinst>
  <relinst type="has reliability finding" cf="100"
           name="[US] C32 - directly obtained evidence from an independent source is the strongest form (AS 1105 para 08)"
           alt="Records that the evidence was obtained directly from a knowledgeable source independent of the bank, the strongest standing in the hierarchy">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%RP3" weight="1"/>
    <condition rel="reliability hierarchy enabled" subject="%RP3" object="true" weight="1"/>
    <condition rel="has evidence source class" subject="%S" object="Independent External" weight="1"/>
    <condition rel="has evidence form" subject="%S" object="Directly Obtained" weight="1"/>
    <condition expression="'Reliability hierarchy: the evidence is strong. Evidence obtained directly rather than indirectly or by inference, from a knowledgeable source independent of the institution, stands at the top of the hierarchy, AS 1105 paragraph 08. That standing supports the conclusion but does not complete it: strong evidence about the wrong thing is still the wrong thing, and the sufficiency and extent questions in this assessment apply unchanged.'" value="%O"/>
  </relinst>
  <relinst type="has reliability finding" cf="100"
           name="[US] C32 - a third party restriction or disclaimer must be evaluated for its effect (AS 1105 para 08)"
           alt="Records that a restriction, limitation or disclaimer attached to the evidence and must be evaluated for its effect on reliability">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%RP4" weight="1"/>
    <condition rel="reliability hierarchy enabled" subject="%RP4" object="true" weight="1"/>
    <condition rel="third party restriction attached" subject="%S" object="true" weight="1"/>
    <condition expression="'A third party restriction attaches to the evidence. Restrictions, limitations and disclaimers placed on evidence by a third party must be evaluated for their effect on its reliability, AS 1105 paragraph 08. A disclaimer does not automatically defeat the evidence, and it is not a formality either: read what it excludes. A report expressly not to be relied on for the purpose this control puts it to is weak support for the control, however authoritative its author.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - the depth of testing practice expects for a standard or canned report (practice taxonomy, two sources)"
           alt="Names a standard report the control relies on and states the depth of testing practice expects for that class">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RC1" weight="1"/>
    <condition rel="report has class" subject="%RC1" object="Canned Report" weight="1"/>
    <condition expression="'Report class and testing depth: ' + %RC1 + ' is recorded as a standard or canned report - one that came with the application and that end users cannot modify. For that class practice expects two things: that the parameters used to run it were checked, and evidence that it is in fact unmodified. The lighter depth rests entirely on the report being unmodifiable, so evidence of that is the load bearing part and not a formality. This class taxonomy is a practice calibration of this assessment and not a requirement of any standard: the sources read publish different class names for the same idea. The sourced obligation is unchanged - the accuracy and completeness of the information must be established either directly or through the controls over it.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - the depth of testing practice expects for a customised report built in house (practice taxonomy, two sources)"
           alt="Names a customised report the control relies on and states the deeper testing practice expects for that class">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RC2" weight="1"/>
    <condition rel="report has class" subject="%RC2" object="Custom Report" weight="1"/>
    <condition expression="'Report class and testing depth: ' + %RC2 + ' is recorded as a customised report - one built or edited inside the bank to meet a specific need. For that class practice expects more than for a standard report: the parameters checked, the query logic or report definition inspected, evidence that the change went through the bank s change management process, and the output reconciled or agreed to the source. A customised report is only as reliable as the change process behind it, which is why the change evidence sits alongside the logic test rather than replacing it. This class taxonomy is a practice calibration of this assessment and not a requirement of any standard.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - the depth of testing practice expects for an ad hoc query run outside change control (practice taxonomy, two sources)"
           alt="Names an ad hoc query the control relies on and states that practice expects the fullest testing for that class on every run">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RC3" weight="1"/>
    <condition rel="report has class" subject="%RC3" object="Ad Hoc Query" weight="1"/>
    <condition expression="'Report class and testing depth: ' + %RC3 + ' is recorded as an ad hoc query - one generated outside the change controlled reports, where whoever runs it chooses the parameters. Practice treats this as the riskiest class and expects the fullest depth, on each occasion it is run rather than once: the parameters checked, the query logic tested, and completeness and accuracy established in both directions, meaning that nothing that belonged in the result is missing and nothing in it does not belong. The reason the testing repeats is that there is no change process making the next run resemble the last. This class taxonomy is a practice calibration of this assessment and not a requirement of any standard.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - a relied on report whose class is not recorded cannot be given a testing depth (practice taxonomy)"
           alt="Names a relied on report with no recorded class and says which depth question cannot be answered for it">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RC4" weight="1"/>
    <condition expression="countRelationshipInstances(%RC4,'report has class',*) is equal to 0" weight="1"
               alt="No report class is recorded against this relied on report"/>
    <condition expression="'Report class not recorded: ' + %RC4 + ' has no class against it, so this assessment states no expected testing depth for it. The depth practice expects differs sharply by class - a standard report that users cannot modify is tested more lightly than an ad hoc query whose parameters are chosen afresh on every run - so the class is worth recording. This affects the practice guidance only. The sourced obligation on the information this control relies on is judged without it, and the determination above does not depend on a class being supplied.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - a standard report whose parameters are not recorded as checked (practice taxonomy, two sources)"
           alt="States that a standard report lacks evidence that the parameters used to run it were checked">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD1" weight="1"/>
    <condition rel="report has class" subject="%RD1" object="Canned Report" weight="1"/>
    <condition expression="countRelationshipInstances(%RD1,'report parameters checked','true') is equal to 0" weight="1"
               alt="Nothing records that the parameters used to run this report were checked"/>
    <condition expression="'Expected depth not evidenced for ' + %RD1 + '. Practice expects the parameters used to run a standard report to be checked, and the record does not show it. Parameters are how a correct report produces the wrong population - the wrong period, entity or cut off - without anything about the report itself being wrong. This is a practice recommendation of this assessment, not a breach of a standard, and the reliance determination above does not turn on it.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - a standard report with no evidence that it is unmodified (practice taxonomy, two sources)"
           alt="States that a standard report lacks the evidence that it is unmodified, which is what justifies its lighter testing">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD1B" weight="1"/>
    <condition rel="report has class" subject="%RD1B" object="Canned Report" weight="1"/>
    <condition expression="countRelationshipInstances(%RD1B,'report is unmodified','true') is equal to 0" weight="1"
               alt="Nothing records that this standard report is unmodified"/>
    <condition expression="'Expected depth not evidenced for ' + %RD1B + '. A standard report is tested more lightly than any other class only because users cannot change it, and nothing in the record evidences that it is unmodified - so the class that earned the lighter treatment is itself an assumption. Of the two elements this class calls for, this is the load bearing one. This is a practice recommendation of this assessment, not a breach of a standard, and the reliance determination above does not turn on it.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - a customised report with no change management evidence behind the change (practice taxonomy, two sources)"
           alt="States that a customised report lacks evidence that the change to it went through the change management process">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD2" weight="1"/>
    <condition rel="report has class" subject="%RD2" object="Custom Report" weight="1"/>
    <condition expression="countRelationshipInstances(%RD2,'report change management evidenced','true') is equal to 0" weight="1"
               alt="Nothing records that the change to this report went through the change management process"/>
    <condition expression="'Expected depth not evidenced for ' + %RD2 + '. A report built or edited inside the bank is only as reliable as the change process behind it, and nothing records that the change went through that process. This is a practice recommendation of this assessment, not a breach of a standard. The reliance determination above does not turn on it, and nothing here says the report is wrong: it says the record does not yet show why it would be right.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - a customised report whose output is not recorded as reconciled (practice taxonomy, two sources)"
           alt="States that a customised report lacks a reconciliation of its output to the source">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD2B" weight="1"/>
    <condition rel="report has class" subject="%RD2B" object="Custom Report" weight="1"/>
    <condition expression="countRelationshipInstances(%RD2B,'report reconciled','true') is equal to 0" weight="1"
               alt="Nothing records that the output of this customised report was reconciled or agreed to the source"/>
    <condition expression="'Expected depth not evidenced for ' + %RD2B + '. Practice expects the output of a customised report to be reconciled or agreed to the source, and the record does not show it. Inspecting the query logic establishes what the report was built to do; the reconciliation establishes what it actually returned, which is why practice expects both rather than either. This is a practice recommendation of this assessment, not a breach of a standard, and the reliance determination above does not turn on it.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] I23 - an ad hoc query without the two way completeness and accuracy testing its class calls for (practice taxonomy, two sources)"
           alt="States that an ad hoc query lacks the completeness and accuracy testing its class calls for on every run">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD3" weight="1"/>
    <condition rel="report has class" subject="%RD3" object="Ad Hoc Query" weight="1"/>
    <condition expression="countRelationshipInstances(%RD3,'report completeness and accuracy tested','true') is equal to 0" weight="1"
               alt="Nothing records that the completeness and accuracy of this ad hoc query result were tested"/>
    <condition expression="'Expected depth not evidenced for ' + %RD3 + '. This is the class practice treats as riskiest - the parameters are chosen afresh each time and no change process makes one run resemble the last - and the record does not show its completeness and accuracy tested. For this class the testing is expected on every run rather than once, so an earlier clean result for the same query does not carry forward. Unlike the two lighter classes this one also engages the sourced obligation directly, because an untested ad hoc extract is untested information produced inside the bank: see the determination above rather than treating this as practice alone.'" value="%O"/>
  </relinst>
  <relinst type="has ipe reliance finding" cf="100"
           name="[US] C24 - a report on an application with ineffective general IT controls and no other procedures recorded over it (PCAOB APA 11 pages 26 and 27)"
           alt="States that no other procedures are recorded over a report whose generating application has ineffective general IT controls">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has relied on report" subject="%S" object="%RD4" weight="1"/>
    <condition rel="report has itgc conclusion" subject="%RD4" object="Deficient" weight="1"/>
    <condition expression="countRelationshipInstances(%RD4,'report other procedures performed','true') is equal to 0" weight="1"
               alt="Nothing records other procedures performed over this report despite the deficient general IT control conclusion"/>
    <condition expression="'No other procedures recorded over ' + %RD4 + '. The general IT controls over the application that produces this report are concluded ineffective, and nothing records any other procedure performed over the report itself. That exact sequence - identifying ineffective general IT controls and then performing no other procedures over the report writer or the systems producing the reports - is recorded as an inspection finding requiring remedy, PCAOB Staff Audit Practice Alert 11 pages 26 and 27. Reconciling the report to an independent source, or testing the items in it directly, are the usual answers.'" value="%O"/>
  </relinst>
  <relinst type="has entity level reliance effect" object="Reliance Available" cf="100"
           name="[US] C26 - an assertion precise entity level control can remove the need to test additional controls for that risk (AS 2201 para 23 iii)"
           alt="The entity level control relied on is designed to operate at a level of precision that would adequately prevent or detect misstatements to the relevant assertion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="entity level control relied on" subject="%S" object="true" weight="1"/>
    <condition rel="entity level control precision tier" subject="%S" object="Assertion Precise Entity Level Control" weight="1"/>
  </relinst>
  <relinst type="has entity level reliance effect" object="Reliance Not Available" cf="100"
           name="[US] C26 - a monitoring entity level control reduces but does not replace testing of other controls (AS 2201 para 23 ii)"
           alt="The entity level control relied on monitors other controls but is not precise enough by itself to address the assessed risk">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="entity level control relied on" subject="%S" object="true" weight="1"/>
    <condition rel="entity level control precision tier" subject="%S" object="Monitoring Entity Level Control" weight="1"/>
  </relinst>
  <relinst type="has entity level reliance effect" object="Reliance Not Available" cf="100"
           name="[US] C26 - an indirect entity level control is never sufficient by itself (AS 2201 paras 22 and 23 i)"
           alt="The entity level control relied on has an important but indirect effect, which influences what else is tested rather than answering the risk itself">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="entity level control relied on" subject="%S" object="true" weight="1"/>
    <condition rel="entity level control precision tier" subject="%S" object="Indirect Entity Level Control" weight="1"/>
  </relinst>
  <relinst type="has entity level reliance effect" object="Reliance Not Applicable" cf="100"
           name="[US] C26 - no entity level reliance arises where none is claimed (AS 2201 para 22)"
           alt="No entity level control is relied on for this control, so the tiered reliance question does not arise">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'entity level control relied on','true') is equal to 0" weight="1"
               alt="No reliance on an entity level control has been claimed for this control"/>
  </relinst>
  <relinst type="has entity level reliance finding" cf="100"
           name="[US] C26 - the three tiers and what each one permits (AS 2201 paras 22 and 23)"
           alt="Explains the three tiers of entity level control precision and states that this assessment has not evaluated the entity level control itself">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="entity level control relied on" subject="%S" object="true"/>
    <condition expression="'Entity level control reliance. Entity level controls vary in nature and precision, AS 2201 paragraph 23. A control with an important but indirect effect influences which other controls are selected and how they are tested, and is not sufficient on its own. A control that monitors the effectiveness of other controls and may identify breakdowns in them, without being precise enough by itself to address the assessed risk, may reduce the testing of other controls when effective. A control designed to operate at a level of precision that would adequately and timeously prevent or detect misstatements to a relevant assertion, where it sufficiently addresses the assessed risk, removes the need to test additional controls for that risk. This assessment has evaluated the effect of the relied on control and not the control itself: the tier is supplied as an input and is the institution s own conclusion.'" value="%O"/>
  </relinst>
  <relinst type="has entity level reliance finding" cf="100"
           name="[US] C26 - an assertion precise entity level control removes the need for additional testing of that risk (AS 2201 para 23 iii)"
           alt="States the consequence of relying on an entity level control at the most precise tier">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has entity level reliance effect" subject="%S" object="Reliance Available"/>
    <condition expression="'Additional controls for this risk need not be tested. Where an entity level control is designed to operate at a level of precision that would adequately prevent or detect, on a timely basis, misstatements to one or more relevant assertions, and it sufficiently addresses the assessed risk, additional controls relating to that risk need not be tested, AS 2201 paragraph 23 iii. Two cautions. Whether it sufficiently addresses the risk is a judgement supplied to this assessment, not reached by it. And the entity level control is then doing the work, so it carries the testing burden the other controls have been relieved of.'" value="%O"/>
  </relinst>
  <relinst type="has entity level reliance finding" cf="100"
           name="[US] C26 - a lower tier entity level control does not relieve the testing of this control (AS 2201 paras 22 and 23 i and ii)"
           alt="States that the tier relied on does not remove the need to test this control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has entity level reliance effect" subject="%S" object="Reliance Not Available"/>
    <condition expression="'This control still has to be tested. The entity level control relied on sits at a tier that does not remove the need to test controls addressing the risk: an indirect control influences what else is tested and is not sufficient alone, and a monitoring control may reduce the testing of other controls but is not precise enough by itself to address the assessed risk, AS 2201 paragraph 23 i and ii. Evaluation of entity level controls can increase or decrease the testing otherwise performed, paragraph 22; it does not remove it at these tiers.'" value="%O"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[US] C27 - no service auditor report and no user entity testing is insufficient evidence (SEC 33-8810 II B 5, AS 2201 para B20)"
           alt="Part of the control is performed outside the bank, no service auditor report is available and the bank has not tested its own controls over the service organisation's activities">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%SP" weight="1"/>
    <condition rel="service organisation evaluation enabled" subject="%SP" object="true" weight="1"/>
    <condition rel="depends on service organisation" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'service auditor report available','true') is equal to 0" weight="1"
               alt="No service auditor report has been put forward for the outsourced part of this control"/>
    <condition expression="countRelationshipInstances(%S,'complementary user entity controls tested','true') is equal to 0" weight="1"
               alt="No testing of the bank's own controls over the service organisation's activities has been put forward"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[US] C27 - a service auditor report that does not cover the period, with no user entity testing, is insufficient evidence (AS 2201 paras B21 and B25)"
           alt="The service auditor report does not cover the assessment period and nothing was done to bridge the gap">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%SP2" weight="1"/>
    <condition rel="service organisation evaluation enabled" subject="%SP2" object="true" weight="1"/>
    <condition rel="depends on service organisation" subject="%S" object="true" weight="1"/>
    <condition rel="service auditor report available" subject="%S" object="true" weight="1"/>
    <!-- WHY PERIOD COVERAGE IS A COUNT AND NOT A READ AT FALSE. The two   -->
    <!-- service organisation flags are injected sub-object facts that no  -->
    <!-- rule here writes and the engine never asks for. The period a      -->
    <!-- report's tests cover is the FIRST of the stated factors deciding  -->
    <!-- whether it is enough (AS 2201 para B21), so a report offered with -->
    <!-- nothing recorded about its period has not met that factor - and   -->
    <!-- reading the flag at false meant the rule only ever fired for a    -->
    <!-- caller who thought to state the gap, which is exactly the caller  -->
    <!-- who does not need telling. The count makes the unproven case the  -->
    <!-- conservative one, which is also what paragraph B25 requires as    -->
    <!-- risk increases. The narrative read at false below is deliberately -->
    <!-- left alone: it speaks only where a gap was actually recorded.     -->
    <condition expression="countRelationshipInstances(%S,'service auditor report covers period','true') is equal to 0" weight="1"
               alt="Nothing records that the service auditor report covers the assessment period"/>
    <condition expression="countRelationshipInstances(%S,'complementary user entity controls tested','true') is equal to 0" weight="1"
               alt="No testing of the bank's own controls over the service organisation's activities has been put forward to bridge the period gap"/>
  </relinst>
  <relinst type="has service organisation finding" cf="100"
           name="[US] C27 - the three evidence routes available where part of a process is outsourced (AS 2201 paras B18 to B20)"
           alt="Names the three routes the standard gives for obtaining evidence about controls at a service organisation">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="depends on service organisation" subject="%S" object="true"/>
    <condition expression="'Part of this control is performed by a service organisation. Where the service organisation s services are part of the institution s information system they are part of internal control, and its activities must be included in determining the evidence required, AS 2201 paragraphs B18 and B19. Three routes give that evidence, paragraph B20: a service auditor report on controls placed in operation together with tests of operating effectiveness, or an agreed upon procedures report describing the relevant control tests; tests of the institution s own controls over the service organisation s activities, such as independent re-performance or reconciling output reports to source documents; or tests of the controls at the service organisation performed on the institution s behalf. Outsourcing moves the work, not the responsibility.'" value="%O"/>
  </relinst>
  <relinst type="has service organisation finding" cf="100"
           name="[US] C27 - an inability to assess an outsourced process is not a permitted scope limitation (SEC Release 33-8810 II B 5)"
           alt="States that an outsourced process with no service auditor report and nothing in its place is the SEC's own example of an aspect that cannot be assessed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="depends on service organisation" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'service auditor report available','true') is equal to 0" weight="1"
               alt="No service auditor report has been put forward for the outsourced part of this control"/>
    <condition expression="'No service auditor report is available. A significant process outsourced to a service organisation where no service auditor report covering the relevant controls will be provided, and there are no controls at the institution that compensate for it, is the regulator s own worked example of an aspect of internal control that cannot be assessed, SEC Release 33-8810 section II B 5. That inability is not a permitted scope limitation: management must determine whether it is significant enough to compel the conclusion that internal control over financial reporting is not effective. This assessment reaches insufficient evidence on the control and names that determination as management s own.'" value="%O"/>
  </relinst>
  <relinst type="has service organisation finding" cf="100"
           name="[US] C27 - the factors deciding whether a service auditor report is enough (AS 2201 paras B21 B22 B23 and B25)"
           alt="Names the factors the standard gives for assessing a service auditor report and the complementary controls question">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="depends on service organisation" subject="%S" object="true"/>
    <condition rel="service auditor report available" subject="%S" object="true" weight="1"/>
    <condition expression="'A service auditor report is available. Whether it is enough turns on the period covered by its tests of controls and how that period relates to the as-of date; the scope of the examination, the applications and controls covered, and how those controls relate to the institution s own; and the test results and the opinion on operating effectiveness, AS 2201 paragraph B21. Where the report is qualified so that the objectives are met only if the user applies complementary controls contemplated in the system design, whether the institution applies those procedures must be evaluated, paragraph B22. The service auditor s reputation, competence and independence should be inquired into, paragraph B23. As risk increases, so does the need for additional evidence, paragraph B25. This assessment consumes the report and never second-guesses its contents.'" value="%O"/>
  </relinst>
  <relinst type="has service organisation finding" cf="100"
           name="[US] C27 - the period gap between the service auditor report and the as of date (AS 2201 paras B21 and B25)"
           alt="States that a report not covering the assessment period leaves a gap that the bank's own work has to bridge">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="service auditor report covers period" subject="%S" object="false"/>
    <condition rel="depends on service organisation" subject="%S" object="true" weight="1"/>
    <condition expression="'The service auditor report does not cover the assessment period. The elapsed time between the report s test period and the as-of date is one of the stated factors in deciding whether additional evidence is needed, together with the significance of the service organisation s activities, any errors identified in its processing, and the nature and significance of control changes, AS 2201 paragraphs B21 and B25. A report covering an earlier period is evidence about that period. Bridging the remainder is the institution s own work: tests of its controls over the service organisation s activities, or procedures performed at the service organisation on its behalf.'" value="%O"/>
  </relinst>
  <relinst type="has service organisation finding" cf="100"
           name="[US] C27 - the bank's own controls over the service organisation were tested (AS 2201 para B20 second route)"
           alt="Records that the bank tested its own controls over the service organisation's activities, which is the second evidence route in the standard">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="depends on service organisation" subject="%S" object="true"/>
    <condition rel="complementary user entity controls tested" subject="%S" object="true" weight="1"/>
    <condition expression="'The institution s own controls over the outsourced activity were tested. That is the second of the standard s three evidence routes and it stands on its own footing: independent re-performance, or reconciling the output reports to source documents, give evidence about the outsourced processing without a service auditor report, AS 2201 paragraph B20. Whether it is sufficient depends on how completely those controls address the processing the control depends on. A reconciliation that would not detect the error the service organisation could make is not an answer to it.'" value="%O"/>
  </relinst>
  <relinst type="has operating candidate" object="Testing Not Required" cf="100"
           name="[US] C29 - a control superseded by a tested successor need not be tested for this conclusion (AS 2201 para 53)"
           alt="The control was superseded in the period by a successor that achieves the same objectives and has been in place long enough to assess and test">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%UP" weight="1"/>
    <condition rel="superseded control route enabled" subject="%UP" object="true" weight="1"/>
    <condition rel="superseded in period" subject="%S" object="true" weight="1"/>
    <condition rel="successor achieves same objectives" subject="%S" object="true" weight="1"/>
    <condition rel="successor in place long enough to test" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has superseded control finding" cf="100"
           name="[US] C29 - the three conditions of the superseded control route (AS 2201 para 53)"
           alt="States the conditions of the route and that the question moves to the successor control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has operating candidate" subject="%S" object="Testing Not Required"/>
    <condition expression="'Superseded control. Where controls have been superseded during the period by new controls that achieve the same objectives, and the new controls have been in place long enough to permit their design to be assessed and their operating effectiveness tested, the superseded controls need not be tested for the purposes of the conclusion on internal control over financial reporting, AS 2201 paragraph 53. All three conditions are recorded as met here. The question moves to the successor control, which must be assessed on its own facts and is not covered by this result.'" value="%O"/>
  </relinst>
  <relinst type="has superseded control finding" cf="100"
           name="[US] C29 - the superseded control must still be tested where it matters to the control risk assessment (AS 2201 para 53)"
           alt="States the carve-back: the route relieves testing for the internal control conclusion only, not for the financial statement audit">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has operating candidate" subject="%S" object="Testing Not Required"/>
    <condition expression="'One carve-back. The relief is for the purposes of the conclusion on internal control over financial reporting only. The superseded control should still be tested where it is important to the control risk assessment in the audit of the financial statements, AS 2201 paragraph 53, which it usually is where it operated over a material part of the period. Treat this outcome as moving the control out of the internal control conclusion, not out of the audit.'" value="%O"/>
  </relinst>
  <relinst type="has superseded control finding" cf="100"
           name="[US] C29 - a superseded control whose successor does not qualify is tested in the ordinary way (AS 2201 para 53)"
           alt="States that where the successor does not achieve the same objectives, the superseded control is assessed in the ordinary way">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="superseded in period" subject="%S" object="true"/>
    <condition rel="successor achieves same objectives" subject="%S" object="false" weight="1"/>
    <condition expression="'Superseded, but the route is not available. The relief in AS 2201 paragraph 53 is conditional on the new controls achieving the same objectives as the controls they replaced. The replacement here is recorded as not achieving the same objectives, so the superseded control is assessed in the ordinary way on the evidence for the part of the period in which it operated. A replacement that leaves an objective unmet is itself worth looking at: the gap between the two controls is where a deficiency would sit.'" value="%O"/>
  </relinst>
  <relinst type="has superseded control finding" cf="100"
           name="[US] C29 - a successor not yet testable does not relieve the superseded control (AS 2201 para 53)"
           alt="States that where the successor has not been in place long enough to test, the relief does not arise">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="superseded in period" subject="%S" object="true"/>
    <condition rel="successor in place long enough to test" subject="%S" object="false" weight="1"/>
    <condition expression="'Superseded, but the successor cannot yet be tested. The relief in AS 2201 paragraph 53 requires the new controls to have been in place long enough for their design to be assessed and their operating effectiveness tested. That is not the position here, so nothing has yet been established about either control and the superseded control is assessed on the evidence for the part of the period in which it operated. A change made late in the period leaves both controls short of evidence, which is a planning problem and not a conclusion.'" value="%O"/>
  </relinst>
  <relinst type="has search boundary statement" cf="100"
           name="[US] C28 - no search below a material weakness is required by the standard (AS 2201 para 62)"
           alt="States that the assessor is not required to search for deficiencies less severe than a material weakness, and what follows from that">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%WP" weight="1"/>
    <condition rel="search below material weakness required" subject="%WP" object="false" weight="1"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'Search boundary. The severity of each deficiency that comes to attention must be evaluated, but there is no requirement to search for deficiencies less severe than a material weakness when planning and performing the work, AS 2201 paragraph 62, and the management guidance states no equivalent obligation. The institution has not elected to go further. Two consequences. A short list of lesser deficiencies is not evidence that few exist. And no conclusion is drawn here from the absence of a deficiency that nobody looked for.'" value="%O"/>
  </relinst>
  <relinst type="has search boundary statement" cf="100"
           name="[US] C28 - the institution has elected to search below a material weakness (AS 2201 para 62, institutional election)"
           alt="States that the institution's own methodology goes beyond the standard and searches below the material weakness threshold">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%WP2" weight="1"/>
    <condition rel="search below material weakness required" subject="%WP2" object="true" weight="1"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'Search boundary. The standard requires the severity of each deficiency that comes to attention to be evaluated and requires no search for deficiencies less severe than a material weakness, AS 2201 paragraph 62. The institution has elected to go further and to search below that threshold. That election is a calibration of this assessment and not a requirement of any standard, and it means the deficiency population here is intended to be more complete than the standard obliges.'" value="%O"/>
  </relinst>
  <relinst type="has unpredictability statement" cf="100"
           name="[US] C30 - the testing approach repeats the prior year and unpredictability is owed at programme level (AS 2201 paras 61 and B13)"
           alt="Records that the approach repeats last year's and names the ways the standard says the approach should be varied">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%NP" weight="1"/>
    <condition rel="unpredictability reporting enabled" subject="%NP" object="true" weight="1"/>
    <condition rel="prior year test approach repeated" subject="%S" object="true" weight="1"/>
    <condition expression="'Unpredictability. The approach taken to this control repeats the prior year. The nature, timing and extent of testing should be varied from year to year to introduce unpredictability and to respond to changed circumstances: testing at a different interim period, increasing or reducing the number and types of tests, or changing the combination of procedures, AS 2201 paragraph 61; in a multi-location engagement the variation extends across locations, paragraph B13. This is a programme-level obligation and no control fails because of it. It is recorded here so the pattern is visible when the programme is reviewed as a whole.'" value="%O"/>
  </relinst>
  <relinst type="has unpredictability statement" cf="100"
           name="[US] C30 - the testing approach was varied from the prior year (AS 2201 paras 61 and B13)"
           alt="Records that the approach differs from the prior year's, which is what the standard asks for at programme level">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%NP2" weight="1"/>
    <condition rel="unpredictability reporting enabled" subject="%NP2" object="true" weight="1"/>
    <condition rel="prior year test approach repeated" subject="%S" object="false" weight="1"/>
    <condition expression="'Unpredictability. The approach taken to this control differs from the prior year, which is what the standard asks: vary the nature, timing and extent of testing from year to year to introduce unpredictability and to respond to changes in circumstances, AS 2201 paragraph 61, and across locations in a multi-location engagement, paragraph B13. Knowledge from past periods may properly make the current testing less extensive or allow less persuasive evidence, paragraphs 57 to 59, but it is not a reason to run the same programme unchanged.'" value="%O"/>
  </relinst>
  <relinst type="has assessor role statement" cf="100"
           name="[US] C33 - a management or second line determination states its own footing (SEC Release 33-8810 section II)"
           alt="Names the assessor role so no reader takes a management determination for an audit conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has assessor role" subject="%S" object="Management Or Second Line"/>
    <condition expression="'This is a management determination. It is made on the footing of the management guidance, SEC Release 33-8810, under which the evidence supporting the assessment is aligned with the assessed risk and management may use self assessment, direct testing, or ongoing monitoring as the evidence of operating effectiveness. It is not an audit conclusion and must not be presented as one. An external auditor applies AS 2201 and has different evidence entitlements and a different reporting obligation.'" value="%O"/>
  </relinst>
  <relinst type="has assessor role statement" cf="100"
           name="[US] C33 - an internal audit determination states its own footing (SEC Release 33-8810 section II and AS 2201 para 71)"
           alt="Names internal audit as the assessor and distinguishes its work from the external audit conclusion">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has assessor role" subject="%S" object="Internal Audit"/>
    <condition expression="'This is an internal audit determination. It is third line work on controls management is responsible for, made on the footing of the management guidance rather than as an audit of internal control. It is not an external audit conclusion. The reports internal audit issues during the year on controls relevant to internal control over financial reporting are themselves evidence the external auditor must take into account, AS 2201 paragraph 71, so this determination may well be read by someone making a different one.'" value="%O"/>
  </relinst>
  <relinst type="has assessor role statement" cf="100"
           name="[US] C33 - an external auditor determination must take all relevant evidence into account (AS 2201 para 71 and its Note)"
           alt="Names the external auditor as the assessor and states the wider evidence obligation that comes with that role">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has assessor role" subject="%S" object="External Auditor"/>
    <condition expression="'This is an external auditor determination. The conclusion must take into account all relevant evidence, not only the results of the control tests: that includes misstatements the control failed to detect and the reports internal audit issued during the year on controls related to internal control over financial reporting, AS 2201 paragraph 71 and its Note. A clean sample sits alongside that evidence rather than above it, and a control that let a detected misstatement through is not effective because the sample was clean.'" value="%O"/>
  </relinst>
  <relinst type="has assessor role statement" cf="100"
           name="[US] C33 D3b - a misstatement the control failed to detect is evidence against it (AS 2201 paras 71 and B8)"
           alt="Records that a misstatement this control failed to detect has been identified, which is affirmative evidence against the control">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="misstatement not detected by this control" subject="%S" object="true"/>
    <condition expression="'A misstatement this control failed to detect has been identified. That is affirmative evidence about the control and must be taken into account in the conclusion, AS 2201 paragraph 71, and a misstatement detected by substantive work that the controls did not prevent or detect is a deficiency for evaluation, paragraph B8. Note the asymmetry that runs through the standards: the absence of misstatements proves nothing about a control, while the presence of one is evidence the other way.'" value="%O"/>
  </relinst>
  <relinst type="has assessor role statement" cf="100"
           name="[US] C33 - internal audit reports are part of the evidence an external auditor must consider (AS 2201 para 71 Note)"
           alt="Records that the internal audit reports for the year have not been read, which is part of the evidence this role must consider">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has assessor role" subject="%S" object="External Auditor"/>
    <condition rel="internal audit reports read" subject="%S" object="false" weight="1"/>
    <condition expression="'The internal audit reports issued during the year have not been read. For a determination made in this role the reports internal audit issued on controls related to internal control over financial reporting are evidence to be taken into account, AS 2201 paragraph 71 Note. The determination below rests on the test evidence alone, which may be incomplete. Read those reports before relying on it.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[US] I31 C16b - the interim change enquiry offered as a practice recommendation on the US path (AS 2201 para 55, with ISA UK 330 para 12 a as the fuller formulation)"
           alt="Offers the change enquiry limb as a practice recommendation, saying plainly that it is not a requirement on this path">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="applies testing policy" subject="%S" object="%EP" weight="1"/>
    <condition rel="change enquiry offered as practice" subject="%EP" object="true" weight="1"/>
    <condition rel="has interim test date" subject="%S" object="%EID" weight="1"/>
    <condition rel="interim change enquiry performed" subject="%S" object="false" weight="1"/>
    <condition expression="'Practice recommendation, not a requirement on this path. The applicable standard here requires a determination of what additional evidence the remaining period needs, AS 2201 paragraph 55, and treats changes since the interim date as a factor in that determination, paragraph 56. The international standard goes further and makes obtaining evidence about significant changes after the interim period a separate obligation in its own right, ISA UK 330 paragraph 12 a. No such enquiry is recorded for this control. On this path that is not a failure, and the recommendation is made because a change nobody asked about is the commonest reason roll forward work turns out to have tested the wrong control.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] C19 G6 - whether this is an initial year is needed before the benchmarking route can be judged (AS 2201 para 60)"
           alt="No answer has been given about whether this is the first year the control has been assessed">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'is initial year assessment',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether this is the initial year of assessment"/>
    <condition expression="'Whether this is the first year this control has been assessed. Benchmarking an automated control is available only in a subsequent year, AS 2201 paragraph 60, because there is no established baseline to compare against in the first year. Until this is answered the reduced extent that an automated control would otherwise take cannot be supported.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] C19 G6 - whether the control is unchanged since the baseline is needed before the benchmarking route can be judged (AS 2201 para B29 c)"
           alt="No answer has been given about whether the control has been verified unchanged since the baseline was established">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'control unchanged since baseline',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control is verified unchanged since the baseline"/>
    <condition expression="'Whether this automated control has been verified unchanged since the baseline was established. Benchmarking rests on that verification, AS 2201 paragraph B29 c, and the nature and extent of evidence needed to establish it depends on the circumstances including the strength of the program change controls. A compilation date report for the programs in production is the usual evidence.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] C19b G6 - whether the control depends on a related data table is needed before the benchmarking route can be judged (AS 2201 para B30)"
           alt="No answer has been given about whether the automated control depends on a related file table rate or parameter">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="has effective control type" subject="%S" object="Automated" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'depends on related data table',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control depends on a related data table"/>
    <condition expression="'Whether this automated control depends on a related file, table, rate or parameter held outside the program logic. Where it does, testing the logic alone is not enough and the integrity of that data must be addressed too, AS 2201 paragraph B30. Interest calculations, fee schedules, limit tables and mapping tables are the common cases, and the control can fail through the table while the program is untouched.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] C27 G6 - whether part of the control is outsourced is needed before its evidence can be judged (SEC Release 33-8810 II B 5 and AS 2201 para B18)"
           alt="No answer has been given about whether any part of the control is performed by a service organisation">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'depends on service organisation',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether part of the control is performed by a service organisation"/>
    <condition expression="'Whether any part of this control is performed by a service organisation outside the institution. Where a service organisation s services are part of the information system, its activities must be included in determining the evidence required, AS 2201 paragraph B18, and a significant outsourced process with no service auditor report and nothing in its place is the regulator s own example of an aspect that cannot be assessed, SEC Release 33-8810 section II B 5. Without this answer an outsourced process can be concluded effective on evidence that never reached the party doing the work.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[US] C29 G6 - whether the control was superseded in the period is needed before its outcome can be reached (AS 2201 para 53)"
           alt="No answer has been given about whether the control was replaced during the period">
    <condition rel="has framework" subject="%S" object="US ICFR"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'superseded in period',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control was superseded during the period"/>
    <condition expression="'Whether this control was replaced during the period by another control. A control superseded by a successor that achieves the same objectives, where the successor has been in place long enough to assess and test, need not be tested for the internal control conclusion, AS 2201 paragraph 53. Without this answer a replaced control is assessed as though it had run all year, and the evidence will look thin for a reason that has nothing to do with how it operated.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19e - earlier evidence may not be used for a control over a significant risk (ISA UK 330 para 15)"
           alt="The control addresses a risk the bank has determined to be a significant risk, and such a control must be tested in the current period">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="addresses significant risk" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19e - earlier evidence may not be used for a control that has changed (ISA UK 330 para 14 a)"
           alt="The control changed during the period, so the earlier testing is evidence about a control that no longer operates in that form">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="changed during the period" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19f - earlier evidence may not be used where no relevance inquiry was made (ISA UK 330 para 14)"
           alt="No inquiry was made about whether significant changes to the control have occurred since it was last tested, so the continuing relevance of the earlier evidence is not established">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="prior period relevance inquiry performed" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19f - earlier evidence may not be used where the relevance inquiry was not corroborated (ISA UK 330 para 14)"
           alt="The relevance inquiry was not combined with observation or inspection, and inquiry alone does not establish that the earlier evidence still holds">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="prior period relevance inquiry performed" subject="%S" object="true" weight="1"/>
    <condition rel="prior period relevance corroborated" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19d I25 - earlier evidence may not be used once the control has gone untested past the cap (ISA UK 330 paras 14 b and A38)"
           alt="The control has gone {{%AS}} assessments without being tested against a cap of {{%MAXAS}}, so it must be tested in this assessment">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="has assessments since last test" subject="%S" object="%AS" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%PP1" weight="1"/>
    <condition rel="maximum assessments since last test" subject="%PP1" object="%MAXAS" weight="1"/>
    <condition expression="%AS is greater than or equal to %MAXAS" weight="1"
               alt="The control has gone as many assessments without testing as the cap allows"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g - a deficient control environment defeats reliance on earlier evidence (ISA UK 330 para A39 first factor)"
           alt="The control environment is recorded as deficient, which is the first of the factors the standard says may defeat reliance on earlier evidence altogether">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="control environment deficient" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g - a deficiency in the monitoring process defeats reliance on earlier evidence (ISA UK 330 para A39 second factor)"
           alt="The bank's process for monitoring its system of internal control is recorded as deficient, so the mechanism that would have surfaced a change in this control is itself impaired">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="monitoring process deficient" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g - a significant manual element defeats reliance on earlier evidence (ISA UK 330 para A39 third factor)"
           alt="The control has a significant manual element, so how it operated in an earlier period is weaker evidence of how it operates now than it would be for an automated control">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="has significant manual element" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g - personnel changes affecting the application defeat reliance on earlier evidence (ISA UK 330 para A39 fourth factor)"
           alt="Personnel changes have significantly affected the way the control is applied, so the earlier testing describes an application of the control that has since changed">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="personnel changes affecting application" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g - circumstances indicating the control must change defeat reliance on earlier evidence (ISA UK 330 paras 13 e and A39 fifth factor)"
           alt="Circumstances have changed in a way that indicates the control itself now needs to change, so the lack of a change in it is a risk rather than a reason to rely on earlier evidence">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="circumstances indicate control must change" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] C19g C20 - deficient general IT controls defeat reliance on earlier evidence (ISA UK 330 para A39 sixth factor)"
           alt="The general IT controls are concluded deficient, which is the sixth factor the standard names and corroborates the same conclusion reached on the general IT control route">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="has itgc conclusion" subject="%S" object="Deficient" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Available" cf="100"
           name="[UK] I9c - earlier evidence may not be used where the institution has switched the route off (ISA UK 330 para 13, parameter prior period evidence permitted)"
           alt="The institution's own calibration does not permit reliance on evidence from an earlier assessment, so every control is tested in the current one">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%PP2" weight="1"/>
    <condition rel="prior period evidence permitted" subject="%PP2" object="false" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Available" cf="100"
           name="[UK] C19d C19f - earlier evidence may be used where the relevance test is met and nothing defeats it (ISA UK 330 paras 14 and A38)"
           alt="The control is unchanged, addresses no significant risk, was tested within the cap, and the continuing relevance of the earlier evidence was established by inquiry corroborated by observation or inspection">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="applies testing policy" subject="%S" object="%PP3" weight="1"/>
    <condition rel="prior period evidence permitted" subject="%PP3" object="true" weight="1"/>
    <condition rel="changed during the period" subject="%S" object="false" weight="1"/>
    <condition rel="addresses significant risk" subject="%S" object="false" weight="1"/>
    <condition rel="prior period relevance inquiry performed" subject="%S" object="true" weight="1"/>
    <condition rel="prior period relevance corroborated" subject="%S" object="true" weight="1"/>
    <condition rel="has significant manual element" subject="%S" object="false" weight="1"/>
    <condition rel="personnel changes affecting application" subject="%S" object="false" weight="1"/>
    <condition rel="circumstances indicate control must change" subject="%S" object="false" weight="1"/>
    <condition rel="has assessments since last test" subject="%S" object="%AS2" weight="1"/>
    <condition rel="maximum assessments since last test" subject="%PP3" object="%MAXAS2" weight="1"/>
    <condition expression="%AS2 is less than %MAXAS2" weight="1"
               alt="The control has gone fewer assessments without testing than the cap allows"/>
  </relinst>
  <relinst type="has prior period reliance candidate" object="Reliance Not Applicable" cf="100"
           name="[UK] C19d - the prior period question does not arise where the control was tested in this assessment (ISA UK 330 para 13)"
           alt="No reliance is placed on testing from an earlier assessment, so the prior period route is not engaged and the current testing stands on its own">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance availability" object="Reliance Not Available" cf="100"
           name="[UK] C19d C19e C19g - earlier evidence is unavailable where any defeating ground stands (ISA UK 330 paras 14 15 and A39)"
           alt="At least one ground defeats reliance on evidence from an earlier assessment, and one defeating ground is enough">
    <condition rel="has prior period reliance candidate" subject="%S" object="Reliance Not Available"/>
  </relinst>
  <relinst type="has prior period reliance availability" object="Reliance Available" cf="100"
           name="[UK] C19d - earlier evidence is available where nothing defeats it (ISA UK 330 paras 14 b and A38)"
           alt="No ground defeats reliance on the earlier evidence and every condition of the route is positively established">
    <condition expression="countRelationshipInstances(%S,'has prior period reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No ground defeats reliance on evidence from an earlier assessment"/>
    <condition rel="has prior period reliance candidate" subject="%S" object="Reliance Available"/>
  </relinst>
  <relinst type="has prior period reliance availability" object="Reliance Not Applicable" cf="100"
           name="[UK] C19d - the prior period route is not engaged for a control tested in this assessment (ISA UK 330 para 13)"
           alt="The prior period route is not engaged, so neither availability nor unavailability is stated">
    <condition expression="countRelationshipInstances(%S,'has prior period reliance candidate','Reliance Not Available') is equal to 0" weight="1"
               alt="No ground defeats reliance on evidence from an earlier assessment"/>
    <condition expression="countRelationshipInstances(%S,'has prior period reliance candidate','Reliance Available') is equal to 0" weight="1"
               alt="No favourable prior period ground was established either"/>
    <condition rel="has prior period reliance candidate" subject="%S" object="Reliance Not Applicable"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[UK] C19d C19e - candidate insufficient evidence where reliance on earlier testing is unavailable (ISA UK 330 paras 14 15 and A39)"
           alt="The conclusion was to rest on testing from an earlier assessment and that evidence may not be used, so there is no evidence covering this assessment">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has prior period reliance availability" subject="%S" object="Reliance Not Available" weight="1"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19d C19f - the prior period route and the relevance test it requires (ISA UK 330 paras 13 14 and A36)"
           alt="States the route, the relevance test and the factors the standard requires to be considered before earlier evidence is used">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true"/>
    <condition expression="'Reliance on testing from an earlier assessment. Before earlier evidence about operating effectiveness may be used, the continuing relevance of that evidence must be established by obtaining evidence about whether significant changes in the control have occurred since it was last tested, and that evidence must come from inquiry combined with observation or inspection, ISA UK 330 paragraph 14. Inquiry alone will not do. The factors to be considered in deciding whether the route is appropriate at all, and how long may elapse before a retest, are the effectiveness of the control environment, the monitoring process and the risk assessment process; whether the control is manual or automated; the effectiveness of the general IT controls; the effectiveness of the control and its application including deviations noted earlier and personnel changes; whether the lack of a change poses a risk in changed circumstances; and the extent of reliance placed on the control, paragraph 13.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19d I25 - the cap on how long a control may go untested (ISA UK 330 paras 14 b and A38)"
           alt="States the cap in assessments, that it is a requirement rather than a practice figure, and the purpose the standard gives for it">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true"/>
    <condition rel="has assessments since last test" subject="%S" object="%AS3"/>
    <condition rel="applies testing policy" subject="%S" object="%PP4" weight="1"/>
    <condition rel="maximum assessments since last test" subject="%PP4" object="%MAXAS3" weight="1"/>
    <condition expression="'Assessments since this control was last tested: ' + %AS3 + ' against a cap of ' + %MAXAS3 + '. Where a control has not changed and does not address a significant risk, it must still be tested at least once in every third assessment, and some controls must be tested in every assessment, so that reliance never rests on a single period of testing followed by two untested ones, ISA UK 330 paragraph 14 b. The interval below that cap is a matter of judgement, paragraph A38, and this assessment does not set it. Unlike the other calibrated figures in this model the cap is a requirement of the standard and not a practice convention: lengthening it is a departure from the standard.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19e - a control over a significant risk is tested every period (ISA UK 330 para 15)"
           alt="States the absolute prohibition for a control over a significant risk and that it is not subject to the cap">
    <!-- Gated on the reliance trigger, because paragraph 15 prohibits       -->
    <!-- RELYING ON earlier evidence for a significant-risk control: it says -->
    <!-- nothing about a control tested fresh in the current period, for     -->
    <!-- which the prohibition simply has no work to do. Without this        -->
    <!-- condition every UK control was asked whether it addresses a         -->
    <!-- significant risk in order to reach a finding that could not apply   -->
    <!-- to it. The part's own open-question rule for this same askable      -->
    <!-- already gates it this way.                                          -->
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="addresses significant risk" subject="%S" object="true" weight="1"/>
    <condition expression="'This control addresses a significant risk. Where reliance is to be placed on controls over a risk determined to be a significant risk, those controls must be tested in the current period, ISA UK 330 paragraph 15. The prohibition is absolute: it is not subject to the three-assessment cap, it is not cured by inquiry, and it is not relaxed by an unblemished testing history. Whether the risk is a significant risk is the bank s own determination and is supplied to this assessment rather than reached by it.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19e C19h - which changes affect the relevance of earlier evidence (ISA UK 330 paras 14 a and A37)"
           alt="States that a changed control must be tested afresh and gives the standard's own worked distinction between changes that matter and changes that do not">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true"/>
    <condition rel="changed during the period" subject="%S" object="true" weight="1"/>
    <condition expression="'The control has changed. Where there have been changes that affect the continuing relevance of the earlier evidence, the control must be tested in the current assessment, ISA UK 330 paragraph 14 a, because changes may mean there is no longer a basis for continued reliance, paragraph A37. The standard s own worked distinction is useful: a change to a system that lets the entity receive a new report from it probably does not affect the relevance of earlier evidence, whereas a change that causes data to be accumulated or calculated differently does. Evidence about the change may increase or decrease the testing needed in the current period, paragraph A36, so a change is not automatically a reason for a full retest of everything.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19g - the factors that defeat reliance on earlier evidence altogether (ISA UK 330 para A39)"
           alt="Names all six factors the standard gives and states the conservative reading this model takes of them">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has prior period reliance availability" subject="%S" object="Reliance Not Available"/>
    <condition expression="'Reliance on earlier evidence is not available. The standard names six factors that may shorten the period before a retest or result in not relying on earlier evidence at all: a deficient control environment; a deficiency in the process for monitoring the system of internal control; a significant manual element in the control; personnel changes significantly affecting how the control is applied; changing circumstances indicating the control itself needs to change; and deficient general IT controls, ISA UK 330 paragraph A39. In general the higher the risk, or the greater the reliance on the control, the shorter the elapsed period is likely to be. This model takes the conservative reading and treats a factor as defeating reliance rather than shortening an interval, because the interval below the cap is a judgement it does not make.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19d - what a favourable prior period conclusion does and does not establish (ISA UK 330 paras 14 b A38 and A40)"
           alt="States what the favourable prior period conclusion rests on and the limits of what it establishes">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has prior period reliance availability" subject="%S" object="Reliance Available"/>
    <condition expression="'Reliance on earlier evidence is available for this control. It is unchanged, addresses no significant risk, sits within the cap, and its continuing relevance was established by inquiry combined with observation or inspection, ISA UK 330 paragraph 14. Two limits. The conclusion is that the earlier testing may be used, not that the control is effective: the other gates in this assessment apply unchanged. And the route is designed to be used for some controls and not all: testing some controls in every assessment is what gives corroborating information about the continuing effectiveness of the control environment, paragraph A40, so a programme relying on earlier evidence for everything within the cap has defeated the purpose of the rule while complying with its letter.'" value="%O"/>
  </relinst>
  <relinst type="has prior period reliance finding" cf="100"
           name="[UK] C19f - inquiry alone does not establish continuing relevance (ISA UK 330 para 14)"
           alt="States that the relevance inquiry has to be corroborated by observation or inspection, and what that usually means in practice">
    <!-- The reliance trigger is read BEFORE the corroboration askable, not  -->
    <!-- after it. Both conditions are mandatory either way, so the logic is -->
    <!-- unchanged - but relationship-form conditions prune the search in    -->
    <!-- the order they are written, and with the corroboration read first   -->
    <!-- the engine asked every UK control whether its relevance inquiry was -->
    <!-- corroborated, including controls tested fresh this period that rely  -->
    <!-- on no earlier evidence at all. Corroborating the continuing         -->
    <!-- relevance of earlier evidence is meaningless where no earlier       -->
    <!-- evidence is being relied on, which is exactly what ISA (UK) 330     -->
    <!-- paragraph 14 is about.                                              -->
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="prior period relevance corroborated" subject="%S" object="false" weight="1"/>
    <condition expression="'The relevance inquiry was not corroborated. Evidence about whether significant changes have occurred must be obtained by performing inquiry COMBINED WITH observation or inspection, ISA UK 330 paragraph 14, and the standard s own illustration for an automated control is inquiry of management together with inspection of change logs to determine which controls have been changed, paragraph A36. An assurance from the control owner that nothing has changed is inquiry. It is the starting point of the test and not the whole of it.'" value="%O"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[UK] C16b - candidate insufficient evidence where no enquiry was made into changes after the interim date (ISA UK 330 para 12 a)"
           alt="Evidence was obtained at an interim date and no evidence was obtained about significant changes to the control after it, which is a requirement in its own right on this path">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has interim test date" subject="%S" object="%ID1" weight="1"/>
    <condition rel="interim change enquiry performed" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[UK] C16b - the interim obligation has two cumulative limbs on this path (ISA UK 330 para 12 a and b)"
           alt="States both limbs of the interim obligation and that the change enquiry is a requirement rather than a factor">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has interim test date" subject="%S" object="%ID2"/>
    <condition expression="'The interim obligation has two limbs and both are required. Where evidence about operating effectiveness was obtained during an interim period, evidence must be obtained about significant changes to the control after that period, AND a determination must be made of what additional evidence is needed for the remaining period, ISA UK 330 paragraph 12 a and b. The first limb is an obligation in its own right here, not merely one factor bearing on the second. The factors deciding the additional evidence are the significance of the assessed risks; which controls were tested at interim and what has changed since, including changes in the information system, the processes and the personnel; how much evidence was obtained at interim; the length of the remaining period; the extent of intended reliance; and the control environment, paragraph A34. The additional evidence may be obtained by extending the tests over the remaining period or by testing the bank s own process for monitoring its system of internal control, paragraph A35.'" value="%O"/>
  </relinst>
  <relinst type="has roll forward finding" cf="100"
           name="[UK] C16b C16c - no enquiry into changes after the interim date was made (ISA UK 330 paras 12 a and A34)"
           alt="States the consequence of the missing change enquiry and why a change of personnel is part of what it asks about">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has interim test date" subject="%S" object="%ID3" weight="1"/>
    <condition rel="interim change enquiry performed" subject="%S" object="false" weight="1"/>
    <condition expression="'No enquiry into changes after the interim date is recorded. On this path that is a failure of the first limb of paragraph 12, not a gap in judgement, and the evidence does not reach the period end however much roll forward work was done. The point of the limb is that roll forward work is only evidence about the control it was designed for: where the information system, the process or the personnel changed after the interim date, the remaining period was covered by procedures aimed at a control that had already altered. Personnel change is named explicitly among the factors, ISA UK 330 paragraph A34.'" value="%O"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[UK] C10b - candidate insufficient evidence where no specific inquiries were made into the deviations (ISA UK 330 para 17)"
           alt="Deviations were detected in a control reliance is placed on and no specific inquiries were made to understand them and their potential consequences">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC1" weight="1"/>
    <condition expression="%EC1 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition rel="deviation specific inquiries made" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has operating candidate" object="Insufficient Evidence" cf="100"
           name="[UK] C10b - candidate insufficient evidence where no determination was made about the basis for reliance (ISA UK 330 para 17 a to c)"
           alt="Deviations were detected and no determination was made about whether the tests still provide an appropriate basis for reliance, whether more testing is needed, or whether the risk must be addressed another way">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC2" weight="1"/>
    <condition expression="%EC2 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition rel="deviation basis for reliance determined" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has deviation response finding" cf="100"
           name="[UK] C10b - the three obligations a detected deviation imposes (ISA UK 330 para 17)"
           alt="States the three cumulative obligations the standard imposes once a deviation is detected">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has effective exception count" subject="%S" object="%EC3"/>
    <condition expression="%EC3 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition expression="'A detected deviation imposes three obligations. Specific inquiries must be made to understand the deviations and their potential consequences; a determination must then be made whether the tests performed still provide an appropriate basis for reliance on the control, whether additional tests of controls are necessary, or whether the potential risks must instead be addressed by substantive procedures; and the procedures must be changed accordingly, ISA UK 330 paragraph 17 a to c. The three are cumulative and the first is not optional: a deviation whose cause nobody established cannot support any of the three determinations that follow. Note what the paragraph does not offer. There is no route by which a larger sample dilutes a deviation away.'" value="%O"/>
  </relinst>
  <relinst type="has deviation response finding" cf="100"
           name="[UK] C10b - no specific inquiries were made into the deviations detected (ISA UK 330 para 17)"
           alt="States that the specific inquiries were not made and what has to happen before any determination can be reached">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC4" weight="1"/>
    <condition expression="%EC4 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition rel="deviation specific inquiries made" subject="%S" object="false" weight="1"/>
    <condition expression="'No specific inquiries were made. Until the deviations and their potential consequences are understood, none of the three determinations the standard requires can be reached, ISA UK 330 paragraph 17. The practical consequence is that this assessment reports an evidence gap and not a finding against the control: nothing adverse has been established about the control, and nothing favourable either. Establish the cause, then assess again.'" value="%O"/>
  </relinst>
  <relinst type="has deviation response finding" cf="100"
           name="[UK] C10b - no determination was made about the basis for reliance (ISA UK 330 para 17 a to c)"
           alt="States that the determination among the three alternatives has not been made and names them">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC5" weight="1"/>
    <condition expression="%EC5 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition rel="deviation basis for reliance determined" subject="%S" object="false" weight="1"/>
    <condition expression="'No determination has been recorded. Once deviations are detected the standard requires a choice to be made and recorded between three alternatives: the tests already performed still provide an appropriate basis for reliance on the control; additional tests of controls are necessary; or the potential risks of misstatement must be addressed using substantive procedures instead, ISA UK 330 paragraph 17 a to c. Leaving the question open is not one of the three. The determination is the bank s to make and this assessment asks for it rather than making it.'" value="%O"/>
  </relinst>
  <relinst type="has deviation response finding" cf="100"
           name="[UK] C10c - what a deviation rate means and what causes deviations (ISA UK 330 para A42)"
           alt="States that effective operation admits some deviations and names the causes and the comparison that matters">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has effective exception count" subject="%S" object="%EC6"/>
    <condition expression="%EC6 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition expression="'What a deviation means. The concept of effective operation recognises that some deviations in the way a control is applied may occur, and names their common causes: changes in key personnel, significant seasonal fluctuations in transaction volume, and human error, ISA UK 330 paragraph A42. It is the detected rate of deviation, in particular compared with the rate expected, that may show the control cannot be relied on. That is the same rate-based comparison this assessment applies, reached independently by a second primary source, and it is the reason a single deviation is evaluated rather than ignored and equally is not treated as proof the control has failed.'" value="%O"/>
  </relinst>
  <relinst type="has deviation response finding" cf="100"
           name="[UK] C10b - the deviation response obligations were met (ISA UK 330 para 17)"
           alt="Records that the inquiries were made and the determination recorded, and states what still follows from them">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC7" weight="1"/>
    <condition expression="%EC7 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition rel="deviation specific inquiries made" subject="%S" object="true" weight="1"/>
    <condition rel="deviation basis for reliance determined" subject="%S" object="true" weight="1"/>
    <condition expression="'The deviation response obligations are met. Specific inquiries were made into the deviations and their potential consequences, and a determination has been recorded, ISA UK 330 paragraph 17. The third limb remains work rather than a fact this assessment can see: the procedures have to be changed to match whatever was determined, and where the determination was that substantive procedures must address the risk, those procedures are outside this assessment. Meeting the response obligations does not make the deviation disappear; the deviation is still evaluated for its severity.'" value="%O"/>
  </relinst>
  <relinst type="has control judgement input" object="Management" cf="100"
           name="[UK] C19e G5 - whether the risk is a significant risk is the bank's own determination (ISA UK 330 para 15)"
           alt="Names the judgement supplied as an input and the role that should own it">
    <!-- Same gate as the C19e finding this record attributes: the judgement  -->
    <!-- is named where the finding can arise, and not sought from a control -->
    <!-- that relies on no earlier evidence.                                 -->
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition rel="addresses significant risk" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has control judgement input" object="The Second Line Controls Function" cf="100"
           name="[UK] C19d G5 - the retest interval below the cap is a judgement this assessment does not make (ISA UK 330 para A38)"
           alt="Names the interval judgement as an input and the function that should own it">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true"/>
  </relinst>
  <relinst type="has applied instrument" object="ISA UK 330 Revised July 2017 Updated September 2025" cf="100"
           name="[UK] C19d G8 - ISA UK 330 is applied where reliance rests on testing from an earlier assessment (ISA UK 330 paras 13 to 15)"
           alt="Names the revision of ISA UK 330 applied, because reliance on evidence from an earlier assessment was evaluated">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] C19d G6 - whether reliance rests on earlier testing is needed before the evidence can be judged (ISA UK 330 para 13)"
           alt="No answer has been given about whether the conclusion rests on testing carried out in an earlier assessment">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior period evidence relied on',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether reliance is placed on testing from an earlier assessment"/>
    <condition expression="'Whether the conclusion on this control rests on testing carried out in an earlier assessment rather than in this one. The route exists and is legitimate, ISA UK 330 paragraphs 13 and 14, but it carries its own conditions: a relevance test, a cap of testing at least once in every third assessment, and two cases where it is never available. Without this answer a control last tested three assessments ago looks the same here as one tested last month.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] C19e G6 - whether the control addresses a significant risk is needed before earlier evidence can be used (ISA UK 330 para 15)"
           alt="No answer has been given about whether the control addresses a risk the bank has determined to be significant">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period evidence relied on" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'addresses significant risk',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the control addresses a significant risk"/>
    <condition expression="'Whether this control addresses a risk the bank has determined to be a significant risk. Controls over a significant risk must be tested in the current period and earlier evidence may never be used for them, ISA UK 330 paragraph 15. The determination of what is a significant risk is the bank s own and is supplied to this assessment, so the answer has to come from the risk assessment rather than from the control record.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] C19f G6 - how the continuing relevance of the earlier evidence was established (ISA UK 330 para 14)"
           alt="No answer has been given about whether the relevance inquiry was combined with observation or inspection">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="prior period relevance inquiry performed" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prior period relevance corroborated',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the relevance inquiry was corroborated"/>
    <condition expression="'Whether the relevance inquiry was combined with observation or inspection. The standard requires inquiry COMBINED WITH observation or inspection to confirm the understanding of the control, ISA UK 330 paragraph 14, and for an automated control the illustration is inquiry of management together with inspection of change logs, paragraph A36. Inquiry alone does not establish continuing relevance, so without this answer the route cannot be cleared.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] C10b G6 - what the specific inquiries into the deviations established (ISA UK 330 para 17)"
           alt="Deviations were detected and no answer has been given about whether specific inquiries were made into them">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="exception position clear" subject="%S" object="false" weight="1"/>
    <condition rel="has effective exception count" subject="%S" object="%EC8" weight="1"/>
    <condition expression="%EC8 is greater than 0" weight="1"
               alt="At least one deviation was detected in the sample"/>
    <condition expression="countRelationshipInstances(%S,'deviation specific inquiries made',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether specific inquiries were made into the deviations"/>
    <condition expression="'Whether specific inquiries were made to understand the deviations found and their potential consequences. This is the first of the three obligations a detected deviation imposes, ISA UK 330 paragraph 17, and the other two depend on it: nothing can be determined about the basis for reliance until the cause of the deviation is understood. Answering this usually means talking to the person who performed the control, not re-reading the test file.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] C16b G6 - whether changes after the interim date were enquired into (ISA UK 330 para 12 a)"
           alt="An interim test is recorded and no answer has been given about whether evidence was obtained about changes after it">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has interim test date" subject="%S" object="%ID4" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'interim change enquiry performed',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether changes after the interim date were enquired into"/>
    <condition expression="'Whether evidence was obtained about significant changes to this control after the interim test date. On this path that is a requirement in its own right and not merely a factor bearing on how much roll forward work is needed, ISA UK 330 paragraph 12 a. Without it the roll forward work may have covered the remaining period with procedures designed for a control that had already changed.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D2 - the likelihood judgement is taken as supplied and is not derived (AS 2201 paras 63 and 65, ISA UK 265 para 6)"
           alt="Records the likelihood judgement supplied and states that no rule in this model derives it">
    <condition rel="has likelihood" subject="%S" object="%LK"/>
    <condition expression="'Likelihood of misstatement, taken as supplied: ' + %LK + '. Severity depends on whether there is a reasonable possibility that the control will fail to prevent or detect a misstatement, and on the magnitude of the potential misstatement. The likelihood is a judgement about the control and the circumstances, and no fetched source reduces it to a test a model can apply, so it is supplied to this assessment rather than reached by it. The factors the standards name as bearing on it are the nature of the financial statement amounts or transactions exposed; the susceptibility of the related asset or liability to loss or fraud; the subjectivity, complexity and judgement involved; the cause and frequency of known or detected exceptions; the interaction of this deficiency with others; and the possible future consequences.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="Management" cf="100"
           name="[CORE] D2 G5 - the likelihood judgement should be owned by management (AS 2201 para 65)"
           alt="Names the likelihood judgement as an input and the role that should own it">
    <condition rel="has likelihood" subject="%S" object="%LK2"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D2 G6 - the likelihood judgement is needed before severity can be evaluated (AS 2201 paras 63 and 65)"
           alt="No likelihood judgement has been supplied for this deficiency">
    <condition rel="has deficiency type" subject="%S" object="%DT1"/>
    <condition expression="countRelationshipInstances(%S,'has likelihood',*) is equal to 0" weight="1"
               alt="No likelihood judgement has been supplied for this deficiency"/>
    <condition expression="'The likelihood that this deficiency results in a misstatement - remote, reasonably possible or probable. Severity cannot be evaluated without it: likelihood and magnitude are the two axes of every severity definition in both frameworks. The judgement is management s and this assessment asks for it rather than making it.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D3 - the magnitude judgement is consumed as a band and never as a figure (AS 2201 paras 63 and 66)"
           alt="Records the magnitude band supplied and states that the model consumes bands rather than monetary amounts">
    <condition rel="has magnitude band" subject="%S" object="%MG"/>
    <condition expression="'Magnitude of the potential misstatement, taken as supplied: ' + %MG + '. The factors the standards name are the financial statement amounts or transaction totals exposed to the deficiency, and the volume of activity in the account or class of transactions exposed in the current period or expected in future periods. This assessment consumes the BAND and never a monetary figure: the institution maps its own materiality to the bands, and no amount, percentage or threshold from its materiality paper enters this model. One consequence worth stating. Because the mapping happens outside, two institutions supplying the same band may mean different amounts by it, and the band is only as good as the mapping behind it.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="Management" cf="100"
           name="[CORE] D3 G5 - the magnitude band should be owned by management (AS 2201 para 66)"
           alt="Names the magnitude band as an input and the role that should own it">
    <condition rel="has magnitude band" subject="%S" object="%MG2"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D3 G6 - the magnitude band is needed before severity can be evaluated (AS 2201 paras 63 and 66)"
           alt="No magnitude band has been supplied for this deficiency">
    <condition rel="has deficiency type" subject="%S" object="%DT2"/>
    <condition expression="countRelationshipInstances(%S,'has magnitude band',*) is equal to 0" weight="1"
               alt="No magnitude band has been supplied for this deficiency"/>
    <condition expression="'The magnitude band of the potential misstatement this deficiency exposes. Supply the band your own materiality mapping gives, not an amount: this assessment consumes bands and holds no monetary figures. Severity cannot be evaluated without it.'" value="%O"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] D3a - the maximum overstatement is the recorded amount but an understatement may be larger (AS 2201 para 67)"
           alt="States the asymmetry between an overstatement ceiling and an understatement exposure, and the direction supplied">
    <condition rel="deficiency of control" subject="%S" object="%DC1"/>
    <condition rel="has framework" subject="%DC1" object="US ICFR" weight="1"/>
    <condition rel="has direction of exposure" subject="%S" object="%DX1" weight="1"/>
    <condition expression="'Direction of exposure, taken as supplied: ' + %DX1 + '. The maximum amount by which an account balance or total of transactions can be OVERSTATED is generally the recorded amount, while understatements could be larger, AS 2201 paragraph 67. The asymmetry matters because a ceiling that is right for an overstatement is wrong for an understatement, and applying it would understate severity. No rule in this model caps a magnitude band at a recorded-amount ceiling in either direction: the band supplied is the band evaluated. The same paragraph records that the probability of a small misstatement is generally greater than that of a large one, which is an aid to the likelihood judgement and quantifies nothing, so it is recorded in the calibration guide and is not applied as a rule here.'" value="%O"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] D3a - an understatement exposure has no recorded-amount ceiling (AS 2201 para 67)"
           alt="States that the exposure includes understatement, so no recorded-amount ceiling applies to the magnitude">
    <condition rel="has direction of exposure" subject="%S" object="Understatement"/>
    <condition rel="deficiency of control" subject="%S" object="%DC2" weight="1"/>
    <condition rel="has framework" subject="%DC2" object="US ICFR" weight="1"/>
    <condition expression="'The exposure is an understatement, so no recorded-amount ceiling applies. An understatement could be larger than the amount currently recorded, AS 2201 paragraph 67, which is why the recorded figure is not evidence of the worst case. Where the magnitude band was set by reference to the amount on the face of the records, review it: for an understatement that reference point is the wrong one.'" value="%O"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] D3a - an exposure in both directions is evaluated on the understatement limb (AS 2201 para 67)"
           alt="States that where the exposure runs in both directions the understatement limb governs the magnitude judgement">
    <condition rel="has direction of exposure" subject="%S" object="Overstatement And Understatement"/>
    <condition rel="deficiency of control" subject="%S" object="%DC3" weight="1"/>
    <condition rel="has framework" subject="%DC3" object="US ICFR" weight="1"/>
    <condition expression="'The exposure runs in both directions. Where a deficiency could produce either an overstatement or an understatement, the understatement limb governs the magnitude judgement, because the overstatement ceiling of the recorded amount gives no comfort about the other side, AS 2201 paragraph 67. In practice this is the common case for a reconciliation or completeness control, where an unrecorded item and a wrongly recorded one are both in point.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="Management" cf="100"
           name="[US] D3a G5 - the direction of exposure should be owned by management (AS 2201 para 67)"
           alt="Names the direction of exposure as an input and the role that should own it">
    <condition rel="has direction of exposure" subject="%S" object="%DX2"/>
    <condition rel="deficiency of control" subject="%S" object="%DC4" weight="1"/>
    <condition rel="has framework" subject="%DC4" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[US] D3a G6 - the direction of exposure is needed before the magnitude band can be read (AS 2201 para 67)"
           alt="No direction of exposure has been supplied, so the magnitude band cannot be read safely">
    <condition rel="deficiency of control" subject="%S" object="%DC5"/>
    <condition rel="has framework" subject="%DC5" object="US ICFR" weight="1"/>
    <condition rel="has magnitude band" subject="%S" object="%MG3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has direction of exposure',*) is equal to 0" weight="1"
               alt="No direction of exposure has been supplied for this deficiency"/>
    <condition expression="'Whether this deficiency exposes the figures to overstatement, understatement, or both. The maximum overstatement is generally the recorded amount while an understatement could be larger, AS 2201 paragraph 67, so a magnitude band set without the direction in mind may have been anchored on a ceiling that does not apply. The answer does not change any rule here; it changes whether the band you supplied is the right one.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D3b - a misstatement the control failed to prevent or detect is a deficiency for evaluation (AS 2201 para B8 and ISA UK 330 para 16)"
           alt="States that a misstatement found by substantive work and not stopped by the control is itself a deficiency to be evaluated">
    <condition rel="material misstatement not detected by control" subject="%S" object="true"/>
    <condition expression="'A misstatement was detected that this control did not prevent or detect. That is a deficiency for evaluation in its own right, however the control performed on the instances tested: a misstatement detected by substantive procedures that the controls did not catch is a deficiency, AS 2201 paragraph B8, and misstatements detected by substantive procedures must be evaluated as indicating that controls are not operating effectively, ISA UK 330 paragraph 16. Note the asymmetry the two paragraphs make between them. The absence of detected misstatements is not evidence that the control is effective; the presence of one is evidence that it is not. A clean sample does not answer a known failure.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D3b G6 - whether a misstatement escaped this control is needed before severity can be evaluated (AS 2201 para B8 and ISA UK 330 para 16)"
           alt="No answer has been recorded about whether a misstatement escaped this control">
    <condition rel="has deficiency type" subject="%S" object="%DT3"/>
    <condition expression="countRelationshipInstances(%S,'material misstatement not detected by control',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether a misstatement escaped this control"/>
    <condition expression="'Whether a misstatement was found that this control should have prevented or detected and did not. It is affirmative evidence about the control and bears directly on both the likelihood and the magnitude judgements, AS 2201 paragraph B8 and ISA UK 330 paragraph 16. A deficiency raised from a clean-looking test file reads very differently once a real misstatement is known to have escaped the control.'" value="%O"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D4 - no compensating control effect where none exists (SEC Release 33-8810 footnote 49)"
           alt="No compensating control has been identified for this deficiency, so nothing reduces its severity">
    <condition rel="compensating control exists" subject="%S" object="false"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D5 I13 - an untested compensating control reduces nothing (AS 2201 para 68 and APA 11 pages 34 to 35, conservative default)"
           alt="A compensating control has been identified but has not been tested effective, and an untested control is an assertion rather than evidence">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%CP1" weight="1"/>
    <condition rel="compensating control must be tested" subject="%CP1" object="true" weight="1"/>
    <condition rel="compensating control tested effective" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D4 - no compensating control effect where its precision is inadequate for the magnitude (SEC Release 33-8810 II B 1 and AS 2201 para 68)"
           alt="The compensating control does not operate at a level of precision that would prevent or detect a misstatement of the magnitude in question">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="compensating control precision adequate" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D5 - no compensating control effect where it addresses a different assertion (APA 11 pages 34 to 35)"
           alt="The compensating control does not address the same assertion as the control that failed, so it does not accomplish the failed control's objective">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="compensating control same assertion" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D6 I13 - no compensating control effect where the institution has switched the effect off (AS 2201 para 68, parameter compensating control effect permitted)"
           alt="The institution's own calibration does not permit a compensating control to reduce severity, so no reduction is applied">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%CP2" weight="1"/>
    <condition rel="compensating control effect permitted" subject="%CP2" object="false" weight="1"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D5 I13 - a compensating control whose testing is unanswered reduces nothing (AS 2201 para 68 and APA 11 pages 34 to 35, conservative default)"
           alt="A compensating control has been identified but nothing records whether it was tested effective, and an untested or unevidenced control reduces nothing">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%CU1" weight="1"/>
    <condition rel="compensating control must be tested" subject="%CU1" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'compensating control tested effective',*) is equal to 0" weight="1"
               alt="Whether the compensating control was tested effective is not recorded"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D4 - a compensating control whose precision is unanswered reduces nothing (SEC Release 33-8810 II B 1 and AS 2201 para 68, conservative default)"
           alt="A compensating control has been identified but nothing records whether its precision is adequate for the magnitude in question">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'compensating control precision adequate',*) is equal to 0" weight="1"
               alt="Whether the compensating control is precise enough for the magnitude in question is not recorded"/>
  </relinst>
  <relinst type="has compensating control effect" object="false" cf="100"
           name="[CORE] D5 - a compensating control whose assertion is unanswered reduces nothing (APA 11 pages 34 to 35, conservative default)"
           alt="A compensating control has been identified but nothing records whether it addresses the same assertion as the control that failed">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'compensating control same assertion',*) is equal to 0" weight="1"
               alt="Whether the compensating control addresses the same assertion as the control that failed is not recorded"/>
  </relinst>
  <relinst type="has compensating control effect" object="true" cf="100"
           name="[CORE] D4 D6 - a compensating control reduces severity only on all four legs (SEC Release 33-8810 II B 1 and footnote 49, AS 2201 para 68)"
           alt="The compensating control exists, has been tested effective, is precise enough for the magnitude in question and addresses the same assertion, so it may reduce severity">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%CP3" weight="1"/>
    <condition rel="compensating control effect permitted" subject="%CP3" object="true" weight="1"/>
    <condition rel="compensating control tested effective" subject="%S" object="true" weight="1"/>
    <condition rel="compensating control precision adequate" subject="%S" object="true" weight="1"/>
    <condition rel="compensating control same assertion" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has compensating control finding" cf="100"
           name="[CORE] D4 - what a compensating control is and the four legs it must meet (SEC Release 33-8810 II B 1 and footnote 49, AS 2201 para 68)"
           alt="States the definition of a compensating control and the four legs this model requires before it reduces severity">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition expression="'A compensating control has been identified. A compensating control is one that accomplishes the objective of another control that did not function properly, SEC Release 33-8810 footnote 49, and to have a mitigating effect on severity it must operate at a level of precision that would prevent or detect a misstatement that could be material, section II B 1, the effect of compensating controls being something the assessor should evaluate, AS 2201 paragraph 68. This model requires four legs before any reduction: the control exists; it has been tested effective; its precision is adequate for the magnitude in question; and it addresses the same assertion as the control that failed. The second leg is the conservative reading of an instruction to evaluate, and it is exposed as a calibration parameter.'" value="%O"/>
  </relinst>
  <relinst type="has compensating control finding" cf="100"
           name="[CORE] D5 - an untested compensating control is an assertion and not evidence (AS 2201 para 68 and APA 11 pages 34 to 35)"
           alt="States why an untested compensating control reduces nothing and what would be needed to change that">
    <condition rel="compensating control tested effective" subject="%S" object="false"/>
    <condition rel="compensating control exists" subject="%S" object="true" weight="1"/>
    <condition expression="'The compensating control has not been tested effective, so it reduces nothing. Practice guidance is explicit that a compensating control must itself be tested, and must address the same relevant assertion as the control that failed, APA 11 pages 34 and 35. The reason is simple enough: a control nobody has tested is a description of an intention. Test it over the same period and for the same assertion, then the reduction can be considered. Until then the severity stands on the failed control alone.'" value="%O"/>
  </relinst>
  <relinst type="has compensating control finding" cf="100"
           name="[CORE] D4 - the precision a compensating control must have (SEC Release 33-8810 II B 1 and AS 2201 para 68)"
           alt="States the precision test a compensating control must meet and that precision is judged against the magnitude in question">
    <condition rel="compensating control precision adequate" subject="%S" object="false"/>
    <condition rel="compensating control exists" subject="%S" object="true" weight="1"/>
    <condition expression="'The compensating control is not precise enough. To have a mitigating effect it must operate at a level of precision that would prevent or detect a misstatement that could be material, SEC Release 33-8810 section II B 1. Precision is judged against the magnitude in question and not in the abstract: a review performed at a level of aggregation far above the exposure, or against a threshold far above it, will not detect the misstatement the failed control was there to stop. A monthly review of a total that would absorb the error without visible change is the usual example.'" value="%O"/>
  </relinst>
  <relinst type="has compensating control finding" cf="100"
           name="[CORE] D5 - a compensating control must address the same assertion as the control that failed (APA 11 pages 34 to 35)"
           alt="States that a control addressing a different assertion does not accomplish the failed control's objective">
    <condition rel="compensating control same assertion" subject="%S" object="false"/>
    <condition rel="compensating control exists" subject="%S" object="true" weight="1"/>
    <condition expression="'The compensating control addresses a different assertion. A compensating control accomplishes the OBJECTIVE of the control that did not function properly, so it has to address the same relevant assertion, APA 11 pages 34 and 35. A strong control over the existence of a balance does not compensate for a failure of its completeness, and an approval control does not compensate for a failure of valuation. The objective has to match, not merely the account.'" value="%O"/>
  </relinst>
  <relinst type="has compensating control finding" cf="100"
           name="[CORE] D4 D6 - what a qualifying compensating control does and does not do (AS 2201 para 68)"
           alt="States what follows from a qualifying compensating control and the limits of the reduction it supports">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition expression="'The compensating control qualifies and may reduce the severity of this deficiency. Two limits are worth stating. It reduces severity; it does not remove the deficiency, which remains a deficiency to be evaluated, communicated where owed, and remediated. And the reduction is bounded by the compensating control s own precision: a control precise enough to catch a misstatement of one size is not evidence about a larger one. Where the reduction is relied on, the compensating control carries the burden the failed control has been relieved of, and it should be tested accordingly in the next assessment.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="Management" cf="100"
           name="[CORE] D4 G5 - the precision of a compensating control is a judgement management should own (AS 2201 para 68)"
           alt="Names the compensating control precision conclusion as an input and the role that should own it">
    <condition rel="compensating control precision adequate" subject="%S" object="%CPA"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D4 G6 - whether a compensating control exists is needed before severity is settled (SEC Release 33-8810 footnote 49 and AS 2201 para 68)"
           alt="No answer has been recorded about whether a compensating control exists for this deficiency">
    <condition rel="has deficiency type" subject="%S" object="%DT4"/>
    <condition expression="countRelationshipInstances(%S,'compensating control exists',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether a compensating control exists"/>
    <condition expression="'Whether another control accomplishes the objective of the control that failed. A compensating control that exists, is tested effective, is precise enough for the magnitude in question and addresses the same assertion may reduce the severity of this deficiency, SEC Release 33-8810 footnote 49 and section II B 1, AS 2201 paragraph 68. Without an answer this assessment applies no reduction, which is the conservative direction and may overstate the severity where a qualifying control does in fact exist.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D5 G6 - whether the compensating control has been tested is needed before it can reduce severity (AS 2201 para 68 and APA 11 pages 34 to 35)"
           alt="A compensating control has been identified and no answer has been recorded about whether it was tested effective">
    <condition rel="compensating control exists" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'compensating control tested effective',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the compensating control was tested effective"/>
    <condition expression="'Whether the compensating control has itself been tested and found effective. An untested compensating control reduces nothing in this model, which is the conservative reading of the instruction to evaluate the effect of compensating controls, AS 2201 paragraph 68, and practice guidance is explicit that the compensating control must itself be tested, APA 11 pages 34 and 35. The requirement is exposed as a calibration parameter, so an institution that reads the instruction differently can change it deliberately rather than by accident.'" value="%O"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D8a - health in one component does not mitigate a shortfall in another (COSO 2013 executive summary and COSO Internal Control FAQs 2013)"
           alt="States that no compensating-component argument is admissible and that only a compensating control may reduce severity">
    <condition rel="for coso component" subject="%S" object="%CC1"/>
    <condition expression="'No compensating-component argument is available. Internal control is effective only where all five components are present and functioning together, so a severe shortfall in one component is not mitigated by the presence and functioning of the others, COSO 2013 executive summary. Deficiencies must be aggregated ACROSS components rather than evaluated only within one, because the components operate together only where the aggregated deficiencies do not amount to a severe shortfall, COSO Internal Control FAQs. The practical consequence for this deficiency: a strong control environment or an effective monitoring function elsewhere is not a reason to reduce its severity. Only a compensating control meeting the four legs set out above can do that.'" value="%O"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[CORE] D1 G6 - a deficiency record is needed before severity can be evaluated (AS 2201 paras 62 and A3)"
           alt="A design or operating failure has raised a deficiency for evaluation and no deficiency record has been supplied against this control">
    <condition rel="has deficiency trigger" subject="%S" object="%DTR"/>
    <condition expression="countRelationshipInstances(%S,'has deficiency',*) is equal to 0" weight="1"
               alt="No deficiency record has been supplied against this control"/>
    <condition expression="'A deficiency has arisen on this control and no deficiency record has been supplied for it. The severity of each deficiency that comes to attention must be evaluated, AS 2201 paragraph 62, and a deficiency exists where the design or operation of a control does not allow the objective to be met, paragraph A3. Supply a deficiency record with its likelihood, magnitude band and direction of exposure, and the severity evaluation will run. Until then this assessment reports the failure and classifies nothing.'" value="%O"/>
  </relinst>
  <relinst type="has judgement statement" cf="100"
           name="[CORE] D1 - a design failure and an operating failure are both deficiencies for evaluation (AS 2201 para A3)"
           alt="States the two limbs of the definition of a deficiency and that each reaches severity evaluation">
    <condition rel="has deficiency trigger" subject="%S" object="%DTR2"/>
    <condition expression="'A deficiency has arisen for evaluation: ' + %DTR2 + '. A deficiency exists where the design or operation of a control does not allow management or employees, in the normal course of performing their assigned functions, to prevent or detect misstatements on a timely basis, AS 2201 paragraph A3. The paragraph has two limbs and both reach severity evaluation: a design deficiency exists where a control necessary to meet the objective is missing, or an existing control is not properly designed so that the objective would not be met even if it operated as designed; an operating deficiency exists where a properly designed control does not operate as designed, or the person performing it lacks the necessary authority or competence.'" value="%O"/>
  </relinst>
  <relinst type="assertion has deficiency" cf="100"
           name="[CORE] D7 D8 - projects a deficiency onto the assertion it affects (SEC Release 33-8810 II B 1 and AS 2201 para 65 Note 2)"
           alt="Carries a deficiency onto the assertion it affects, so the assertion can be looked at as a whole">
    <condition rel="for assertion" subject="%O" object="%S"/>
  </relinst>
  <relinst type="line item has deficiency" cf="100"
           name="[CORE] D7 D8 - projects a deficiency onto the line item it affects (SEC Release 33-8810 II B 1 and AS 2201 para 65 Note 2)"
           alt="Carries a deficiency onto the financial statement line item it affects, so the line item can be looked at as a whole">
    <condition rel="for line item" subject="%O" object="%S"/>
  </relinst>
  <relinst type="component has deficiency" cf="100"
           name="[CORE] D7 D8 - projects a deficiency onto the component of internal control it affects (COSO Internal Control FAQs 2013)"
           alt="Carries a deficiency onto the component of internal control it affects, so deficiencies can be aggregated across components">
    <condition rel="for coso component" subject="%O" object="%S"/>
  </relinst>
  <relinst type="assertion has deficiency band rank" cf="100"
           name="[CORE] D7 - carries each member band onto the assertion as a rank so the group can be counted by band (AS 2201 para 65 Note 2)"
           alt="Carries one member's magnitude band onto the assertion as a rank, so the assertion's deficiencies can be counted band by band">
    <condition rel="for assertion" subject="%DA" object="%S"/>
    <condition rel="has magnitude band" subject="%DA" object="%BA" weight="1"/>
    <condition rel="band has rank" subject="%BA" object="%O" weight="1"/>
  </relinst>
  <relinst type="line item has deficiency band rank" cf="100"
           name="[CORE] D7 - carries each member band onto the line item as a rank so the group can be counted by band (SEC Release 33-8810 II B 1)"
           alt="Carries one member's magnitude band onto the line item as a rank, so the line item's deficiencies can be counted band by band">
    <condition rel="for line item" subject="%DL" object="%S"/>
    <condition rel="has magnitude band" subject="%DL" object="%BL" weight="1"/>
    <condition rel="band has rank" subject="%BL" object="%O" weight="1"/>
  </relinst>
  <relinst type="component has deficiency band rank" cf="100"
           name="[CORE] D7 - carries each member band onto the component as a rank so the group can be counted by band (COSO Internal Control FAQs 2013)"
           alt="Carries one member's magnitude band onto the component of internal control as a rank, so the component's deficiencies can be counted band by band">
    <condition rel="for coso component" subject="%DK" object="%S"/>
    <condition rel="has magnitude band" subject="%DK" object="%BK" weight="1"/>
    <condition rel="band has rank" subject="%BK" object="%O" weight="1"/>
  </relinst>
  <relinst type="has group size candidate" cf="100"
           name="[CORE] D7 I11 - the size of the assertion group this deficiency belongs to (AS 2201 para 65 Note 2, parameter aggregates by assertion)"
           alt="Counts the deficiencies affecting the same assertion as this one">
    <condition rel="deficiency applies testing policy" subject="%S" object="%PA"/>
    <condition rel="aggregates by assertion" subject="%PA" object="true" weight="1"/>
    <condition rel="for assertion" subject="%S" object="%AA" weight="1"/>
    <condition expression="countRelationshipInstances(%AA,'assertion has deficiency',*)" value="%O" weight="1"
               alt="The number of deficiencies affecting the same assertion"/>
  </relinst>
  <relinst type="has group size candidate" cf="100"
           name="[CORE] D7 I11 - the size of the line item group this deficiency belongs to (SEC Release 33-8810 II B 1, parameter aggregates by line item)"
           alt="Counts the deficiencies affecting the same financial statement line item as this one">
    <condition rel="deficiency applies testing policy" subject="%S" object="%PL"/>
    <condition rel="aggregates by line item" subject="%PL" object="true" weight="1"/>
    <condition rel="for line item" subject="%S" object="%AL" weight="1"/>
    <condition expression="countRelationshipInstances(%AL,'line item has deficiency',*)" value="%O" weight="1"
               alt="The number of deficiencies affecting the same line item"/>
  </relinst>
  <relinst type="has group size candidate" cf="100"
           name="[CORE] D7 D8 I11 - the size of the component group this deficiency belongs to (COSO Internal Control FAQs 2013, parameter aggregates by coso component)"
           alt="Counts the deficiencies affecting the same component of internal control as this one">
    <condition rel="deficiency applies testing policy" subject="%S" object="%PK"/>
    <condition rel="aggregates by coso component" subject="%PK" object="true" weight="1"/>
    <condition rel="for coso component" subject="%S" object="%AK" weight="1"/>
    <condition expression="countRelationshipInstances(%AK,'component has deficiency',*)" value="%O" weight="1"
               alt="The number of deficiencies affecting the same component of internal control"/>
  </relinst>
  <relinst type="has group deficiency count" cf="100"
           name="[CORE] D7 - the governing group size is the largest group this deficiency belongs to (AS 2201 para 65 Note 2)"
           alt="Takes the largest of the groups this deficiency belongs to, because the widest combination is the one that matters">
    <condition expression="countRelationshipInstances(%S,'has group size candidate',*) is greater than or equal to 1" weight="1"
               alt="At least one grouping axis has been established for this deficiency"/>
    <condition expression="maxObjects(%S,'has group size candidate',*)" value="%O" weight="1"
               alt="The largest group this deficiency belongs to governs"/>
  </relinst>
  <relinst type="has aggregated band candidate" cf="100"
           name="[CORE] D7 I11 - deficiencies on the same assertion aggregate to a higher band (AS 2201 para 65 Note 2, practice calibration of the row counts)"
           alt="At least {{%MINA}} deficiencies on this assertion sit at the row's individual band, so the combination is evaluated at the aggregated band">
    <condition rel="deficiency applies testing policy" subject="%S" object="%QA"/>
    <condition rel="aggregates by assertion" subject="%QA" object="true" weight="1"/>
    <condition rel="for assertion" subject="%S" object="%GA" weight="1"/>
    <condition rel="has aggregation row" subject="%QA" object="%RA" weight="1"/>
    <condition rel="aggregation row individual band" subject="%RA" object="%IBA" weight="1"/>
    <condition rel="band has rank" subject="%IBA" object="%IRA" weight="1"/>
    <condition rel="aggregation row minimum count" subject="%RA" object="%MINA" weight="1"/>
    <!-- The relationship-form read below is what makes the count beneath it  -->
    <!-- meaningful. A count whose object is a BOUND value is not pursued as  -->
    <!-- a goal, so the per-member band projections were never derived and    -->
    <!-- the count stood at zero on a group that plainly qualified. Reading   -->
    <!-- the projection at the row's own band first makes the engine derive   -->
    <!-- it, and doubles as the proof that at least one member sits there.    -->
    <condition rel="assertion has deficiency band rank" subject="%GA" object="%IRA" weight="1"/>
    <condition expression="countRelationshipInstances(%GA,'assertion has deficiency band rank',%IRA) is greater than or equal to %MINA" weight="1"
               alt="The assertion carries at least as many deficiencies at the row's individual band as the row requires"/>
    <condition rel="aggregation row aggregated band" subject="%RA" object="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregated band candidate" cf="100"
           name="[CORE] D7 I11 - deficiencies on the same line item aggregate to a higher band (SEC Release 33-8810 II B 1, practice calibration of the row counts)"
           alt="At least {{%MINL}} deficiencies on this line item sit at the row's individual band, so the combination is evaluated at the aggregated band">
    <condition rel="deficiency applies testing policy" subject="%S" object="%QL"/>
    <condition rel="aggregates by line item" subject="%QL" object="true" weight="1"/>
    <condition rel="for line item" subject="%S" object="%GL" weight="1"/>
    <condition rel="has aggregation row" subject="%QL" object="%RL" weight="1"/>
    <condition rel="aggregation row individual band" subject="%RL" object="%IBL" weight="1"/>
    <condition rel="band has rank" subject="%IBL" object="%IRL" weight="1"/>
    <condition rel="aggregation row minimum count" subject="%RL" object="%MINL" weight="1"/>
    <!-- See the assertion rule above: the relationship-form read forces the  -->
    <!-- per-member projections to be derived before they are counted.        -->
    <condition rel="line item has deficiency band rank" subject="%GL" object="%IRL" weight="1"/>
    <condition expression="countRelationshipInstances(%GL,'line item has deficiency band rank',%IRL) is greater than or equal to %MINL" weight="1"
               alt="The line item carries at least as many deficiencies at the row's individual band as the row requires"/>
    <condition rel="aggregation row aggregated band" subject="%RL" object="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregated band candidate" cf="100"
           name="[CORE] D7 D8 I11 - deficiencies in the same component aggregate to a higher band (COSO Internal Control FAQs 2013, practice calibration of the row counts)"
           alt="At least {{%MINK}} deficiencies in this component sit at the row's individual band, so the combination is evaluated at the aggregated band">
    <condition rel="deficiency applies testing policy" subject="%S" object="%QK"/>
    <condition rel="aggregates by coso component" subject="%QK" object="true" weight="1"/>
    <condition rel="for coso component" subject="%S" object="%GK" weight="1"/>
    <condition rel="has aggregation row" subject="%QK" object="%RK" weight="1"/>
    <condition rel="aggregation row individual band" subject="%RK" object="%IBK" weight="1"/>
    <condition rel="band has rank" subject="%IBK" object="%IRK" weight="1"/>
    <condition rel="aggregation row minimum count" subject="%RK" object="%MINK" weight="1"/>
    <!-- See the assertion rule above: the relationship-form read forces the  -->
    <!-- per-member projections to be derived before they are counted.        -->
    <condition rel="component has deficiency band rank" subject="%GK" object="%IRK" weight="1"/>
    <condition expression="countRelationshipInstances(%GK,'component has deficiency band rank',%IRK) is greater than or equal to %MINK" weight="1"
               alt="The component carries at least as many deficiencies at the row's individual band as the row requires"/>
    <condition rel="aggregation row aggregated band" subject="%RK" object="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregated band candidate rank" cf="100"
           name="[CORE] D7 - ranks each aggregated band candidate so the highest can be taken (AS 2201 para 65 Note 2)"
           alt="Ranks one aggregated band candidate so the candidates can be compared without any rule holding a band name as a threshold">
    <condition rel="has aggregated band candidate" subject="%S" object="%CB"/>
    <condition rel="band has rank" subject="%CB" object="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregated magnitude band" cf="100"
           name="[CORE] D7 - the governing aggregated band is the highest candidate (AS 2201 para 65 Note 2 and SEC Release 33-8810 II B 1)"
           alt="Takes the highest aggregated band any grouping axis produced, because one axis cannot reduce what another has established">
    <condition expression="countRelationshipInstances(%S,'has aggregated band candidate rank',*) is greater than or equal to 1" weight="1"
               alt="At least one aggregated band candidate has been established for this deficiency"/>
    <condition expression="maxObjects(%S,'has aggregated band candidate rank',*)" value="%MAXAR" weight="1"
               alt="The highest aggregated band candidate governs"/>
    <condition rel="has aggregated band candidate" subject="%S" object="%O" weight="1"/>
    <condition rel="band has rank" subject="%O" object="%OWNAR" weight="1"/>
    <condition expression="%OWNAR is equal to %MAXAR" weight="1"
               alt="This candidate is the highest aggregated band candidate"/>
  </relinst>
  <relinst type="has effective magnitude band" cf="100"
           name="[CORE] D7 - where nothing aggregates the effective band is the band supplied (AS 2201 paras 63 and 66)"
           alt="No combination raises this deficiency's magnitude, so the effective band is the band supplied for it">
    <condition rel="has magnitude band" subject="%S" object="%O"/>
    <condition expression="countRelationshipInstances(%S,'has aggregated band candidate rank',*) is equal to 0" weight="1"
               alt="No grouping axis produced an aggregated band for this deficiency"/>
    <condition expression="countRelationshipInstances(%S,'has aggregated magnitude band',*) is equal to 0" weight="1"
               alt="No aggregated magnitude band has been established or supplied for this deficiency"/>
  </relinst>
  <relinst type="has effective magnitude band" cf="100"
           name="[CORE] D7 - the combination governs where it is higher than the band supplied (AS 2201 para 65 Note 2)"
           alt="The combination carries a higher magnitude than this deficiency on its own, so the aggregated band governs">
    <condition rel="has aggregated magnitude band" subject="%S" object="%O"/>
    <condition rel="band has rank" subject="%O" object="%AGR" weight="1"/>
    <condition rel="has magnitude band" subject="%S" object="%OWNB" weight="1"/>
    <condition rel="band has rank" subject="%OWNB" object="%OWNR" weight="1"/>
    <condition expression="%AGR is greater than %OWNR" weight="1"
               alt="The aggregated band is higher than the band supplied for this deficiency alone"/>
  </relinst>
  <relinst type="has effective magnitude band" cf="100"
           name="[CORE] D7 - aggregation never lowers the band supplied (AS 2201 paras 65 Note 2 and 66)"
           alt="The band supplied for this deficiency is already at or above the aggregated band, so it stands">
    <condition rel="has magnitude band" subject="%S" object="%O"/>
    <condition rel="band has rank" subject="%O" object="%OWNR2" weight="1"/>
    <condition rel="has aggregated magnitude band" subject="%S" object="%AGB2" weight="1"/>
    <condition rel="band has rank" subject="%AGB2" object="%AGR2" weight="1"/>
    <condition expression="%OWNR2 is greater than or equal to %AGR2" weight="1"
               alt="The band supplied is at least as high as the aggregated band"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D7 - why deficiencies are evaluated in combination at all (AS 2201 paras 62 and 65 Note 2, SEC Release 33-8810 II B 1)"
           alt="States the obligation to evaluate deficiencies in combination and the three grouping axes this assessment uses">
    <condition rel="has group deficiency count" subject="%S" object="%GC"/>
    <condition expression="'Deficiencies in the same group as this one: ' + %GC + '. The severity of each deficiency must be evaluated to determine whether deficiencies, INDIVIDUALLY OR IN COMBINATION, are severe, AS 2201 paragraph 62. Multiple deficiencies affecting the same amount or disclosure increase the likelihood of misstatement and may in combination amount to a severe failing even where each is individually less severe, paragraph 65 Note 2 and SEC Release 33-8810 section II B 1, which directs grouping by common amount, common disclosure or common component of internal control. This assessment groups on three axes - the same assertion, the same line item, and the same component - and the widest group governs.'" value="%O"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D7 - the combination raised the magnitude above the band supplied (AS 2201 para 65 Note 2 and SEC Release 33-8810 II B 1)"
           alt="States that the combination raised the magnitude, naming the band supplied and the aggregated band">
    <condition rel="has aggregated magnitude band" subject="%S" object="%AGF"/>
    <condition rel="band has rank" subject="%AGF" object="%AGFR" weight="1"/>
    <condition rel="has magnitude band" subject="%S" object="%OWNF" weight="1"/>
    <condition rel="band has rank" subject="%OWNF" object="%OWNFR" weight="1"/>
    <condition expression="%AGFR is greater than %OWNFR" weight="1"
               alt="The aggregated band is higher than the band supplied for this deficiency alone"/>
    <condition rel="has effective magnitude band" subject="%S" object="%EFF" weight="1"/>
    <condition expression="'The combination governs. Taken alone this deficiency was supplied at ' + %OWNF" value="%P1" weight="1"/>
    <condition expression="%P1 + ' and the group it belongs to aggregates to ' + %AGF" value="%P2" weight="1"/>
    <condition expression="%P2 + ', so the magnitude evaluated is ' + %EFF" value="%P3" weight="1"/>
    <condition expression="%P3 + '. A combination may be more severe than any of its members, AS 2201 paragraph 65 Note 2 and SEC Release 33-8810 section II B 1. The row counts that decide when a combination escalates are a practice calibration and not a figure any primary source states, so they are exposed as parameters and the institution should set them against its own experience.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D7 - an aggregation row was met but it does not raise the band supplied (AS 2201 paras 65 Note 2 and 66)"
           alt="States that a combination was identified but the band supplied already stands at or above it, so aggregation changes nothing">
    <condition rel="has aggregated magnitude band" subject="%S" object="%AGN"/>
    <condition rel="band has rank" subject="%AGN" object="%AGNR" weight="1"/>
    <condition rel="has magnitude band" subject="%S" object="%OWNN" weight="1"/>
    <condition rel="band has rank" subject="%OWNN" object="%OWNNR" weight="1"/>
    <condition expression="%OWNNR is greater than or equal to %AGNR" weight="1"
               alt="The band supplied is at least as high as the aggregated band"/>
    <condition expression="'An aggregation row was met for this deficiency and the group it belongs to aggregates to ' + %AGN" value="%N1" weight="1"/>
    <condition expression="%N1 + ', but the band supplied for this deficiency on its own is already ' + %OWNN" value="%N2" weight="1"/>
    <condition expression="%N2 + ', so the combination does not raise the magnitude evaluated and the band supplied stands. Aggregation may raise a magnitude and never lowers one, AS 2201 paragraph 65 Note 2 read with paragraph 66. The interaction among the deficiencies in the group remains a named likelihood factor in its own right and should be weighed in the likelihood judgement even where the magnitude is unchanged.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D7 - a deficiency standing alone in its group (AS 2201 para 65 Note 2)"
           alt="States that this deficiency is the only one in its group, so no combination arises">
    <condition rel="has group deficiency count" subject="%S" object="1"/>
    <condition expression="'This deficiency is the only one in its group, so no combination arises and its own magnitude band governs. Worth noting what that does and does not mean. It means no OTHER deficiency has been supplied to this assessment against the same assertion, line item or component. It does not mean none exists: the aggregation this assessment can perform is bounded by the deficiencies it has been given, and a deficiency recorded elsewhere and not supplied here cannot be grouped with this one.'" value="%O"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D7 - a group of more than one where no row was met (AS 2201 para 65 Note 2, practice calibration of the row counts)"
           alt="States that the group holds more than one deficiency but no aggregation row was met, so the band supplied stands">
    <condition rel="has group deficiency count" subject="%S" object="%GN"/>
    <condition expression="%GN is greater than or equal to 2" weight="1"
               alt="The group holds more than one deficiency"/>
    <condition expression="countRelationshipInstances(%S,'has aggregated band candidate',*) is equal to 0" weight="1"
               alt="No aggregation row was met for this deficiency"/>
    <condition expression="'The group holds more than one deficiency and no aggregation row was met, so this deficiency is evaluated at the band supplied for it. That is a conclusion about the calibrated row counts and not a judgement that the combination is harmless. Two points follow. The row counts are practice, so an institution that sees combinations escalate sooner should lower them. And the interaction among the deficiencies in the group remains a named likelihood factor in its own right, so it should be weighed in the likelihood judgement even where the magnitude table is silent.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the assertion grouping axis (AS 2201 para 65 Note 2)"
           alt="Names the assertion group this deficiency belongs to and how large it is">
    <condition rel="for assertion" subject="%S" object="%AX1"/>
    <condition expression="countRelationshipInstances(%AX1,'assertion has deficiency',*)" value="%AC1" weight="1"
               alt="The number of deficiencies affecting the same assertion"/>
    <condition expression="'Assertion grouping: this deficiency affects ' + %AX1" value="%Q1" weight="1"/>
    <condition expression="%Q1 + ', which carries ' + %AC1" value="%Q2" weight="1"/>
    <condition expression="%Q2 + ' deficiency record or records in this assessment. The relevant assertion is the unit of aggregation the standard works in, because a control is selected and judged against the assertion it addresses, AS 2201 paragraph 65 Note 2.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the line item grouping axis (SEC Release 33-8810 II B 1)"
           alt="Names the line item group this deficiency belongs to and how large it is">
    <condition rel="for line item" subject="%S" object="%AX2"/>
    <condition expression="countRelationshipInstances(%AX2,'line item has deficiency',*)" value="%AC2" weight="1"
               alt="The number of deficiencies affecting the same line item"/>
    <condition expression="'Line item grouping: this deficiency affects ' + %AX2" value="%R1" weight="1"/>
    <condition expression="%R1 + ', which carries ' + %AC2" value="%R2" weight="1"/>
    <condition expression="%R2 + ' deficiency record or records in this assessment. Management is directed to group deficiencies by common financial statement amount or common disclosure, SEC Release 33-8810 section II B 1, which is the axis a reader of the accounts would recognise.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the component grouping axis and the across-components obligation (COSO Internal Control FAQs 2013)"
           alt="Names the component group this deficiency belongs to and states that deficiencies must be aggregated across components">
    <condition rel="for coso component" subject="%S" object="%AX3"/>
    <condition expression="countRelationshipInstances(%AX3,'component has deficiency',*)" value="%AC3" weight="1"
               alt="The number of deficiencies affecting the same component of internal control"/>
    <condition expression="'Component grouping: this deficiency affects ' + %AX3" value="%T1" weight="1"/>
    <condition expression="%T1 + ', which carries ' + %AC3" value="%T2" weight="1"/>
    <condition expression="%T2 + ' deficiency record or records in this assessment. The components operate together only where deficiencies AGGREGATED ACROSS components do not amount to a severe shortfall, COSO Internal Control FAQs, so deficiencies must be aggregated across the components and not evaluated only within one. The direction of that obligation is worth keeping in view: grouping by component is a way of finding combinations, never a way of confining a deficiency to one component and treating the rest of the system as unaffected.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the assertion grouping has been switched off (AS 2201 para 65 Note 2, parameter aggregates by assertion)"
           alt="States that grouping by assertion has been switched off in this institution's calibration">
    <condition rel="deficiency applies testing policy" subject="%S" object="%OF1"/>
    <condition rel="aggregates by assertion" subject="%OF1" object="false" weight="1"/>
    <condition expression="'Grouping by assertion is switched off in this calibration, so no combination on that axis has been looked for. The standard directs that deficiencies be evaluated individually or in combination, AS 2201 paragraphs 62 and 65 Note 2, and the assertion is the unit the standard itself works in, so switching this axis off narrows the assessment and should be a deliberate choice recorded with a reason.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the line item grouping has been switched off (SEC Release 33-8810 II B 1, parameter aggregates by line item)"
           alt="States that grouping by line item has been switched off in this institution's calibration">
    <condition rel="deficiency applies testing policy" subject="%S" object="%OF2"/>
    <condition rel="aggregates by line item" subject="%OF2" object="false" weight="1"/>
    <condition expression="'Grouping by financial statement line item is switched off in this calibration, so no combination on that axis has been looked for. Management is directed to group by common amount or common disclosure, SEC Release 33-8810 section II B 1, so switching this axis off narrows the assessment and should be a deliberate choice recorded with a reason.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has aggregation finding" cf="100"
           name="[CORE] D8 I11 - the component grouping has been switched off (COSO Internal Control FAQs 2013, parameter aggregates by coso component)"
           alt="States that grouping by component of internal control has been switched off in this institution's calibration">
    <condition rel="deficiency applies testing policy" subject="%S" object="%OF3"/>
    <condition rel="aggregates by coso component" subject="%OF3" object="false" weight="1"/>
    <condition expression="'Grouping by component of internal control is switched off in this calibration, so no combination on that axis has been looked for. Deficiencies must be aggregated across components, COSO Internal Control FAQs, so switching this axis off narrows the assessment and should be a deliberate choice recorded with a reason.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D7a - interaction among deficiencies and among controls is a named likelihood factor (AS 2201 para 65 and SEC Release 33-8810 II B 1)"
           alt="States that interaction bears on the likelihood judgement directly and not only through the grouping table">
    <condition rel="has group deficiency count" subject="%S" object="%GI"/>
    <condition expression="%GI is greater than or equal to 2" weight="1"
               alt="This deficiency shares a group with at least one other"/>
    <condition expression="'Interaction is a likelihood factor in its own right. Among the factors that affect whether there is a reasonable possibility of misstatement, AS 2201 paragraph 65 names the INTERACTION OR RELATIONSHIP of the control with other controls, including whether they are interdependent or redundant, and the INTERACTION OF THE DEFICIENCIES, including whether related deficiencies affect the same amount or disclosure. Deficiencies affecting the same amount increase the likelihood of misstatement, SEC Release 33-8810 section II B 1. So interaction reaches severity by two routes, and this assessment applies only one of them: the grouping table raises the MAGNITUDE where the calibrated counts are met, and the effect of interaction on LIKELIHOOD is left to the judgement supplied, because no fetched source reduces it to a test. Where this deficiency shares a group with others, the likelihood supplied should already reflect that.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency judgement statement" cf="100"
           name="[CORE] D7a - evaluating deficiencies in isolation is a named failure (PCAOB Staff Audit Practice Alert No 11 pages 32 to 35)"
           alt="Records the inspection finding that deficiencies evaluated in isolation and magnitude read from identified misstatements alone are both known failures">
    <condition rel="has group deficiency count" subject="%S" object="%GJ"/>
    <condition expression="%GJ is greater than or equal to 2" weight="1"
               alt="This deficiency shares a group with at least one other"/>
    <condition expression="'Three failures recur in inspection findings, and this one shares a group with others, so all three are in point. Assessing control deficiencies IN ISOLATION without considering the effect of deficiencies in combination; considering only the amount of IDENTIFIED misstatements without evaluating the magnitude of POTENTIAL misstatement; and working through a checklist of indicators without considering other relevant factors. Evaluating deficiencies requires professional scepticism and a careful analysis of all the evidence obtained, and a mechanical or cursory evaluation leads to the three errors above, PCAOB Staff Audit Practice Alert No 11 pages 32 to 35. This assessment performs the grouping; the scepticism is the reader s.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D7 D8 G6 - no grouping axis has been supplied for this deficiency (AS 2201 para 65 Note 2 and SEC Release 33-8810 II B 1)"
           alt="No assertion, line item or component has been supplied for this deficiency, so it cannot be grouped with any other">
    <condition rel="has deficiency type" subject="%S" object="%DTG"/>
    <condition expression="countRelationshipInstances(%S,'for assertion',*) is equal to 0" weight="1"
               alt="No assertion has been supplied for this deficiency"/>
    <condition expression="countRelationshipInstances(%S,'for line item',*) is equal to 0" weight="1"
               alt="No line item has been supplied for this deficiency"/>
    <condition expression="countRelationshipInstances(%S,'for coso component',*) is equal to 0" weight="1"
               alt="No component of internal control has been supplied for this deficiency"/>
    <condition expression="'Which assertion, which financial statement line item and which component of internal control this deficiency affects. None of the three has been supplied, so this deficiency cannot be grouped with any other and the obligation to evaluate deficiencies in combination has not been discharged for it, AS 2201 paragraphs 62 and 65 Note 2 and SEC Release 33-8810 section II B 1. The severity reported rests on this deficiency alone and may understate it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D8 G6 - the component of internal control has not been supplied (COSO Internal Control FAQs 2013)"
           alt="A grouping axis has been supplied but not the component of internal control, so the across-components aggregation cannot run">
    <condition rel="deficiency applies testing policy" subject="%S" object="%OQ1"/>
    <condition rel="aggregates by coso component" subject="%OQ1" object="true" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%DTH" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'for coso component',*) is equal to 0" weight="1"
               alt="No component of internal control has been supplied for this deficiency"/>
    <condition expression="'Which component of internal control this deficiency affects - the control environment, risk assessment, control activities, information and communication, or monitoring activities. Grouping by component is switched on in this calibration but the component has not been supplied, so the across-components aggregation the framework requires cannot run for this deficiency, COSO Internal Control FAQs. Deficiencies that look unrelated across processes often share a component, and that is exactly the combination this axis exists to find.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D7 G6 - a group member has no magnitude band so the group cannot be counted by band (AS 2201 paras 65 Note 2 and 66)"
           alt="This deficiency shares a group with others and has no magnitude band, so it contributes nothing to the group's band counts">
    <condition rel="has group deficiency count" subject="%S" object="%GQ"/>
    <condition expression="%GQ is greater than or equal to 2" weight="1"
               alt="This deficiency shares a group with at least one other"/>
    <condition expression="countRelationshipInstances(%S,'has magnitude band',*) is equal to 0" weight="1"
               alt="No magnitude band has been supplied for this deficiency"/>
    <condition expression="'The magnitude band for this deficiency, which is needed twice over. Without it this deficiency has no magnitude of its own, and it also contributes nothing to the band counts of the group it belongs to, so the combination may be understated for every OTHER member of that group as well. A missing band in a group is not a local gap.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has remediation months candidate" cf="100"
           name="[CORE] D9 I10a - months of operation from the date the remediated control was first performed (AS 2201 para B2, SEC 33-8810 II A 2 b, practice)"
           alt="Measures the months from the date the remediated control was first performed as designed to the period end">
    <condition rel="remediation first performed date" subject="%S" object="%RFD"/>
    <condition rel="deficiency of control" subject="%S" object="%RC1" weight="1"/>
    <condition rel="has period end" subject="%RC1" object="%RPE" weight="1"/>
    <condition expression="isAfterDate(%RFD,%RPE) is equal to false" weight="1"
               alt="The date the remediated control was first performed falls on or before the period end"/>
    <condition expression="monthsBetween(%RFD,%RPE)" value="%O" weight="1"
               alt="Counts the months the remediated control has operated up to the period end"/>
  </relinst>
  <relinst type="has remediation months candidate" cf="100"
           name="[CORE] D9 - the months of operation as supplied (AS 2201 paras 52 and 53)"
           alt="Takes the months of operation of the remediated control as supplied">
    <condition rel="remediation months of operation" subject="%S" object="%O"/>
  </relinst>
  <relinst type="has remediation months" cf="100"
           name="[CORE] D9 I10a - the governing months of operation is the shorter of the two routes (AS 2201 paras 52 and 53, conservative default)"
           alt="Takes the shorter of the computed and the supplied months of operation, because a remediation clock is not a figure to flatter">
    <condition expression="countRelationshipInstances(%S,'has remediation months candidate',*) is greater than or equal to 1" weight="1"
               alt="At least one measure of the months of operation is available"/>
    <condition expression="minObjects(%S,'has remediation months candidate',*)" value="%O" weight="1"
               alt="The shorter measure of the months of operation governs"/>
  </relinst>
  <relinst type="remediation period sufficient" object="true" cf="100"
           name="[CORE] D9 D11 I10 - the remediated control has operated long enough for its frequency (AS 2201 paras 52 and 53, SEC 33-8810 II A 2 b, practice)"
           alt="The remediated control has operated for {{%RM1}} months against a calibrated minimum of {{%MINM1}} for its frequency, so the period is sufficient">
    <condition rel="has remediation months" subject="%S" object="%RM1"/>
    <condition rel="deficiency of control" subject="%S" object="%PC1" weight="1"/>
    <condition rel="has frequency" subject="%PC1" object="%PF1" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%PP1" weight="1"/>
    <condition rel="has remediation row" subject="%PP1" object="%PR1" weight="1"/>
    <condition rel="remediation row frequency" subject="%PR1" object="%PF1" weight="1"/>
    <condition rel="remediation row minimum months" subject="%PR1" object="%MINM1" weight="1"/>
    <condition expression="%RM1 is greater than or equal to %MINM1" weight="1"
               alt="The months of operation meet the calibrated minimum for the control's frequency"/>
  </relinst>
  <relinst type="remediation period sufficient" object="false" cf="100"
           name="[CORE] D10 D11 I10 - the remediated control has not operated long enough for its frequency (AS 2201 paras 52 and 53, practice calibration of the period)"
           alt="The remediated control has operated for {{%RM2}} months against a calibrated minimum of {{%MINM2}} for its frequency, so the period is not sufficient">
    <condition rel="has remediation months" subject="%S" object="%RM2"/>
    <condition rel="deficiency of control" subject="%S" object="%PC2" weight="1"/>
    <condition rel="has frequency" subject="%PC2" object="%PF2" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%PP2" weight="1"/>
    <condition rel="has remediation row" subject="%PP2" object="%PR2" weight="1"/>
    <condition rel="remediation row frequency" subject="%PR2" object="%PF2" weight="1"/>
    <condition rel="remediation row minimum months" subject="%PR2" object="%MINM2" weight="1"/>
    <condition expression="%RM2 is less than %MINM2" weight="1"
               alt="The months of operation fall short of the calibrated minimum for the control's frequency"/>
  </relinst>
  <relinst type="remediation period sufficient" object="false" cf="100"
           name="[CORE] D10 D11 G6 - a retest with no record of how long the fix has operated cannot establish the period (AS 2201 paras 52 and 53, conservative default)"
           alt="The remediated control was retested and nothing records how long it has operated, so the period cannot be found sufficient">
    <condition rel="remediated control retested" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediation first performed date',*) is equal to 0" weight="1"
               alt="No date is recorded for when the remediated control was first performed as designed"/>
    <condition expression="countRelationshipInstances(%S,'remediation months of operation',*) is equal to 0" weight="1"
               alt="No month count is recorded for how long the remediated control has operated"/>
  </relinst>
  <relinst type="remediation occurrences sufficient" object="true" cf="100"
           name="[CORE] D9 I10b - the retest of the remediated control covered enough occurrences (AS 2201 para 54, practice calibration of the occurrences)"
           alt="The retest covered {{%OS1}} occurrences against a calibrated minimum of {{%MINO1}} for the control's frequency, so the extent of the retest is sufficient">
    <condition rel="remediated control retest sample size" subject="%S" object="%OS1"/>
    <condition rel="deficiency of control" subject="%S" object="%OC1" weight="1"/>
    <condition rel="has frequency" subject="%OC1" object="%OF1" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%OP1" weight="1"/>
    <condition rel="has remediation row" subject="%OP1" object="%OR1" weight="1"/>
    <condition rel="remediation row frequency" subject="%OR1" object="%OF1" weight="1"/>
    <condition rel="remediation row minimum occurrences" subject="%OR1" object="%MINO1" weight="1"/>
    <condition expression="%OS1 is greater than or equal to %MINO1" weight="1"
               alt="The retest sample meets the calibrated minimum occurrences for the control's frequency"/>
  </relinst>
  <relinst type="remediation occurrences sufficient" object="false" cf="100"
           name="[CORE] D10 I10b - the retest of the remediated control covered too few occurrences (AS 2201 para 54, practice calibration of the occurrences)"
           alt="The retest covered {{%OS2}} occurrences against a calibrated minimum of {{%MINO2}} for the control's frequency, so the extent of the retest is not sufficient">
    <condition rel="remediated control retest sample size" subject="%S" object="%OS2"/>
    <condition rel="deficiency of control" subject="%S" object="%OC2" weight="1"/>
    <condition rel="has frequency" subject="%OC2" object="%OF2" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%OP2" weight="1"/>
    <condition rel="has remediation row" subject="%OP2" object="%OR2" weight="1"/>
    <condition rel="remediation row frequency" subject="%OR2" object="%OF2" weight="1"/>
    <condition rel="remediation row minimum occurrences" subject="%OR2" object="%MINO2" weight="1"/>
    <condition expression="%OS2 is less than %MINO2" weight="1"
               alt="The retest sample falls short of the calibrated minimum occurrences for the control's frequency"/>
  </relinst>
  <relinst type="remediation occurrences sufficient" object="false" cf="100"
           name="[CORE] D10 I10b G6 - a retest with no record of its extent cannot establish the extent (AS 2201 para 54, conservative default)"
           alt="The remediated control was retested and nothing records how many occurrences the retest covered, so the extent cannot be found sufficient">
    <condition rel="remediated control retested" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediated control retest sample size',*) is equal to 0" weight="1"
               alt="No retest sample size is recorded for the remediated control"/>
  </relinst>
  <relinst type="remediation independence cleared" object="true" cf="100"
           name="[CORE] I10c I24 - the separation is not required in this calibration (SEC Release 33-8810 II A 2, practice separation switched off)"
           alt="This institution's calibration does not require the retest to be independent of the implementer, so the leg does not apply">
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP1"/>
    <condition rel="remediation retester independence required" subject="%IP1" object="false" weight="1"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="remediation independence cleared" object="true" cf="100"
           name="[CORE] I10c I24 - the retest was performed independently of whoever implemented the fix (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="The retest of the remediated control was performed independently of the person who implemented the remediation">
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP2"/>
    <condition rel="remediation retester independence required" subject="%IP2" object="true" weight="1"/>
    <condition rel="remediation retester independent" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="remediation independence cleared" object="false" cf="100"
           name="[CORE] I10c I24 - the retest was performed by whoever implemented the fix (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="The retest of the remediated control was not independent of the person who implemented the remediation">
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP3"/>
    <condition rel="remediation retester independence required" subject="%IP3" object="true" weight="1"/>
    <condition rel="remediation retester independent" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="remediation independence cleared" object="false" cf="100"
           name="[CORE] I10c I24 G6 - the separation is required and who performed the retest is unanswered (SEC Release 33-8810 II A 2 footnote 40, conservative default)"
           alt="This institution requires the retest to be independent of the implementer and nothing records whether it was, so the leg is not cleared">
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP4"/>
    <condition rel="remediation retester independence required" subject="%IP4" object="true" weight="1"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'remediation retester independent',*) is equal to 0" weight="1"
               alt="Whether the retest was independent of the person who implemented the remediation is not recorded"/>
  </relinst>
  <relinst type="persists at period end" object="false" cf="100"
           name="[CORE] D9 - a deficiency fixed and properly retested before period end does not persist (AS 2201 paras B2 52 and 53, 17 CFR 229.308 a 2 and SEC Release 33-8810 II A 2 b)"
           alt="The deficiency was remediated before period end and the remediated control was retested over a sufficient period and extent, so it does not persist at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition rel="remediation period sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="remediation occurrences sufficient" subject="%S" object="true" weight="1"/>
    <condition rel="remediation independence cleared" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D9 - an unremediated deficiency persists at period end (AS 2201 para B2 and 17 CFR 229.308 a 2)"
           alt="The deficiency was not remediated before period end, so it stands at the date the conclusion speaks as of">
    <condition rel="remediated before period end" subject="%S" object="false"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D9 G6 - a deficiency with no remediation answer is treated as persisting at period end (AS 2201 para B2, conservative default)"
           alt="No answer has been recorded on remediation before period end, so this assessment treats the deficiency as standing at that date">
    <condition rel="has deficiency type" subject="%S" object="%ZD1"/>
    <condition expression="countRelationshipInstances(%S,'remediated before period end',*) is equal to 0" weight="1"
               alt="No answer has been recorded either way on whether this deficiency was remediated before period end"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D10 - a remediation that was never retested leaves the deficiency standing (AS 2201 paras 52 and 53)"
           alt="The remediated control was not retested, so there is no evidence the fix works and the deficiency stands at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D10 G6 - a remediation with no answer on retesting leaves the deficiency standing (AS 2201 paras 52 and 53, conservative default)"
           alt="The deficiency was remediated before period end but nothing records whether the remediated control was retested, so it stands at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediated control retested',*) is equal to 0" weight="1"
               alt="Whether the remediated control was retested is not recorded"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D10 D11 - a retest over too short a period leaves the deficiency standing (AS 2201 paras 52 and 53, practice calibration of the period)"
           alt="The remediated control had not operated long enough to be assessed, so the deficiency stands at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediation period sufficient" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D10 I10b - a retest over too few occurrences leaves the deficiency standing (AS 2201 para 54, practice calibration of the occurrences)"
           alt="The retest of the remediated control covered too few occurrences, so the deficiency stands at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediation occurrences sufficient" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="persists at period end" object="true" cf="100"
           name="[CORE] D10 I10c - a retest by the implementer leaves the deficiency standing (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="The retest of the remediated control was not independent of the person who implemented the fix, so the deficiency stands at period end">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediation independence cleared" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="requires retest" object="true" cf="100"
           name="[CORE] D12 - a remediation with no retest requires one (AS 2201 paras 52 and 53)"
           alt="The deficiency was remediated and the remediated control has not been retested, so a retest is required">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="requires retest" object="true" cf="100"
           name="[CORE] D12 G6 - a remediation with no answer on retesting requires a retest (AS 2201 paras 52 and 53, conservative default)"
           alt="The deficiency was remediated and nothing records a retest of the remediated control, so a retest is required">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediated control retested',*) is equal to 0" weight="1"
               alt="Whether the remediated control was retested is not recorded"/>
  </relinst>
  <relinst type="requires retest" object="true" cf="100"
           name="[CORE] D12 D11 - a retest over too short a period must be repeated once the period is long enough (AS 2201 paras 52 and 53, practice calibration of the period)"
           alt="The remediated control was retested too early, so a further retest is required once it has operated long enough">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition rel="remediation period sufficient" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="requires retest" object="true" cf="100"
           name="[CORE] D12 I10b - a retest over too few occurrences must be extended (AS 2201 para 54, practice calibration of the occurrences)"
           alt="The retest covered too few occurrences, so a further retest is required to reach the calibrated extent">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition rel="remediation occurrences sufficient" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="requires retest" object="true" cf="100"
           name="[CORE] D12 I10c - a retest by the implementer must be repeated independently (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="The retest was not independent of the person who implemented the fix, so an independent retest is required">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition rel="remediation independence cleared" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="requires retest" object="false" cf="100"
           name="[CORE] D12 - no retest is required where the remediation is already established (AS 2201 paras 52 and 53)"
           alt="The remediation has been retested over a sufficient period and extent, so no further retest is required for this deficiency">
    <condition rel="persists at period end" subject="%S" object="false"/>
  </relinst>
  <relinst type="requires retest" object="false" cf="100"
           name="[CORE] D12 - no retest arises where nothing has been remediated (AS 2201 para B2)"
           alt="Nothing has been remediated, so there is no remediated control to retest and the deficiency stands on its own facts">
    <condition rel="remediated before period end" subject="%S" object="false"/>
  </relinst>
  <relinst type="requires retest" object="false" cf="100"
           name="[CORE] D12 G6 - no retest requirement arises where no remediation has been claimed either way (AS 2201 para B2, conservative default)"
           alt="No remediation has been recorded for this deficiency either way, so there is no remediated control for a retest to establish">
    <condition rel="has deficiency type" subject="%S" object="%ZD2"/>
    <condition expression="countRelationshipInstances(%S,'remediated before period end',*) is equal to 0" weight="1"
               alt="No answer has been recorded either way on whether this deficiency was remediated before period end"/>
  </relinst>
  <relinst type="has retest condition" cf="100"
           name="[CORE] D12 D11 - the conditions a retest must meet, stated once a retest is required (AS 2201 paras 52 53 and 54, practice calibration of the figures)"
           alt="States the three conditions a retest of a remediated control must meet, naming the calibrated figures for the control's frequency">
    <condition rel="requires retest" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%TC1" weight="1"/>
    <condition rel="has frequency" subject="%TC1" object="%TF1" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%TP1" weight="1"/>
    <condition rel="has remediation row" subject="%TP1" object="%TR1" weight="1"/>
    <condition rel="remediation row frequency" subject="%TR1" object="%TF1" weight="1"/>
    <condition rel="remediation row minimum months" subject="%TR1" object="%TMM" weight="1"/>
    <condition rel="remediation row minimum occurrences" subject="%TR1" object="%TMO" weight="1"/>
    <condition expression="'A retest is required, and three conditions govern it for a control performed ' + %TF1" value="%U1" weight="1"/>
    <condition expression="%U1 + '. The remediated control must have operated as designed for at least ' + %TMM" value="%U2" weight="1"/>
    <condition expression="%U2 + ' months, counted from the date it was first performed as designed and not from the date the fix was implemented. The retest must cover at least ' + %TMO" value="%U3" weight="1"/>
    <condition expression="%U3 + ' occurrences, because enough elapsed time is not the same as enough instances. And the retest must be performed independently of whoever implemented the remediation. The first two figures are a practice calibration: no primary source fetched in this build states a number, and the three practice sources that do give figures disagree, so these are a conservative synthesis exposed as parameters.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D9 - why a remediation must be retested at all, and where the rule comes from (AS 2201 paras B2 52 and 53, 17 CFR 229.308 a 2, SEC Release 33-8810 II A 2 b)"
           alt="States the assembled warrant for the remediation rule and names the paragraphs each limb rests on">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition expression="'This deficiency is said to have been remediated before period end, so the question is whether the fix has been established. No primary source fetched in this build has a remediation paragraph, so the rule applied here is assembled from three that were fetched. The assessment speaks AS OF a date, AS 2201 paragraph B2 and 17 CFR 229.308(a)(2). Evidence must cover a period sufficient to assess operating effectiveness, AS 2201 paragraphs 52 and 53. And it should ordinarily cover a reasonable period of time that includes the fiscal year end, SEC Release 33-8810 section II A 2 b. Taken together: a fix counts at period end only if the fixed control has run long enough, up to that date, to be tested. PCAOB AS 6115 addresses reporting on whether a severe failing continues to exist and is VOLUNTARY guidance; it is persuasive by analogy here and is not applied as a requirement.'" value="%O"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D9 I10a - the clock starts when the remediated control was first performed as designed (AS 2201 paras 52 and 53, practice clock start)"
           alt="Names the months of operation relied on and states that the clock starts at first performance and not at implementation">
    <condition rel="has remediation months" subject="%S" object="%FM"/>
    <condition expression="'Months of operation relied on: ' + %FM" value="%V1" weight="1"/>
    <condition expression="%V1 + '. The clock starts on the date the remediated control was first PERFORMED as designed, not the date the fix was implemented, and the difference is routinely months. Designing, building and rolling out a change is not operation, and a control that exists on paper from January but is first performed in April has operated since April. No source fetched in this build states the clock start in terms, so it is a practice inference, recorded as such. Where both a first-performed date and a month count were supplied and they disagree, the shorter figure has been used.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D10 D11 - the remediated control has not run long enough (AS 2201 paras 52 and 53, practice calibration of the period)"
           alt="States that the period of operation falls short of the calibrated minimum and what follows from that">
    <condition rel="remediation period sufficient" subject="%S" object="false"/>
    <condition rel="has remediation months" subject="%S" object="%SM"/>
    <condition expression="'The remediated control has operated for ' + %SM" value="%W1" weight="1"/>
    <condition expression="%W1 + ' months, which is short of the minimum calibrated for its frequency, so the original severity stands at period end. This is not a finding that the fix is bad. It is a finding that there is not yet enough evidence to say it is good, and the standard requires evidence over a period sufficient to assess operating effectiveness, AS 2201 paragraphs 52 and 53. The practical consequence is a timing one: a remediation completed late in the period will usually stand unresolved at period end however well designed it is, and the honest answer is to report it as persisting and retest in the following period.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D10 I10b - enough elapsed time is not enough occurrences (AS 2201 para 54, practice calibration of the occurrences)"
           alt="States that the retest covered too few occurrences even though time may have elapsed">
    <condition rel="remediation occurrences sufficient" subject="%S" object="false"/>
    <condition rel="remediated control retest sample size" subject="%S" object="%SO"/>
    <condition expression="'The retest covered ' + %SO" value="%X1" weight="1"/>
    <condition expression="%X1 + ' occurrences, which is short of the minimum calibrated for the control s frequency. The two legs are separate for a reason. A monthly control that has run six months and been retested once has had enough time pass and has not been tested enough: one passing instance is an anecdote, and the extent of testing is a question in its own right, AS 2201 paragraph 54. Closure of a remediation requires a passing retest at the frequency-appropriate extent, not the first instance after the fix.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D10 I10c - the retest must not be performed by whoever implemented the fix (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="States that the retest was not independent of the implementer and why that matters">
    <condition rel="remediation independence cleared" subject="%S" object="false"/>
    <condition expression="'The retest of the remediated control was performed by, or not independently of, the person who implemented the remediation, so it does not establish the fix. The objectivity point is the same one that runs through the evidence requirements generally: the evidence is less persuasive the closer the tester sits to the thing tested, SEC Release 33-8810 section II A 2 and footnote 40. Nobody is a disinterested judge of their own repair. The separation is a practice leg rather than a stated requirement, so it is exposed as a parameter, but switching it off should be a deliberate choice.'" value="%O"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D9 - the remediation is established and the deficiency does not persist (AS 2201 paras B2 52 and 53 and SEC Release 33-8810 II A 2 b)"
           alt="States that the remediation is established at period end and what that does and does not mean">
    <condition rel="persists at period end" subject="%S" object="false"/>
    <condition expression="'The remediation is established: the control was fixed before period end and the fixed control has been retested over a sufficient period and extent, so this deficiency does not persist at the date the conclusion speaks as of. Two limits on that. It does not erase the deficiency from the period: it existed, it was evaluated, and whatever communication was owed when it was identified remains owed. And it is a conclusion about this deficiency only - a control can be fixed in one respect and deficient in another.'" value="%O"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D9 - nothing has been remediated so the deficiency stands as found (AS 2201 para B2 and 17 CFR 229.308 a 2)"
           alt="States that no remediation has been recorded, so the deficiency stands at period end on its own facts">
    <condition rel="remediated before period end" subject="%S" object="false"/>
    <condition expression="'No remediation has been recorded for this deficiency before period end, so it stands at the date the conclusion speaks as of, AS 2201 paragraph B2 and 17 CFR 229.308(a)(2). Whether a remediation plan exists is a separate question from whether the control was fixed in time, and this assessment deals only with the second. Remediation planning is outside its scope; what it will say is whether a retest is required and the conditions that retest must meet.'" value="%O"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D9 - a root cause that has not been established (SEC Release 33-8810 II B 3, practice)"
           alt="States that no root cause has been established for this deficiency and why that bears on any remediation">
    <condition rel="root cause established" subject="%S" object="false"/>
    <condition expression="'No root cause has been established for this deficiency. That matters for the remediation rather than for the severity: a fix designed without the cause is a fix aimed at the symptom, and it is the commonest reason a remediated deficiency recurs in the following period. The management guidance expects a disclosure of a severe failing to convey its CAUSE and its potential impact and not merely its existence, SEC Release 33-8810 section II B 3, which cannot be done from a description of what went wrong alone.'" value="%O"/>
  </relinst>
  <relinst type="has remediation finding" cf="100"
           name="[CORE] D12 - no remediation action has been stated (SEC Release 33-8810 II B 3)"
           alt="States that no remediation action has been recorded and what the reporting consequence of that is">
    <condition rel="remediation action stated" subject="%S" object="false"/>
    <condition expression="'No remediation action has been recorded for this deficiency. This assessment does not plan remediation and does not fault its absence as a matter of the determination. It notes one reporting consequence: where a severe failing is disclosed, management should consider disclosing the plans or actions already undertaken for remediation, SEC Release 33-8810 section II B 3, so a disclosure prepared with nothing recorded here will be incomplete in a way a reader of the accounts will notice.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="The Second Line Controls Function" cf="100"
           name="[CORE] D12 G5 - the sufficiency of a remediation retest is a judgement the second line should own (AS 2201 paras 52 and 53, practice)"
           alt="Names the remediation retest sufficiency as a calibrated judgement and the function that should own it">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D9 G6 - whether the deficiency was remediated before period end (AS 2201 para B2 and 17 CFR 229.308 a 2)"
           alt="No answer has been recorded about whether this deficiency was remediated before period end">
    <condition rel="has deficiency type" subject="%S" object="%QD1"/>
    <condition expression="countRelationshipInstances(%S,'remediated before period end',*) is equal to 0" weight="1"
               alt="No answer has been recorded about remediation before period end"/>
    <condition expression="'Whether this deficiency was remediated before the period end. The assessment speaks as of that date, AS 2201 paragraph B2 and 17 CFR 229.308(a)(2), so a deficiency fixed and properly retested before it does not persist, and one fixed after it does. Without an answer this assessment treats the deficiency as persisting, which is the conservative direction and may overstate the position where a remediation was in fact completed and tested in time.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D10 G6 - whether the remediated control was retested (AS 2201 paras 52 and 53)"
           alt="A remediation has been recorded and no answer has been recorded about whether the remediated control was retested">
    <condition rel="remediated before period end" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediated control retested',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the remediated control was retested"/>
    <condition expression="'Whether the remediated control has itself been retested. Implementation is not evidence of operation: a remediation establishes nothing until the fixed control has been tested over a sufficient period, AS 2201 paragraphs 52 and 53. Without an answer this assessment treats the deficiency as persisting at period end and reports that a retest is required.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D9 I10a G6 - how long the remediated control has operated (AS 2201 paras 52 and 53, practice clock start)"
           alt="A remediation has been retested and neither the first performance date nor a month count has been supplied">
    <condition rel="remediated control retested" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has remediation months candidate',*) is equal to 0" weight="1"
               alt="Neither a first performance date nor a month count has been supplied for the remediated control"/>
    <condition expression="'How long the remediated control has operated - either the date it was first performed as designed, or the number of months it has operated to period end. The sufficiency of a remediation turns on it, AS 2201 paragraphs 52 and 53. Supply the FIRST PERFORMED date in preference: it is the date the practice sources treat as the clock start, and it is usually well after the date the fix was implemented. Without either figure this assessment cannot find the period sufficient and the deficiency stands at period end.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] I10b G6 - how many occurrences the retest covered (AS 2201 para 54, practice calibration of the occurrences)"
           alt="A remediation has been retested and the number of occurrences the retest covered has not been supplied">
    <condition rel="remediated control retested" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'remediated control retest sample size',*) is equal to 0" weight="1"
               alt="No retest sample size has been supplied for the remediated control"/>
    <condition expression="'How many occurrences of the remediated control the retest covered. Enough elapsed time is not enough instances, and the extent of testing is a question in its own right, AS 2201 paragraph 54. Without a figure this assessment cannot find the extent sufficient and the deficiency stands at period end.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] I10c G6 - whether the retest was independent of the implementer (SEC Release 33-8810 II A 2 footnote 40, practice separation)"
           alt="The separation is required in this calibration and no answer has been recorded about the independence of the retest">
    <condition rel="deficiency applies testing policy" subject="%S" object="%QP1"/>
    <condition rel="remediation retester independence required" subject="%QP1" object="true" weight="1"/>
    <condition rel="remediated control retested" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'remediation retester independent',*) is equal to 0" weight="1"
               alt="No answer has been recorded about whether the retest was independent of the implementer"/>
    <condition expression="'Whether the retest of the remediated control was performed independently of the person who implemented the remediation. This institution s calibration requires that separation, consistent with the objectivity direction in SEC Release 33-8810 section II A 2 and footnote 40. Without an answer the leg is not cleared and the deficiency stands at period end.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[CORE] D9 G6 - the control has no period end so no as-of date can be applied (AS 2201 para B2 and 17 CFR 229.308 a 2)"
           alt="A remediation date has been supplied but the control has no period end, so the months of operation cannot be computed">
    <condition rel="remediation first performed date" subject="%S" object="%QRD"/>
    <condition rel="deficiency of control" subject="%S" object="%QC1" weight="1"/>
    <condition expression="countRelationshipInstances(%QC1,'has period end',*) is equal to 0" weight="1"
               alt="No period end has been supplied for the control this deficiency belongs to"/>
    <condition expression="'The period end for the control this deficiency belongs to. A first performance date has been supplied for the remediated control, but the months of operation are measured UP TO the period end, and the whole determination speaks as of that date, AS 2201 paragraph B2 and 17 CFR 229.308(a)(2). Without it the remediation clock cannot be computed from the date supplied.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E1 - the three severity definitions and where each sits (AS 2201 paras A3 A7 and A11, AS 1305 paras 01 02 and 03)"
           alt="States the three US severity definitions and the paragraph each rests on">
    <condition rel="deficiency of control" subject="%S" object="%EC1"/>
    <condition rel="has framework" subject="%EC1" object="US ICFR" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%ET1" weight="1"/>
    <condition expression="'Three severity values apply on this path, and each has its own definition. A CONTROL DEFICIENCY exists where the design or operation of a control does not allow management or employees, in the normal course of performing their assigned functions, to prevent or detect misstatements on a timely basis, AS 2201 paragraph A3. A MATERIAL WEAKNESS is a deficiency, or a combination of deficiencies, such that there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis, paragraph A7. A SIGNIFICANT DEFICIENCY is a deficiency, or a combination of deficiencies, less severe than a material weakness yet important enough to merit attention by those responsible for oversight of the company s financial reporting, paragraph A11. The same three definitions are reproduced for a financial statement audit at AS 1305 paragraphs 01, 02 and 03. Note that two of the three say OR A COMBINATION OF DEFICIENCIES in terms, which is why the aggregation step is not optional.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E1a - reasonable possibility is the union of the upper two likelihood bands (AS 2201 para A7 Note)"
           alt="States how reasonable possibility is defined and which likelihood bands satisfy it">
    <condition rel="deficiency of control" subject="%S" object="%EC2"/>
    <condition rel="has framework" subject="%EC2" object="US ICFR" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%EL2" weight="1"/>
    <condition expression="'Likelihood supplied: ' + %EL2" value="%A1" weight="1"/>
    <condition expression="%A1 + '. There is a REASONABLE POSSIBILITY of an event when its likelihood is either REASONABLY POSSIBLE or PROBABLE as those terms are used in the accounting standard on contingencies, AS 2201 paragraph A7 Note. So the test is the union of the upper two of the three bands, and REMOTE does not meet it. This is also the reason the graph takes likelihood on that particular three-point scale rather than any other: the scale is the one the definition itself borrows.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" cf="100"
           name="[US] E2 E3 E4 E5 - the severity matrix cell for the effective magnitude band and the likelihood (AS 2201 paras 63 to 66, practice calibration of the cells)"
           alt="Reads the calibrated severity for this deficiency's effective magnitude band and likelihood">
    <condition rel="deficiency of control" subject="%S" object="%MC1"/>
    <condition rel="has framework" subject="%MC1" object="US ICFR" weight="1"/>
    <condition rel="has effective magnitude band" subject="%S" object="%MB1" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%ML1" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%MP1" weight="1"/>
    <condition rel="has severity row" subject="%MP1" object="%MR1" weight="1"/>
    <condition rel="row magnitude band" subject="%MR1" object="%MB1" weight="1"/>
    <condition rel="row likelihood" subject="%MR1" object="%ML1" weight="1"/>
    <condition rel="row is ambiguous in sources" subject="%MR1" object="false" weight="1"/>
    <condition rel="row us severity" subject="%MR1" object="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" cf="100"
           name="[US] I20 - the ambiguous matrix cell is resolved by parameter (practice calibration, both published grids read significant or material)"
           alt="This cell is ambiguous in the practice sources, so the calibrated resolution is used">
    <condition rel="deficiency of control" subject="%S" object="%MC2"/>
    <condition rel="has framework" subject="%MC2" object="US ICFR" weight="1"/>
    <condition rel="has effective magnitude band" subject="%S" object="%MB2" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%ML2" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%MP2" weight="1"/>
    <condition rel="has severity row" subject="%MP2" object="%MR2" weight="1"/>
    <condition rel="row magnitude band" subject="%MR2" object="%MB2" weight="1"/>
    <condition rel="row likelihood" subject="%MR2" object="%ML2" weight="1"/>
    <condition rel="row is ambiguous in sources" subject="%MR2" object="true" weight="1"/>
    <condition rel="ambiguous severity cell resolution" subject="%MP2" object="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] I20 - the output says when a cell was ambiguous in the sources and which way it resolved (practice calibration)"
           alt="States that this cell is ambiguous in the published practice grids and names the calibrated resolution">
    <condition rel="deficiency of control" subject="%S" object="%MC3"/>
    <condition rel="has framework" subject="%MC3" object="US ICFR" weight="1"/>
    <condition rel="has effective magnitude band" subject="%S" object="%MB3" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%ML3" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%MP3" weight="1"/>
    <condition rel="has severity row" subject="%MP3" object="%MR3" weight="1"/>
    <condition rel="row magnitude band" subject="%MR3" object="%MB3" weight="1"/>
    <condition rel="row likelihood" subject="%MR3" object="%ML3" weight="1"/>
    <condition rel="row is ambiguous in sources" subject="%MR3" object="true" weight="1"/>
    <condition rel="ambiguous severity cell resolution" subject="%MP3" object="%AMB" weight="1"/>
    <condition expression="'This combination of magnitude and likelihood is AMBIGUOUS in the sources. Both public practice grids consulted read this one cell as significant OR material and neither resolves it, so no default here could claim to be the published answer. The calibrated resolution applied is: ' + %AMB" value="%B1" weight="1"/>
    <condition expression="%B1 + '. It is exposed as a parameter precisely because the sources leave the choice open, and an institution may set it the other way with a recorded reason. Escalation remains available on the facts: an indicator or the prudent official test raises this deficiency to the highest severity regardless of how the cell resolved.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E3 - the significant deficiency definition is comparative and the grid is practice (17 CFR 240.12b-2, 17 CFR 210.1-02 a 4, AS 2201 para A11 and SEC Release 33-8829)"
           alt="States that the significant deficiency definition carries no likelihood component and no quantitative threshold, so the grid is a practice calibration">
    <condition rel="deficiency of control" subject="%S" object="%MC4"/>
    <condition rel="has framework" subject="%MC4" object="US ICFR" weight="1"/>
    <condition rel="has us severity candidate" subject="%S" object="Significant Deficiency" weight="1"/>
    <condition expression="'How the significant deficiency line was drawn, since it matters to how much weight this result bears. The operative definition is purely COMPARATIVE - less severe than a material weakness, yet important enough to merit attention by those responsible for oversight of the company s financial reporting - 17 CFR 240.12b-2, 17 CFR 210.1-02(a)(4) and AS 2201 paragraph A11. It carries NO likelihood component, and the Commission deliberately declined to add quantitative thresholds, SEC Release 33-8829. So the magnitude and likelihood grid that produced this result is not in the primary sources at all: it is a practice calibration, shipped filled from two public grids that agree cell for cell, and every cell is a parameter this institution can change. Treat the grid as a starting point for the judgement, not as the answer.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E8 - an aggregated material weakness where the combination is material and at least reasonably possible (AS 2201 paras 65 Note 2 A7 and A11)"
           alt="The combination of deficiencies reaches a material magnitude at a likelihood that is at least reasonably possible">
    <condition rel="deficiency of control" subject="%S" object="%AC1"/>
    <condition rel="has framework" subject="%AC1" object="US ICFR" weight="1"/>
    <condition rel="has aggregated magnitude band" subject="%S" object="%AB1" weight="1"/>
    <condition rel="band has rank" subject="%AB1" object="%ABR1" weight="1"/>
    <condition rel="band has rank" subject="Material" object="%MATR1" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%AL1" weight="1"/>
    <condition rel="likelihood has rank" subject="%AL1" object="%ALR1" weight="1"/>
    <condition rel="likelihood has rank" subject="Reasonably Possible" object="%RPR1" weight="1"/>
    <condition expression="%ALR1 is greater than or equal to %RPR1" weight="1"
               alt="The likelihood is at least reasonably possible"/>
    <condition expression="%ABR1 is greater than or equal to %MATR1" weight="1"
               alt="The aggregated magnitude reaches the material band"/>
  </relinst>
  <relinst type="has applicable indicator" cf="100"
           name="[US] E7 - projects each indicator supplied onto the output so it is always visible (AS 2201 para 69 and SEC Release 33-8810 II B 1)"
           alt="Carries an indicator supplied for this deficiency onto the output, whether or not it is treated as conclusive">
    <condition rel="deficiency of control" subject="%S" object="%IC0"/>
    <condition rel="has framework" subject="%IC0" object="US ICFR" weight="1"/>
    <condition rel="has indicator" subject="%S" object="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E7 I16 - fraud by senior management is an indicator of a material weakness (AS 2201 para 69 first indicator and footnote 14)"
           alt="Fraud on the part of senior management has been identified, which is an indicator of a material weakness">
    <condition rel="has indicator" subject="%S" object="Fraud By Senior Management"/>
    <condition rel="deficiency of control" subject="%S" object="%IC1" weight="1"/>
    <condition rel="has framework" subject="%IC1" object="US ICFR" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP1" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP1" object="true" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E7 I16 - a restatement correcting a material misstatement is an indicator of a material weakness (AS 2201 para 69 second indicator and footnote 15)"
           alt="A restatement to correct a material misstatement has been identified, which is an indicator of a material weakness">
    <condition rel="has indicator" subject="%S" object="Restatement Correcting Material Misstatement"/>
    <condition rel="deficiency of control" subject="%S" object="%IC2" weight="1"/>
    <condition rel="has framework" subject="%IC2" object="US ICFR" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP2" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP2" object="true" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E7 I16 - a material misstatement the control would not have detected is an indicator of a material weakness (AS 2201 para 69 third indicator)"
           alt="A material misstatement was identified in circumstances indicating internal control would not have detected it, which is an indicator of a material weakness">
    <condition rel="has indicator" subject="%S" object="Material Misstatement Found By Auditor Not By ICFR"/>
    <condition rel="deficiency of control" subject="%S" object="%IC3" weight="1"/>
    <condition rel="has framework" subject="%IC3" object="US ICFR" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP3" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP3" object="true" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E7 I16 - ineffective audit committee oversight is an indicator of a material weakness (AS 2201 para 69 fourth indicator)"
           alt="Oversight of external financial reporting and internal control by the audit committee is ineffective, which is an indicator of a material weakness">
    <condition rel="has indicator" subject="%S" object="Ineffective Audit Committee Oversight"/>
    <condition rel="deficiency of control" subject="%S" object="%IC4" weight="1"/>
    <condition rel="has framework" subject="%IC4" object="US ICFR" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP4" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP4" object="true" weight="1"/>
  </relinst>
  <relinst type="has prudent official position" object="true" cf="100"
           name="[US] E7a D14 - a stated judgement that the prudent official test is met is taken as supplied (AS 2201 para 70)"
           alt="The deficiency is recorded as one that might prevent prudent officials from concluding they have reasonable assurance, so that is taken as supplied">
    <condition rel="prudent official test applies" subject="%S" object="true"/>
  </relinst>
  <relinst type="has prudent official position" object="false" cf="100"
           name="[US] E7a D14 - a stated judgement that the prudent official test is not met is taken as supplied (AS 2201 para 70)"
           alt="The deficiency is recorded as one that would not prevent prudent officials from concluding they have reasonable assurance, so that is taken as supplied">
    <condition rel="prudent official test applies" subject="%S" object="false"/>
  </relinst>
  <relinst type="has prudent official position" object="false" cf="100"
           name="[US] E7a D14 J4 - absent a judgement the prudent official test is not treated as met (AS 2201 paras 68 and 70)"
           alt="No judgement on the prudent official test is recorded, so it is not treated as met and the reduction a compensating control supports remains available">
    <condition rel="deficiency of control" subject="%S" object="%POC" weight="1"/>
    <condition rel="has framework" subject="%POC" object="US ICFR" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prudent official test applies',*) is equal to 0" weight="1"
               alt="Whether the prudent official test is met is not recorded for this deficiency"/>
  </relinst>
  <relinst type="has us severity candidate" object="Material Weakness" cf="100"
           name="[US] E7a I16 - the prudent official test is a fifth indicator of a material weakness (AS 2201 para 70 and SEC Release 33-8810 II B 1)"
           alt="The deficiency might prevent prudent officials from concluding they have reasonable assurance, which is an indicator of a material weakness">
    <condition rel="has prudent official position" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%IC5" weight="1"/>
    <condition rel="has framework" subject="%IC5" object="US ICFR" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP5" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP5" object="true" weight="1"/>
  </relinst>
  <relinst type="has applicable indicator" object="Prudent Official Test" cf="100"
           name="[US] E7a - projects the prudent official test onto the indicator output when it applies (AS 2201 para 70)"
           alt="Records the prudent official test as an indicator that applied to this deficiency">
    <condition rel="has prudent official position" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%IC6" weight="1"/>
    <condition rel="has framework" subject="%IC6" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E7 I16 - the indicators, and the fact that their conclusiveness is a conservative choice (AS 2201 para 69 and SEC Release 33-8810 II B 1)"
           alt="Lists the indicators of a material weakness and states that treating an indicator as conclusive is a calibrated conservative reading">
    <condition rel="deficiency of control" subject="%S" object="%IF1"/>
    <condition rel="has framework" subject="%IF1" object="US ICFR" weight="1"/>
    <condition rel="has applicable indicator" subject="%S" object="%IND1" weight="1"/>
    <condition expression="'An indicator of a material weakness applies to this deficiency: ' + %IND1" value="%C1" weight="1"/>
    <condition expression="%C1 + '. Four indicators are named, AS 2201 paragraph 69 and SEC Release 33-8810 section II B 1: identification of fraud, whether or not material, on the part of senior management; restatement of previously issued financial statements to reflect the correction of a material misstatement; identification of a material misstatement in the current period in circumstances indicating it would not have been detected by internal control; and ineffective oversight of external financial reporting and internal control by the audit committee. A fifth test sits at paragraph 70: where a deficiency might prevent prudent officials from concluding they have reasonable assurance that transactions are recorded as necessary to permit preparation in accordance with the applicable accounting principles, that too is an indicator. One point of honesty about what the standard does NOT say. Both texts call these INDICATORS to be EVALUATED and neither says whether an indicator is conclusive or rebuttable. This assessment treats an indicator as establishing the highest severity on its own, which is the conservative reading, and exposes that as a parameter. Where an institution reads the standard as leaving the indicator rebuttable it can set the parameter accordingly, and the indicator will still be reported.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E7i - the indicator definitions come from the paragraph footnotes and are inputs (AS 2201 para 69 footnotes 14 and 15)"
           alt="States that seniority and the restatement test are defined by the paragraph's own footnotes and are supplied rather than derived">
    <condition rel="deficiency of control" subject="%S" object="%IF2"/>
    <condition rel="has framework" subject="%IF2" object="US ICFR" weight="1"/>
    <condition rel="has applicable indicator" subject="%S" object="%IND2" weight="1"/>
    <condition expression="'Two of the indicators turn on definitions this assessment does not attempt itself. SENIOR MANAGEMENT for the fraud indicator is defined by reference to the officers who certify the annual report, AS 2201 paragraph 69 footnote 14, so the question asked is whether the fraud was by a certifying officer and not whether a person is senior. RESTATEMENT means a restatement to correct a material misstatement as that term is used in the applicable accounting standard on accounting changes and error corrections, footnote 15, so the question asked is whether the restatement corrected a material misstatement and not whether an amount is material. Both are supplied as inputs, deliberately: classifying seniority or materiality is exactly the judgement the footnotes reserve to the people doing the work.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E7 I16 - an indicator applies but the institution has made indicators rebuttable (AS 2201 para 69, parameter indicator effect conclusive off)"
           alt="An indicator applies and this institution's calibration does not treat an indicator as conclusive, so it raises the severity for consideration only">
    <condition rel="deficiency of control" subject="%S" object="%IF3"/>
    <condition rel="has framework" subject="%IF3" object="US ICFR" weight="1"/>
    <condition rel="has applicable indicator" subject="%S" object="%IND3" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%IP6" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%IP6" object="false" weight="1"/>
    <condition expression="'An indicator applies and this institution s calibration does NOT treat an indicator as conclusive, so it has not of itself established the highest severity here. The indicator is reported and must be weighed: both texts require indicators to be EVALUATED, AS 2201 paragraph 69 and SEC Release 33-8810 section II B 1, and inspection findings single out working through an indicator checklist without considering other relevant factors as a known failure. Where an indicator applies and the severity reached is below the highest, the reason should be recorded.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E7b - severity does not depend on whether a misstatement actually occurred (AS 2201 para 64 and SEC Release 33-8810 II B 1)"
           alt="States that severity turns on the potential magnitude and not on whether a misstatement has actually happened">
    <condition rel="deficiency of control" subject="%S" object="%IF4"/>
    <condition rel="has framework" subject="%IF4" object="US ICFR" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%ET4" weight="1"/>
    <condition expression="'The severity of a deficiency does NOT depend on whether a misstatement actually occurred, AS 2201 paragraph 64 and SEC Release 33-8810 section II B 1. It depends on whether there is a reasonable possibility that the control will fail to prevent or detect a misstatement, and on the magnitude of the potential misstatement. This cuts both ways and is worth stating in both directions. A clean period does not reduce a severe deficiency, because the absence of a misstatement may be luck or may be the compensating effect of something not relied on. And a detected misstatement does not by itself make a deficiency severe, because a small error caught by a weak control is still a small error. The question is always the potential, over the whole population the control covers.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="us severity reduced by compensating control" object="true" cf="100"
           name="[US] E6 D6 - a qualifying compensating control reduces the highest severity by one step (AS 2201 para 68 and SEC 33-8810 II B 1 and fn 49)"
           alt="A qualifying compensating control applies, no indicator stands and the prudent official test does not apply, so the highest severity is reduced by one step">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%RC0" weight="1"/>
    <condition rel="has framework" subject="%RC0" object="US ICFR" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has indicator',*) is equal to 0" weight="1"
               alt="No indicator of a material weakness applies to this deficiency"/>
    <condition rel="has prudent official position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="us severity reduced by compensating control" object="false" cf="100"
           name="[US] E6a - no reduction where no compensating control is claimed for the deficiency (AS 2201 para 68)"
           alt="No compensating control has been put forward for this deficiency, so there is nothing to reduce its severity">
    <condition rel="deficiency of control" subject="%S" object="%RD0"/>
    <condition expression="countRelationshipInstances(%S,'compensating control exists',*) is equal to 0" weight="1"
               alt="No compensating control has been recorded for this deficiency either way"/>
  </relinst>
  <relinst type="us severity reduced by compensating control" object="false" cf="100"
           name="[US] E6b - no reduction where the compensating control does not qualify (AS 2201 para 68 and SEC 33-8810 fn 49)"
           alt="The compensating control put forward does not meet all four legs, so it reduces nothing">
    <condition rel="has compensating control effect" subject="%S" object="false"/>
  </relinst>
  <relinst type="us severity reduced by compensating control" object="false" cf="100"
           name="[US] E6c - no reduction where an indicator of a material weakness applies (AS 2201 paras 68 and 69)"
           alt="An indicator of a material weakness applies, so the reduction a qualifying compensating control would support is not available">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition expression="countRelationshipInstances(%S,'has indicator',*) is greater than or equal to 1" weight="1"
               alt="At least one indicator of a material weakness applies to this deficiency"/>
  </relinst>
  <relinst type="us severity reduced by compensating control" object="false" cf="100"
           name="[US] E6d - no reduction where the deficiency fails the prudent official test (AS 2201 paras 68 and 70)"
           alt="The deficiency fails the prudent official test, so the reduction a qualifying compensating control would support is not available">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition rel="has prudent official position" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has us severity candidate" object="Significant Deficiency" cf="100"
           name="[US] E6 D6 - the reduced severity is a candidate where a qualifying compensating control applies (AS 2201 para 68 and SEC 33-8810 II B 1 and fn 49)"
           alt="A qualifying compensating control applies and the matrix reached the highest severity, so the reduced severity is a candidate">
    <condition rel="us severity reduced by compensating control" subject="%S" object="true"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E6 - the reduction a qualifying compensating control supports, and its limit (AS 2201 para 68 and SEC Release 33-8810 II B 1)"
           alt="States that a qualifying compensating control may reduce the severity by one step and that it cannot displace an indicator">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%RC2" weight="1"/>
    <condition rel="has framework" subject="%RC2" object="US ICFR" weight="1"/>
    <condition expression="'A compensating control qualifies on all four legs, so it supports a reduction of one step - a material weakness to a significant deficiency - the effect of compensating controls being something the assessor should evaluate, AS 2201 paragraph 68, and a compensating control having a mitigating effect only where it operates at a level of precision that would prevent or detect a misstatement that could be material, SEC Release 33-8810 section II B 1 and footnote 49. Two limits are applied here and both matter. The reduction is ONE step and not two: nothing in the sources supports a material weakness becoming a plain deficiency on the strength of a compensating control. And a compensating control cannot displace an INDICATOR: where an indicator applies the highest severity is established on the indicator alone, and this reduction does not reach it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E6 - a qualifying compensating control is not reached where an indicator applies (AS 2201 paras 68 69 and 70)"
           alt="States that an indicator applies, so the compensating control reduction is not available however good the compensating control is">
    <condition rel="has compensating control effect" subject="%S" object="true"/>
    <condition rel="has applicable indicator" subject="%S" object="%RIND"/>
    <condition rel="deficiency of control" subject="%S" object="%RC3" weight="1"/>
    <condition rel="has framework" subject="%RC3" object="US ICFR" weight="1"/>
    <condition expression="'A compensating control qualifies, and an indicator of a material weakness also applies, so no reduction has been made. The reasoning is the structure of the standard rather than a view about this compensating control. An indicator establishes the highest severity on its own under this calibration, AS 2201 paragraphs 69 and 70, and the compensating control provision is an instruction to evaluate the effect of compensating controls on the magnitude and likelihood analysis, paragraph 68. Fraud by a certifying officer, a restatement, a misstatement internal control would not have caught, or ineffective audit committee oversight are not answered by a precise control somewhere else in the process.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity determination" object="Material Weakness" cf="100"
           name="[US] E4 E7 E8 - a material weakness governs wherever one is established (AS 2201 paras A7 69 and 70)"
           alt="A material weakness has been established, by the matrix, by an indicator or by the combination, and nothing outranks it">
    <condition rel="has us severity candidate" subject="%S" object="Material Weakness"/>
    <condition rel="us severity reduced by compensating control" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has us severity determination" object="Significant Deficiency" cf="100"
           name="[US] E3 E6 - a significant deficiency governs where no material weakness is established (AS 2201 para A11)"
           alt="A significant deficiency has been established and no material weakness stands against this deficiency">
    <condition expression="countRelationshipInstances(%S,'has us severity candidate','Material Weakness') is equal to 0" weight="1"
               alt="No material weakness has been established for this deficiency"/>
    <condition rel="has us severity candidate" subject="%S" object="Significant Deficiency"/>
  </relinst>
  <relinst type="has us severity determination" object="Significant Deficiency" cf="100"
           name="[US] E6 - a significant deficiency governs where a compensating control has reduced a material weakness (AS 2201 para 68)"
           alt="A qualifying compensating control has reduced the material weakness the analysis reached, so a significant deficiency governs">
    <condition rel="us severity reduced by compensating control" subject="%S" object="true"/>
    <condition rel="has us severity candidate" subject="%S" object="Significant Deficiency" weight="1"/>
  </relinst>
  <relinst type="has us severity determination" object="Deficiency" cf="100"
           name="[US] E2 - a deficiency is the floor where nothing more severe is established (AS 2201 para A3)"
           alt="Neither a material weakness nor a significant deficiency has been established, so the deficiency stands at the base severity">
    <condition expression="countRelationshipInstances(%S,'has us severity candidate','Material Weakness') is equal to 0" weight="1"
               alt="No material weakness has been established for this deficiency"/>
    <condition expression="countRelationshipInstances(%S,'has us severity candidate','Significant Deficiency') is equal to 0" weight="1"
               alt="No significant deficiency has been established for this deficiency"/>
    <condition rel="has us severity candidate" subject="%S" object="Deficiency"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E4 G3 - reason for a material weakness reached on the magnitude and likelihood analysis (AS 2201 paras A7 63 to 66)"
           alt="Explains a material weakness reached through the magnitude and likelihood analysis rather than through an indicator">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="has effective magnitude band" subject="%S" object="%RB1" weight="1"/>
    <condition rel="has likelihood" subject="%S" object="%RL1" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has applicable indicator',*) is equal to 0" weight="1"
               alt="No indicator of a material weakness applies to this deficiency"/>
    <condition expression="'Material weakness, on the magnitude and likelihood analysis and not on an indicator. Potential magnitude: ' + %RB1" value="%D1" weight="1"/>
    <condition expression="%D1 + '. Likelihood: ' + %RL1" value="%D2" weight="1"/>
    <condition expression="%D2 + '. A material weakness is a deficiency, or a combination of deficiencies, such that there is a reasonable possibility that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis, AS 2201 paragraph A7, and reasonable possibility means a likelihood that is reasonably possible or probable, paragraph A7 Note. Both limbs are met on the judgements supplied. No indicator was needed to reach this and none was found. The magnitude and likelihood judgements are inputs, and the grid that maps them is a practice calibration rather than a sourced rule, so a reader who disagrees should disagree with a judgement or a parameter rather than with the derivation.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E7 E7a G3 - reason for a material weakness established by an indicator (AS 2201 paras 69 and 70)"
           alt="Explains a material weakness established by an indicator rather than by the magnitude and likelihood analysis">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="has applicable indicator" subject="%S" object="%RI2" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%RP2" weight="1"/>
    <condition rel="indicator effect conclusive" subject="%RP2" object="true" weight="1"/>
    <condition expression="'Material weakness, established by an indicator: ' + %RI2" value="%E1" weight="1"/>
    <condition expression="%E1 + '. Under this institution s calibration an indicator establishes the highest severity on its own, so this result does not depend on the magnitude and likelihood grid and would stand even on a lower magnitude judgement, AS 2201 paragraphs 69 and 70. Two honest qualifications. The standard calls these indicators to be EVALUATED and does not itself say they are conclusive, so the conclusiveness is this pack s conservative reading and is a parameter. And a compensating control does not displace an indicator here, however precise it is. Where the institution reads the standard differently the parameter is where to change it, and the change is recorded rather than silent.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E8 G3 - reason for a material weakness reached only in combination (AS 2201 para 65 Note 2)"
           alt="Explains a material weakness that the deficiency reaches only when combined with others in its group">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="has aggregated magnitude band" subject="%S" object="%RA3" weight="1"/>
    <condition rel="has magnitude band" subject="%S" object="%RO3" weight="1"/>
    <condition rel="band has rank" subject="%RA3" object="%RAR3" weight="1"/>
    <condition rel="band has rank" subject="%RO3" object="%ROR3" weight="1"/>
    <condition expression="%RAR3 is greater than %ROR3" weight="1"
               alt="The combination carries a higher magnitude than this deficiency on its own"/>
    <condition expression="'This material weakness is reached in COMBINATION and not by this deficiency alone. On its own the potential magnitude was judged ' + %RO3" value="%F1" weight="1"/>
    <condition expression="%F1 + ', and taken with the other deficiencies affecting the same group it reaches ' + %RA3" value="%F2" weight="1"/>
    <condition expression="%F2 + '. Two of the three severity definitions say OR A COMBINATION OF DEFICIENCIES in terms, and the standard requires the assessor to evaluate the effect of multiple deficiencies on the same account, disclosure or component, AS 2201 paragraph 65 Note 2. So the obligation to look across the group is not discretionary. The practical consequence is that remediating this one deficiency does not by itself clear the weakness: the group is the unit, and the aggregation finding above names the group and its size.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E3 E6 G3 - reason for a significant deficiency determination (AS 2201 paras A11 and 68)"
           alt="Explains a significant deficiency, what it obliges and what it does not">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
    <condition expression="'Significant deficiency: less severe than a material weakness, yet important enough to merit attention by those responsible for oversight of the company s financial reporting, AS 2201 paragraph A11. Two consequences follow and they are different in kind. It must be communicated in writing to the audit committee, and it is NOT publicly disclosed, so a significant deficiency determination is not a disclosure event. It also does not preclude a conclusion that internal control over financial reporting is effective, which is precisely why the line between this and a material weakness carries so much weight and why the judgements behind it should be recorded. Where this result follows a compensating control reduction, the reduction and its limits are stated in the findings above.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E2 G3 - reason for a plain deficiency determination (AS 2201 para A3)"
           alt="Explains a base deficiency determination and that it is not a clean result">
    <condition rel="has us severity determination" subject="%S" object="Deficiency"/>
    <condition expression="'Control deficiency, at the base severity. A deficiency exists where the design or operation of a control does not allow management or employees, in the normal course of performing their assigned functions, to prevent or detect misstatements on a timely basis, AS 2201 paragraph A3. On the judgements supplied it is neither important enough to merit the attention of those charged with oversight nor a reasonable possibility of a material misstatement. This is not a clean result and it is not nothing: the control did not do what it was designed to do. It carries no external communication or disclosure obligation on this path, and it does count towards any combination affecting the same account, disclosure or component - so the same deficiency can become severe later without any new failure, simply by being joined.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity reason" cf="100"
           name="[US] E1 G6 G3 - reason no US severity determination was reached (AS 2201 paras 63 to 66)"
           alt="Explains that the facts supplied do not reach any severity candidate and points to the open questions">
    <condition rel="deficiency of control" subject="%S" object="%RNC"/>
    <condition rel="has framework" subject="%RNC" object="US ICFR" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%RNT" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has us severity candidate',*) is equal to 0" weight="1"
               alt="No severity candidate could be derived from the facts supplied for this deficiency"/>
    <condition expression="'No severity determination. A deficiency record exists but the facts supplied do not reach any severity, and no severity has been assumed in either direction. Severity rests on the potential magnitude of the misstatement the control could fail to prevent or detect and on the likelihood of that failure, AS 2201 paragraphs 63 to 66, and both are judgements the institution supplies: this assessment will not invent either, because inventing them would mean answering the very question it was asked to evaluate. The open questions listed with this result name what is still needed. Until they are answered the deficiency stands unevaluated, which is itself a reportable state of affairs rather than a neutral one.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has restatement statement" cf="100"
           name="[US] E16 - a restatement is an indicator for this period and does not reopen the prior conclusion (AS 2201 para 69 second indicator and SEC Release 33-8810 II B 4)"
           alt="States how the restatement indicator and the no-reopening position sit together without conflict">
    <condition rel="has indicator" subject="%S" object="Restatement Correcting Material Misstatement"/>
    <condition rel="deficiency of control" subject="%S" object="%SC1" weight="1"/>
    <condition rel="has framework" subject="%SC1" object="US ICFR" weight="1"/>
    <condition expression="'A restatement correcting a material misstatement is in point, and two source positions apply at once. For the period UNDER ASSESSMENT it is an indicator of a material weakness, AS 2201 paragraph 69 second indicator. For the PRIOR period it does NOT, by itself, require management to reconsider its previous conclusion on the effectiveness of internal control over financial reporting, and there is no requirement to reassess or revise the previously filed conclusion, SEC Release 33-8810 section II B 4. These are not in conflict and this assessment holds them apart: the indicator applies only to the period being assessed, and no rule here reaches back to a prior-period determination or disturbs it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has restatement statement" cf="100"
           name="[US] E16 - the prior disclosures should be considered and supplemented if misleading (SEC Release 33-8810 II B 4)"
           alt="States the two board or management actions a restatement calls for in relation to the prior disclosures">
    <condition rel="restatement relates to previously issued period" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%SC2" weight="1"/>
    <condition rel="has framework" subject="%SC2" object="US ICFR" weight="1"/>
    <condition expression="'Two actions follow for management and the board, and neither is a determination this assessment makes. Management should consider whether its ORIGINAL disclosures remain appropriate and should supplement them so they are not misleading. And a material change to internal control over financial reporting is itself disclosable, SEC Release 33-8810 section II B 4. The distinction the release draws is a narrow one and easy to overstate in either direction: the prior conclusion is not reopened, and the prior DISCLOSURES are not thereby beyond review.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Prior disclosures considered for continued appropriateness" cf="100"
           name="[US] E16 - prior disclosures are considered for continued appropriateness (SEC Release 33-8810 II B 4)"
           alt="Records that the prior disclosures should be considered for continued appropriateness">
    <condition rel="restatement relates to previously issued period" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%SC3" weight="1"/>
    <condition rel="has framework" subject="%SC3" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Material change to internal control disclosed under Item 308 c" cf="100"
           name="[US] E16 - a material change to internal control is disclosable in its own right (Regulation S-K Item 308 c, 17 CFR 229.308 c)"
           alt="Records that a material change to internal control arising from the restatement is itself disclosable">
    <condition rel="restatement relates to previously issued period" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%SC4" weight="1"/>
    <condition rel="has framework" subject="%SC4" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has restatement statement" cf="100"
           name="[US] E16 - a prior period determination is not disturbed by this assessment (SEC Release 33-8810 II B 4)"
           alt="States that a prior period determination exists and that this assessment neither reads nor revises it">
    <condition rel="prior period determination exists" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%SC5" weight="1"/>
    <condition rel="has framework" subject="%SC5" object="US ICFR" weight="1"/>
    <condition expression="'A determination exists for a prior period. This assessment does not read it, does not revise it and reaches no conclusion about it. That is a deliberate boundary rather than a limitation of the data: a restatement does not by itself require the prior conclusion to be reconsidered, SEC Release 33-8810 section II B 4, and a model that quietly re-derived a prior year from this year s facts would be doing exactly what the release says is not required - and doing it on a record that was never designed to support it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="PCAOB AS 2201 as cited AS No 5 text" cf="100"
           name="[US] E1 G8 - the auditing standard version this severity determination rests on (AS 2201 paras 62 to 70)"
           alt="Names the version of the auditing standard this severity determination rests on">
    <condition rel="has us severity determination" subject="%S" object="%VD1"/>
    <condition rel="deficiency of control" subject="%S" object="%VC1" weight="1"/>
    <condition rel="has framework" subject="%VC1" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="SEC Release 33-8810 of 20 June 2007" cf="100"
           name="[US] E1 G8 - the management guidance version this severity determination rests on (SEC Release 33-8810 II B 1)"
           alt="Names the version of the management guidance this severity determination rests on">
    <condition rel="has us severity determination" subject="%S" object="%VD2"/>
    <condition rel="deficiency of control" subject="%S" object="%VC2" weight="1"/>
    <condition rel="has framework" subject="%VC2" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="SEC Release 33-8829 effective 10 September 2007" cf="100"
           name="[US] E3 G8 - the release that fixed the significant deficiency definition (SEC Release 33-8829)"
           alt="Names the release that settled the definition of a significant deficiency without a likelihood component">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
    <condition rel="deficiency of control" subject="%S" object="%VC3" weight="1"/>
    <condition rel="has framework" subject="%VC3" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[US] E7 G6 - whether any indicator of a material weakness applies (AS 2201 paras 69 and 70)"
           alt="No indicator has been supplied and no answer has been recorded on the prudent official test">
    <condition rel="deficiency of control" subject="%S" object="%QC1"/>
    <condition rel="has framework" subject="%QC1" object="US ICFR" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%QT1" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has indicator',*) is equal to 0" weight="1"
               alt="No indicator has been supplied for this deficiency"/>
    <condition expression="countRelationshipInstances(%S,'prudent official test applies',*) is equal to 0" weight="1"
               alt="No answer has been recorded on the prudent official test"/>
    <condition expression="'Whether any indicator of a material weakness applies, and whether the prudent official test is met. Five questions, each answerable yes or no: fraud by a certifying officer; a restatement correcting a material misstatement; a material misstatement identified in circumstances indicating internal control would not have detected it; ineffective audit committee oversight; and whether the deficiency might prevent prudent officials from concluding they have reasonable assurance, AS 2201 paragraphs 69 and 70. Each independently establishes the highest severity under this calibration, so leaving them unanswered means the severity reported rests on the magnitude and likelihood grid alone - and the grid is the practice part of the method, not the sourced part.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[US] E7a G6 - the prudent official test has not been answered (AS 2201 para 70)"
           alt="An indicator has been supplied but the prudent official test has not been answered">
    <condition rel="deficiency of control" subject="%S" object="%QC2"/>
    <condition rel="has framework" subject="%QC2" object="US ICFR" weight="1"/>
    <condition rel="has indicator" subject="%S" object="%QI2" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'prudent official test applies',*) is equal to 0" weight="1"
               alt="No answer has been recorded on the prudent official test"/>
    <condition expression="'Whether the prudent official test is met: would this deficiency, alone or in combination, prevent prudent officials in the conduct of their own affairs from concluding that they have reasonable assurance that transactions are recorded as necessary to permit preparation of the financial statements in accordance with the applicable accounting principles, AS 2201 paragraph 70. It is the broadest of the five tests and the one most often skipped, because it asks for a judgement rather than a fact. It is also the one that catches a deficiency the four specific indicators miss.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has judgement input" object="The Audit Committee" cf="100"
           name="[US] E7a G5 - the prudent official test is a judgement the audit committee should own (AS 2201 para 70)"
           alt="Names the prudent official test as a judgement input and the body that should own it">
    <condition rel="prudent official test applies" subject="%S" object="%PJ1"/>
    <condition rel="deficiency of control" subject="%S" object="%PJC" weight="1"/>
    <condition rel="has framework" subject="%PJC" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Material Control Did Not Operate Effectively" cf="100"
           name="[UK] F2 - candidate did not operate effectively where a failure stands at the balance sheet date (FRC Guidance 2024 para 297 first limb, Provision 29 third bullet)"
           alt="A deficiency in this material control still stands at the balance sheet date, so the control did not operate effectively at that date">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has deficiency" subject="%S" object="%UD1" weight="1"/>
    <condition rel="persists at period end" subject="%UD1" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Material Control Did Not Operate Effectively" cf="100"
           name="[UK] F1c - candidate did not operate effectively where the control is defectively designed (FRC Guidance 2024 para 297 third limb, ISA UK 265 para 6 a i)"
           alt="This material control is defectively designed, and effectiveness for the declaration covers design and implementation and not operation alone">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has design assessment" subject="%S" object="Design Deficient" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Material Control Did Not Operate Effectively" cf="100"
           name="[UK] F1c F2 - candidate did not operate effectively on an adverse operating conclusion (FRC Guidance 2024 para 297 first limb)"
           alt="The operating effectiveness conclusion for this material control is adverse, so the control did not operate effectively">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Not Operating Effectively" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Effectiveness Not Determinable" cf="100"
           name="[UK] F9a - candidate effectiveness not determinable where the evidence does not support a conclusion (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="The evidence obtained for this material control does not support a conclusion either way, so its effectiveness at the balance sheet date cannot be determined">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Insufficient Evidence" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Effectiveness Not Determinable" cf="100"
           name="[UK] F9a - candidate effectiveness not determinable where no operating conclusion was reached (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="No operating conclusion was reached for this material control, so its effectiveness at the balance sheet date cannot be determined">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has operating effectiveness conclusion" subject="%S" object="No Operating Determination" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Effectiveness Not Determinable" cf="100"
           name="[UK] F1c F9a - candidate effectiveness not determinable where the design could not be determined (FRC Corporate Governance Code Guidance 2024 paras 297 and 298)"
           alt="The design of this material control could not be determined, and the declaration covers design as well as operation">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has design assessment" subject="%S" object="No Design Determination" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Material Control Operated Effectively" cf="100"
           name="[UK] F1 F1c F4 - candidate operated effectively where design and operation clear and no deficiency stands (FRC Guidance 2024 para 297, Mythbuster 29 January 2026)"
           alt="This material control is effectively designed, operated effectively on the testing, and no deficiency stands against it at the balance sheet date">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has design assessment" subject="%S" object="Design Effective" weight="1"/>
    <condition rel="has operating effectiveness conclusion" subject="%S" object="Operating Effective" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has persisting deficiency',*) is equal to 0" weight="1"
               alt="No deficiency in this control stands unremediated at the balance sheet date"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="Material Control Operated Effectively" cf="100"
           name="[UK] F4 - candidate operated effectively where the in period failure was remediated and retested in time (FRC Mythbuster 29 January 2026, Guidance para 297)"
           alt="The in-period failure in this material control was remediated and retested before the balance sheet date, so the control operated effectively at that date">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition rel="has design assessment" subject="%S" object="Design Effective" weight="1"/>
    <condition rel="has deficiency" subject="%S" object="%UD2" weight="1"/>
    <condition rel="persists at period end" subject="%UD2" object="false" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has persisting deficiency',*) is equal to 0" weight="1"
               alt="No other deficiency in this control stands unremediated at the balance sheet date"/>
  </relinst>
  <relinst type="has persisting deficiency" cf="100"
           name="[UK] F2 - projects a deficiency standing at the balance sheet date onto the control (FRC Corporate Governance Code Guidance 2024 para 297 first limb)"
           alt="Carries a deficiency that still stands at the balance sheet date onto the control, so the declaration can be reached without counting across two hops">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has deficiency" subject="%S" object="%O" weight="1"/>
    <condition rel="persists at period end" subject="%O" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk declaration candidate" object="No Declaration Consequence" cf="100"
           name="[UK] F5 - candidate no declaration consequence where the control is not a material control (Provision 29 second bullet, FRC Guidance para 270)"
           alt="This control is not designated a material control, so its effectiveness is not the subject of the Provision 29 declaration">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="false" weight="1"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk declaration determination" object="Material Control Did Not Operate Effectively" cf="100"
           name="[UK] F2 - an established failure standing at the balance sheet date governs the declaration (UK Corporate Governance Code 2024 Provision 29 third bullet)"
           alt="An established failure stands at the balance sheet date, which outranks every other declaration outcome">
    <condition rel="has uk declaration candidate" subject="%S" object="Material Control Did Not Operate Effectively"/>
  </relinst>
  <relinst type="has uk declaration determination" object="Effectiveness Not Determinable" cf="100"
           name="[UK] F9a - effectiveness not determinable governs where no established failure stands (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="The evidence does not reach a conclusion and no established failure stands at the balance sheet date">
    <condition expression="countRelationshipInstances(%S,'has uk declaration candidate','Material Control Did Not Operate Effectively') is equal to 0" weight="1"
               alt="No established failure stands against this material control at the balance sheet date"/>
    <condition rel="has uk declaration candidate" subject="%S" object="Effectiveness Not Determinable"/>
  </relinst>
  <relinst type="has uk declaration determination" object="Material Control Operated Effectively" cf="100"
           name="[UK] F1 F4 - operated effectively governs only where nothing adverse and nothing undetermined stands (FRC Corporate Governance Code Guidance 2024 paras 296 and 297)"
           alt="Every gate is positively cleared, no established failure stands at the balance sheet date and nothing is undetermined">
    <condition expression="countRelationshipInstances(%S,'has uk declaration candidate','Material Control Did Not Operate Effectively') is equal to 0" weight="1"
               alt="No established failure stands against this material control at the balance sheet date"/>
    <condition expression="countRelationshipInstances(%S,'has uk declaration candidate','Effectiveness Not Determinable') is equal to 0" weight="1"
               alt="Nothing about this material control is left undetermined"/>
    <condition rel="has uk declaration candidate" subject="%S" object="Material Control Operated Effectively"/>
  </relinst>
  <relinst type="has uk declaration determination" object="No Declaration Consequence" cf="100"
           name="[UK] F5 - a control outside the material control designation has no declaration outcome (UK Corporate Governance Code 2024 Provision 29 second bullet)"
           alt="This control is not a material control, so the declaration reaches no outcome about it">
    <condition rel="has uk declaration candidate" subject="%S" object="No Declaration Consequence"/>
  </relinst>
  <relinst type="has uk declaration determination" object="Effectiveness Not Determinable" cf="100"
           name="[UK] F9a G6 - no declaration candidate was reached on the facts supplied (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="The facts supplied reach no declaration outcome, so the effectiveness of this control at the balance sheet date is not determinable on them">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has uk declaration candidate',*) is equal to 0" weight="1"
               alt="No declaration candidate could be derived from the facts supplied for this control"/>
  </relinst>
  <relinst type="must be described in the declaration" object="true" cf="100"
           name="[UK] F2 F3 - a material control not operating effectively at the balance sheet date must be described (Code 2024 Provision 29 third bullet, FRC Guidance para 297)"
           alt="This material control did not operate effectively at the balance sheet date, so it must be described in the declaration">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Did Not Operate Effectively"/>
  </relinst>
  <relinst type="must be described in the declaration" object="false" cf="100"
           name="[UK] F4 - a material control effective at the balance sheet date need not be described (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="This material control operated effectively at the balance sheet date, so there is nothing for the declaration to describe">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Operated Effectively"/>
  </relinst>
  <relinst type="must be described in the declaration" object="false" cf="100"
           name="[UK] F5 - a control outside the designation is not described in the declaration (UK Corporate Governance Code 2024 Provision 29 second bullet)"
           alt="This control is not a material control, so it is not a subject of the declaration at all">
    <condition rel="has uk declaration determination" subject="%S" object="No Declaration Consequence"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Declaration of effectiveness of material controls at the balance sheet date" cf="100"
           name="[UK] F1 F3 - the declaration itself is the second Provision 29 bullet (UK Corporate Governance Code 2024 Provision 29 second bullet and FRC Guidance para 290)"
           alt="Names the declaration of effectiveness as at the balance sheet date as a required disclosure for this material control">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Description of material controls that did not operate effectively" cf="100"
           name="[UK] F3 - the description of the controls that did not operate effectively (UK Corporate Governance Code 2024 Provision 29 third bullet first element)"
           alt="A description of this material control and how it failed is a required element of the declaration">
    <condition rel="must be described in the declaration" subject="%S" object="true"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Action taken or proposed to improve those controls" cf="100"
           name="[UK] F3 - the action taken or proposed to improve the control (UK Corporate Governance Code 2024 Provision 29 third bullet second element)"
           alt="The action taken, or proposed, to improve this control is a required element of the declaration">
    <condition rel="must be described in the declaration" subject="%S" object="true"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Action taken to address previously reported issues" cf="100"
           name="[UK] F7 - the third element is triggered by what was previously reported, not the current conclusion (Code 2024 Provision 29 third bullet, FRC Guidance para 297)"
           alt="A deficiency in this control was reported in a previous declaration, so the action taken to address it is a required element whatever this year's conclusion is">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="has deficiency" subject="%S" object="%UD3" weight="1"/>
    <condition rel="reported in prior year declaration" subject="%UD3" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk disclosure element" object="Explanation under comply or explain where no declaration can be given" cf="100"
           name="[UK] F9a - the comply or explain route where effectiveness cannot be determined (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="Effectiveness cannot be determined, so the board may explain the position in the annual report under the comply or explain nature of the Code">
    <condition rel="has uk declaration determination" subject="%S" object="Effectiveness Not Determinable"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F1a - the two dates, and why a clean declaration can sit beside an in period failure (Code 2024 Provision 29, FRC Guidance paras 281 and 296)"
           alt="Explains that the declaration is a point in time at the balance sheet date while the review behind it covers the period">
    <condition rel="has uk declaration determination" subject="%S" object="%UF1"/>
    <condition expression="'The two dates this result depends on, which are easy to conflate. The DECLARATION is as at the balance sheet date: a point in time, Provision 29 second bullet and FRC guidance paragraph 296. The REVIEW behind it is period based, running the full year up to and including that date, paragraph 281. So a period-based review can properly find a failure during the year while the point-in-time declaration stays clean. That is what the provision says rather than a gap in it, and it is why this assessment reads whether a deficiency STILL STANDS at the balance sheet date and not whether a failure happened.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F1c F10d - declaration effectiveness covers design and implementation, not operation alone (FRC Guidance 2024 para 297, ISA UK 265 para 6 a)"
           alt="Explains that the declaration test is wider than operation, covering design and implementation too">
    <condition rel="has uk declaration determination" subject="%S" object="%UF2"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="'What effectiveness means here, and why it is wider than a clean test result. The declaration covers design and implementation as well as operation, FRC guidance paragraph 297 third limb, and the international definition of a deficiency has the same three limbs plus a fourth - a control designed, implemented or operated such that it cannot prevent, or detect and correct, misstatements on a timely basis, or a necessary control missing, ISA UK 265 paragraph 6 a. The implementation limb matters in practice: a control that is well designed on paper and never actually put in place is deficient, and a sample of zero instances will not say so. A defectively designed material control therefore fails the balance-sheet-date test even where every instance tested passed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F4c - a later procedure evidences the balance sheet date position and does not cure it (FRC Corporate Governance Code Guidance 2024 para 300)"
           alt="States the narrow reading taken of post balance sheet date procedures, and that the sources do not resolve the point">
    <condition rel="has uk declaration determination" subject="%S" object="%UF3"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="'A choice made where the sources are silent, stated so it can be challenged. Procedures carried out after the balance sheet date may be RELEVANT TO the declaration, and the declaration covers information collected before and on that date, FRC guidance paragraph 300. Whether such a procedure can CURE a control that was ineffective at the balance sheet date, or only EVIDENCE that it was in fact effective then, is stated nowhere in the fetched sources. This assessment takes the narrow reading - later work evidences the position at that date and cannot change it - because that is what as at the balance sheet date requires. An institution reading it more widely should record the reading and the reason.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F4d - a declaration already made is not voided by a later discovery (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="States that effectiveness is declared as at the balance sheet date and that there is no duty to revise it for later discoveries">
    <condition rel="has uk declaration determination" subject="%S" object="%UF4"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="'One consequence of the point-in-time test worth stating plainly. Effectiveness is declared as at the balance sheet date, and a matter discovered afterwards does not void a declaration already properly made, FRC Provision 29 Mythbuster, 29 January 2026. This is not a licence to look away: a later discovery is evidence about the position at that date, it falls into the next period s review, and anything significant is reported to the board whether or not the declaration changes.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F9b - disclosure is required and the board may still withhold commercially sensitive detail (FRC Corporate Governance Code Guidance 2024 para 299)"
           alt="States that a required disclosure stands while the board may withhold detail that would reveal confidential information">
    <condition rel="must be described in the declaration" subject="%S" object="true"/>
    <condition rel="has deficiency" subject="%S" object="%UD4" weight="1"/>
    <condition rel="disclosure would reveal confidential information" subject="%UD4" object="true" weight="1"/>
    <condition expression="'The disclosure obligation stands, and the level of detail is a board judgement. No disclosure of an improvement area or a remedial action is expected where, in the board s professional judgement, it would reveal confidential information or something that could inadvertently affect the company s interests if publicly reported, FRC guidance paragraph 299. So the control and the action are described, and the technical detail that would create the exposure need not be. This is a limit on DETAIL and not a route to silence: the element itself is still required.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F4b F12 - a remediated failure still reaches the board and still calls for root cause work (FRC Corporate Governance Code Guidance 2024 paras 262 284 and 287)"
           alt="States that a remediated in-period failure still produces an internal escalation and root cause obligation even where no disclosure follows">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Operated Effectively"/>
    <condition rel="has deficiency" subject="%S" object="%UD5" weight="1"/>
    <condition rel="persists at period end" subject="%UD5" object="false" weight="1"/>
    <condition expression="'A clean declaration does not end the matter internally. Any significant issue should be reported to the board EVEN IF IT HAS BEEN REMEDIATED, with the actions taken, FRC guidance paragraph 262, and the annual review must consider the incidence of significant control failings and the action taken on material controls that did not operate effectively, paragraph 284. Where an improvement area emerges the board should establish how it arose, its impact and how effective the remedial measures were, and re-evaluate its monitoring processes, paragraph 287. So this failure produces an internal escalation and a root cause obligation while producing no declaration consequence - two different questions with two different answers.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F13 - the board defined terms the sources do not align (FRC Corporate Governance Code Guidance 2024 paras 250 287 288 and 289)"
           alt="States that the UK vocabulary around a failing is board defined and that the sources assert no ordering between the terms">
    <condition rel="has uk declaration determination" subject="%S" object="%UF5"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="'Four terms, no ordering. A SIGNIFICANT CONTROL FAILING is a term the board itself must define, FRC guidance paragraph 250. A MATERIAL CONTROL NOT OPERATING EFFECTIVELY is the Code s disclosure trigger. An IMPROVEMENT AREA, paragraph 288, and a NEAR MISS, paragraph 289, are separate again. No fetched source states how the four relate to one another or ranks them, so this assessment takes each as a supplied value with its own consequence and asserts no ordering between them. An institution that wants an ordering must define one and record it, because the sources will not supply it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F5 - a non material control still carries a deficiency record and a communication test (Code 2024 Provision 29, ISA UK 265 para 10 b)"
           alt="States that no declaration consequence is not the same as no consequence for a control outside the designation">
    <condition rel="has uk declaration determination" subject="%S" object="No Declaration Consequence"/>
    <condition expression="'No declaration consequence is not the same as no consequence. The Provision 29 declaration is about MATERIAL controls, second bullet, and this control is not designated one, so its failure does not enter the declaration. The deficiency is still recorded, it is still classified on the international three-way test, and a deficiency of sufficient importance to merit management s attention is still communicated to management at an appropriate level of responsibility, ISA UK 265 paragraph 10 b. The designation also belongs to the board and can change: a control outside it this year is not outside it permanently.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration reason" cf="100"
           name="[UK] F2 F3 G3 - reason a material control did not operate effectively at the balance sheet date (Code 2024 Provision 29, FRC Guidance para 297)"
           alt="Explains the adverse declaration outcome and the three disclosure elements it brings with it">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Did Not Operate Effectively"/>
    <condition expression="'This material control did not operate effectively as at the balance sheet date. The trigger in the guidance is a material control not operating effectively at the date of the balance sheet, paragraph 297 first limb, and an issue persisting at that date is expressly one the FRC expects to see reported. The declaration must therefore describe the control and how it failed, and the action taken OR PROPOSED to improve it, Provision 29 third bullet. The or proposed wording matters: remediation that is only planned still satisfies the element, so there is no incentive to delay the disclosure until the work is finished. Effectiveness here covers design and implementation as well as operation, so the finding may rest on how the control is built rather than on a failed test.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration reason" cf="100"
           name="[UK] F1 F1b F4 G3 - reason a material control operated effectively at the balance sheet date (FRC Corporate Governance Code Guidance 2024 paras 286 296 and 297)"
           alt="Explains the favourable declaration outcome and how far it goes">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Operated Effectively"/>
    <condition expression="'This material control operated effectively as at the balance sheet date. Every gate is positively cleared rather than merely unchallenged: the design is effective, the testing supports the operating conclusion, and no deficiency stands against the control at that date. Where a failure occurred during the year and was remediated and retested before the balance sheet date, there is no expectation that it is reported in the declaration, FRC Provision 29 Mythbuster of 29 January 2026. How far this goes: it is a reasonable conclusion drawn from the work carried out and the evidence obtained, not a guarantee and not absolute certainty, paragraph 296, and an effective control reduces but does not eliminate the underlying risk, paragraph 286. It is about this control and not about the bank s framework.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration reason" cf="100"
           name="[UK] F9a G3 - reason effectiveness could not be determined and what the Code permits (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="Explains the not determinable outcome, the comply or explain route, and that this is not a clean declaration">
    <condition rel="has uk declaration determination" subject="%S" object="Effectiveness Not Determinable"/>
    <condition expression="'The effectiveness of this material control as at the balance sheet date could not be determined on the facts supplied. Nothing has been established against the control and nothing in its favour, so this is neither a clean declaration nor an adverse one. Where the board cannot determine effectiveness, or cannot give a declaration, it COULD rely on the comply or explain nature of the Code and explain the position in the annual report, FRC guidance paragraph 298. The guidance is permissive and names no alternative, so this outcome names an option rather than asserting a duty. It is also the point at which the two overlays in this model genuinely differ: on the other path an inability to assess is not a permitted scope limitation and a conclusion is compelled. The open questions listed with this result name what would close the gap.'" value="%O"/>
  </relinst>
  <relinst type="has uk declaration reason" cf="100"
           name="[UK] F5 G3 - reason a control outside the designation reaches no declaration outcome (Code 2024 Provision 29, FRC Guidance paras 270 to 271)"
           alt="Explains why a control outside the material control designation reaches no declaration outcome">
    <condition rel="has uk declaration determination" subject="%S" object="No Declaration Consequence"/>
    <condition expression="'This control is not designated a material control, so it reaches no declaration outcome. The designation is the board s and nobody else s: it is not the FRC s role or intention to prescribe or dictate what a material control is for a company, guidance executive summary paragraph 8, material controls are company specific by size, business model, strategy, operations, structure and complexity, paragraph 270, and the test the board applies is how a hypothetical deficiency in the control could impact the interests of the company, shareholders and other stakeholders, paragraph 271. This assessment consumes that designation and never derives it. Anything found about this control is still recorded and still classified.'" value="%O"/>
  </relinst>
  <relinst type="has international classification candidate" object="Significant Deficiency Reportable To Those Charged With Governance" cf="100"
           name="[UK] F10e - candidate significant deficiency where the deficiency merits the attention of those charged with governance (ISA UK 265 paras 6 b and 9)"
           alt="This deficiency merits the attention of those charged with governance, which is the definition of a significant deficiency on this path">
    <condition rel="merits attention of those charged with governance" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%KC1" weight="1"/>
    <condition rel="has framework" subject="%KC1" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has international classification candidate" object="Deficiency Meriting Management Attention" cf="100"
           name="[UK] F10e I27 - candidate deficiency meriting management attention but not that of those charged with governance (ISA UK 265 para 10 b)"
           alt="This deficiency is of sufficient importance to merit management's attention and does not merit the attention of those charged with governance">
    <condition rel="merits management attention" subject="%S" object="true"/>
    <condition rel="merits attention of those charged with governance" subject="%S" object="false" weight="1"/>
    <condition rel="deficiency of control" subject="%S" object="%KC2" weight="1"/>
    <condition rel="has framework" subject="%KC2" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has international classification candidate" object="Deficiency Meriting Neither" cf="100"
           name="[UK] F10e I27 - candidate deficiency meriting neither where both judgements are answered in the negative (ISA UK 265 paras 6 b 10 b and A22)"
           alt="This deficiency merits neither the attention of those charged with governance nor management's attention on the judgements supplied">
    <condition rel="merits attention of those charged with governance" subject="%S" object="false"/>
    <condition rel="merits management attention" subject="%S" object="false" weight="1"/>
    <condition rel="deficiency of control" subject="%S" object="%KC3" weight="1"/>
    <condition rel="has framework" subject="%KC3" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has international classification candidate" object="Significant Deficiency Reportable To Those Charged With Governance" cf="100"
           name="[UK] F10f I26 - candidate significant deficiency from an indicator only where the institution has made indicators conclusive (ISA UK 265 paras A6 and A7, parameter)"
           alt="An international significance indicator applies and this institution has chosen to treat an indicator as establishing the classification on this path">
    <condition rel="has international significance indicator" subject="%S" object="%KI1"/>
    <condition rel="deficiency of control" subject="%S" object="%KC4" weight="1"/>
    <condition rel="has framework" subject="%KC4" object="UK Material Controls" weight="1"/>
    <condition rel="deficiency applies testing policy" subject="%S" object="%KP1" weight="1"/>
    <condition rel="international indicator effect conclusive" subject="%KP1" object="true" weight="1"/>
  </relinst>
  <relinst type="has international classification" object="Significant Deficiency Reportable To Those Charged With Governance" cf="100"
           name="[UK] F10e - a significant deficiency governs the classification (ISA UK 265 paras 6 b and 9)"
           alt="This deficiency merits the attention of those charged with governance, which is the highest of the three classes">
    <condition rel="has international classification candidate" subject="%S" object="Significant Deficiency Reportable To Those Charged With Governance"/>
  </relinst>
  <relinst type="has international classification" object="Deficiency Meriting Management Attention" cf="100"
           name="[UK] F10e - a deficiency meriting management attention governs where it is not a significant deficiency (ISA UK 265 para 10 b)"
           alt="This deficiency merits management's attention and does not reach the class reportable to those charged with governance">
    <condition expression="countRelationshipInstances(%S,'has international classification candidate','Significant Deficiency Reportable To Those Charged With Governance') is equal to 0" weight="1"
               alt="This deficiency does not reach the class reportable to those charged with governance"/>
    <condition rel="has international classification candidate" subject="%S" object="Deficiency Meriting Management Attention"/>
  </relinst>
  <relinst type="has international classification" object="Deficiency Meriting Neither" cf="100"
           name="[UK] F10e - a deficiency meriting neither is the base class where neither higher class is reached (ISA UK 265 paras 6 a and A22)"
           alt="This deficiency reaches neither of the two higher classes on the judgements supplied">
    <condition expression="countRelationshipInstances(%S,'has international classification candidate','Significant Deficiency Reportable To Those Charged With Governance') is equal to 0" weight="1"
               alt="This deficiency does not reach the class reportable to those charged with governance"/>
    <condition expression="countRelationshipInstances(%S,'has international classification candidate','Deficiency Meriting Management Attention') is equal to 0" weight="1"
               alt="This deficiency does not reach the class meriting management attention"/>
    <condition rel="has international classification candidate" subject="%S" object="Deficiency Meriting Neither"/>
  </relinst>
  <relinst type="has international classification" object="Classification Not Determinable" cf="100"
           name="[UK] F10e I27 G6 - the classification is not determinable where the two judgements have not been supplied (ISA UK 265 paras 6 b 10 b and A22)"
           alt="Neither significance judgement has been supplied for this deficiency, so its classification is not determinable">
    <condition rel="deficiency of control" subject="%S" object="%KC5"/>
    <condition rel="has framework" subject="%KC5" object="UK Material Controls" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%KT5" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has international classification candidate',*) is equal to 0" weight="1"
               alt="No classification candidate could be derived from the judgements supplied for this deficiency"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10d - the four triggers of a deficiency on the international path (ISA UK 265 paras 6 a i and 6 a ii)"
           alt="States the four triggers of a deficiency in internal control on the international path, including the missing control limb">
    <condition rel="has international classification" subject="%S" object="%KF1"/>
    <condition expression="'How a deficiency arises on this path. A deficiency in internal control exists where a control is DESIGNED, IMPLEMENTED or OPERATED in such a way that it cannot prevent, or detect and correct, misstatements in the financial statements on a timely basis, ISA UK 265 paragraph 6 a i, OR where a control necessary to do so is MISSING, paragraph 6 a ii. Four triggers, and two of them are easy to miss in a testing programme: an unimplemented control passes a sample of nothing, and a missing control appears in no control inventory at all. A significant deficiency is a deficiency, or a COMBINATION of deficiencies, that in the assessor s professional judgement merits the attention of those charged with governance, paragraph 6 b.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10e I27 - the boundary between the lower two classes is a judgement the standard leaves open (ISA UK 265 paras 10 b and A22)"
           alt="States that the boundary between a deficiency meriting management attention and one meriting neither is undefined in the standard and is supplied">
    <condition rel="has international classification" subject="%S" object="%KF2"/>
    <condition expression="'Where this classification is a judgement and not a derivation. The standard defines a significant deficiency, paragraph 6 b, and requires other deficiencies of sufficient importance to merit management s attention to be communicated to management, paragraph 10 b. It does NOT define the boundary between that class and a deficiency meriting neither: other deficiency is left undefined and the only test given is the likelihood and potential magnitude of misstatement, paragraph A22. No fetched source supplies a threshold, so this assessment ships none and takes both significance judgements as inputs. A classification of meriting neither therefore records a judgement someone made, and the output names who should own it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10f I26 - an indicator raises significance for consideration and does not establish it on this path (ISA UK 265 paras 8 A6 and A7)"
           alt="States that the indicator lists on this path are expressly illustrative and that the determination is the assessor's own">
    <condition rel="has international significance indicator" subject="%S" object="%KI2"/>
    <condition rel="deficiency of control" subject="%S" object="%KC6" weight="1"/>
    <condition rel="has framework" subject="%KC6" object="UK Material Controls" weight="1"/>
    <condition expression="'An international significance indicator applies to this deficiency: ' + %KI2" value="%G1" weight="1"/>
    <condition expression="%G1 + '. On this path an indicator RAISES significance for consideration and does not establish it. Paragraph A6 lists matters the assessor may consider in judging significance and paragraph A7 lists indicators of a significant deficiency; both are expressly illustrative - may consider, include for example - and paragraph 8 requires the assessor s own determination. This is the opposite default from the other framework in this model, and the divergence is deliberate rather than an inconsistency: there the sources are silent and the conservative reading of silence makes an indicator conclusive, here the sources speak and say the list is illustrative. The indicator is reported and must be weighed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10f - a previously communicated deficiency left unremediated may itself be significant (ISA UK 265 para A17)"
           alt="States the near exception to the illustrative posture, which is still permissive and still not conclusive">
    <condition rel="previously communicated and unremediated" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%KC7" weight="1"/>
    <condition rel="has framework" subject="%KC7" object="UK Material Controls" weight="1"/>
    <condition expression="'The closest the standard comes to a conclusive indicator, and it still stops short. A deficiency communicated in a previous period that management has not remediated, without a reasonable explanation, MAY IN ITSELF REPRESENT a significant deficiency, ISA UK 265 paragraph A17. The wording is permissive, so this assessment does not treat it as establishing the classification. It is reported prominently because it is the one indicator the standard singles out this way, and because an unremediated deficiency that was already communicated says something about the monitoring process and not only about the control.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10h - a material misstatement the control did not prevent or detect is a strong indicator (ISA UK 330 para A41 and ISA UK 265 para A7 fifth item)"
           alt="States that a material misstatement not prevented or detected by the control is a strong indicator of a significant deficiency">
    <condition rel="material misstatement not detected by control" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%KC8" weight="1"/>
    <condition rel="has framework" subject="%KC8" object="UK Material Controls" weight="1"/>
    <condition expression="'A material misstatement was identified that this control did not prevent or detect. That is a STRONG indicator of a significant deficiency, ISA UK 330 paragraph A41, and it appears in the indicator list at ISA UK 265 paragraph A7. It is taken here as an input and is not derived: whether a misstatement is material, and whether the control was the one that should have caught it, are both judgements about the facts rather than consequences of them. Strong is not the same as conclusive, so the classification still rests on the significance judgements supplied - but a deficiency with this indicator and a classification below significant is a combination that should be explained.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10g - significance does not depend on a misstatement having occurred (ISA UK 265 para A5)"
           alt="States that significance turns on the likelihood and potential magnitude of misstatement rather than on one having occurred">
    <condition rel="has international classification" subject="%S" object="%KF3"/>
    <condition expression="'Significance does not depend on a misstatement having occurred. It turns on the likelihood that a misstatement COULD occur and on its potential magnitude, and a significant deficiency may exist even though no misstatement was identified, ISA UK 265 paragraph A5. The same proposition holds on the other framework in this model, reached from a different text, which is one of the few places where the two paths say exactly the same thing for different reasons. The practical point: a clean year is not evidence that a weak control is insignificant.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10i - there is no nil report obligation on this path (ISA UK 265 paras 3 and 9)"
           alt="States that a communication duty arises only from an identified significant deficiency and that no nil report is asserted">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition expression="'No nil report is owed and none is asserted here. The written communication duty is triggered only by an IDENTIFIED significant deficiency, ISA UK 265 paragraph 9, and other communication is permitted but not required, paragraph 3. So this result does not state that nothing further exists, and it is not a certificate that the control is sound - it records that on the judgements supplied this deficiency merits neither the attention of those charged with governance nor management s attention. If that reads surprisingly, the judgements are where to look.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10c - the paragraph that joins this communication duty to the Code (ISA UK 265 para A12-1)"
           alt="States the single place in the sources where the audit communication standard and the Code are joined">
    <condition rel="has international classification" subject="%S" object="Significant Deficiency Reportable To Those Charged With Governance"/>
    <condition expression="'Why this classification matters beyond the audit. In the United Kingdom, prompt written communication of significant deficiencies to the directors of a listed entity CAN ASSIST THEM to comply with the provisions of the UK Corporate Governance Code on internal control and on reporting to shareholders, ISA UK 265 paragraph A12-1. That paragraph is the only place in the fetched primary sources where the communication standard and the Code are expressly joined, and it is what makes one shared method legitimate across both frameworks in this model rather than a convenience. The communication duty itself is not created by the Code and does not wait for the annual report.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification reason" cf="100"
           name="[UK] F10e G3 - reason for a significant deficiency classification (ISA UK 265 paras 6 b 9 and 11)"
           alt="Explains the significant deficiency classification and what it obliges">
    <condition rel="has international classification" subject="%S" object="Significant Deficiency Reportable To Those Charged With Governance"/>
    <condition expression="'Significant deficiency: a deficiency, or a combination of deficiencies, that in professional judgement merits the attention of those charged with governance, ISA UK 265 paragraph 6 b. It must be communicated IN WRITING to those charged with governance on a timely basis, paragraph 9, and the written communication must contain a description of the deficiency with an explanation of its POTENTIAL EFFECTS, plus sufficient information for the recipients to understand its context, paragraph 11. Potential effects, not actual ones: the communication is owed whether or not a misstatement occurred. This classification is about communication and is not itself a disclosure outcome - whether anything appears in the annual report is the declaration question and is answered separately.'" value="%O"/>
  </relinst>
  <relinst type="has international classification reason" cf="100"
           name="[UK] F10e I27 G3 - reason for a deficiency meriting management attention (ISA UK 265 paras 10 b and A22)"
           alt="Explains the middle classification and that its boundary is a supplied judgement">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Management Attention"/>
    <condition expression="'This deficiency is of sufficient importance to merit management s attention and does not, on the judgement supplied, merit the attention of those charged with governance. It is therefore communicated to MANAGEMENT at an appropriate level of responsibility, on a timely basis, ISA UK 265 paragraph 10 b, and no written communication to those charged with governance is required by that standard. Two cautions. The boundary below this class is undefined in the standard, paragraph A22, so the classification rests on a judgement rather than on a threshold. And an appropriate level means a level with the authority to act, which will not always be the control owner.'" value="%O"/>
  </relinst>
  <relinst type="has international classification reason" cf="100"
           name="[UK] F10e F10i G3 - reason for a deficiency meriting neither (ISA UK 265 paras 3 10 b and A22)"
           alt="Explains the base classification, that it is a judgement, and that it is not a certificate">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition expression="'On the judgements supplied this deficiency merits neither the attention of those charged with governance nor management s attention, so no communication requirement arises from the communication standard. This is a recorded judgement and not a derivation: the standard gives no threshold for the boundary and names only the likelihood and potential magnitude of misstatement as the test, paragraph A22. It is also not a clean result. The control did not do what it was designed to do, the deficiency remains on the record, and it can be drawn into a combination later. If this classification looks wrong for the facts, the two significance judgements are the inputs to revisit.'" value="%O"/>
  </relinst>
  <relinst type="has international classification reason" cf="100"
           name="[UK] F10e G6 G3 - reason the classification could not be determined (ISA UK 265 paras 6 b and 10 b)"
           alt="Explains that neither significance judgement was supplied and that nothing has been assumed">
    <condition rel="has international classification" subject="%S" object="Classification Not Determinable"/>
    <condition expression="'The classification of this deficiency could not be determined. The two judgements it rests on - whether the deficiency merits the attention of those charged with governance, ISA UK 265 paragraph 6 b, and whether it is of sufficient importance to merit management s attention, paragraph 10 b - have not both been supplied, and neither has been assumed in either direction. Assuming the lower class would suppress a communication the standard may require; assuming the higher would manufacture one it does not. The open questions listed with this result name what is needed, and an unclassified deficiency is itself a state of affairs worth reporting rather than a neutral one.'" value="%O"/>
  </relinst>
  <relinst type="has judgement input" object="The Board" cf="100"
           name="[UK] F10e I27 G5 - the two significance judgements are owned by the board on this path (ISA UK 265 paras 6 b and A22)"
           alt="Names the significance judgements as inputs and the body that should own them">
    <condition rel="has international classification" subject="%S" object="%KJ1"/>
    <condition rel="deficiency of control" subject="%S" object="%KC9" weight="1"/>
    <condition rel="has framework" subject="%KC9" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has control judgement input" object="The Board" cf="100"
           name="[UK] F9a G5 - whether a declaration can be given at all is a board judgement (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="Names the decision whether to give a declaration or explain the position as a board judgement">
    <condition rel="has uk declaration determination" subject="%S" object="Effectiveness Not Determinable"/>
  </relinst>
  <relinst type="has control judgement input" object="The Board" cf="100"
           name="[UK] F9b G5 - the level of detail disclosed is a board judgement (FRC Corporate Governance Code Guidance 2024 para 299)"
           alt="Names the level of disclosed detail as a board judgement where confidentiality is in issue">
    <condition rel="must be described in the declaration" subject="%S" object="true"/>
    <condition rel="has deficiency" subject="%S" object="%UD6" weight="1"/>
    <condition rel="disclosure would reveal confidential information" subject="%UD6" object="true" weight="1"/>
  </relinst>
  <relinst type="has open question" cf="100"
           name="[UK] F1 F9a G6 - the design and operating determinations the declaration needs are not both present (FRC Corporate Governance Code Guidance 2024 para 297)"
           alt="This material control reached no declaration candidate, so the determinations the declaration rests on are still needed">
    <condition rel="has framework" subject="%S" object="UK Material Controls"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has uk declaration candidate',*) is equal to 0" weight="1"
               alt="No declaration candidate could be derived from the facts supplied for this control"/>
    <condition expression="'The declaration for a material control rests on three things, and they are needed in this order: whether the control is effectively DESIGNED, whether it OPERATED effectively on the testing, and whether any deficiency still STANDS at the balance sheet date. Effectiveness for the declaration covers design and implementation as well as operation, FRC guidance paragraph 297, so a clean test result alone will not reach it. The open questions on the design and operating decision points above name the individual facts each needs.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[UK] F10e I27 G6 - the two significance judgements have not been supplied (ISA UK 265 paras 6 b and 10 b)"
           alt="Neither significance judgement has been supplied for this deficiency on the UK path">
    <condition rel="deficiency of control" subject="%S" object="%KQ1"/>
    <condition rel="has framework" subject="%KQ1" object="UK Material Controls" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'merits attention of those charged with governance',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether the deficiency merits the attention of those charged with governance"/>
    <condition expression="'Whether this deficiency merits the attention of those charged with governance, ISA UK 265 paragraph 6 b, and whether it is of sufficient importance to merit management s attention, paragraph 10 b. Two separate yes or no judgements, and the standard supplies no threshold for either: the only test it gives is the likelihood that a misstatement could occur and its potential magnitude, paragraph A22. Both are needed because they select between three different communication outcomes, and no default is shipped for either - a shipped default here would be this pack inventing the boundary the standard declines to draw.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[UK] F10e I27 G6 - the management attention judgement alone is missing (ISA UK 265 para 10 b)"
           alt="The governance judgement is answered in the negative but the management attention judgement has not been supplied">
    <condition rel="merits attention of those charged with governance" subject="%S" object="false"/>
    <condition rel="deficiency of control" subject="%S" object="%KQ2" weight="1"/>
    <condition rel="has framework" subject="%KQ2" object="UK Material Controls" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'merits management attention',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether the deficiency merits management attention"/>
    <condition expression="'Whether this deficiency is of sufficient importance to merit management s attention, ISA UK 265 paragraph 10 b. It has been judged not to merit the attention of those charged with governance, which settles the written communication to that body but not the communication to management. The two remaining classes carry different consequences - communication to management at an appropriate level of responsibility, or no communication requirement at all - so the classification is left open rather than resolved downwards by silence.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[UK] F7 G6 - whether the deficiency was reported in a previous declaration (Code 2024 Provision 29 third bullet, FRC Guidance para 297)"
           alt="No answer has been recorded on whether this deficiency was reported in a previous declaration">
    <condition rel="deficiency of control" subject="%S" object="%KQ3"/>
    <condition rel="has framework" subject="%KQ3" object="UK Material Controls" weight="1"/>
    <condition rel="has deficiency type" subject="%S" object="%KQT3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'reported in prior year declaration',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether this deficiency was reported in a previous declaration"/>
    <condition expression="'Whether this deficiency was reported in a previous declaration. It matters independently of this year s conclusion: the third disclosure element is a summary of how the board has addressed PREVIOUSLY REPORTED issues, Provision 29 third bullet and FRC guidance paragraph 297 fourth limb, so it is triggered by what was reported before and not by whether the control is ineffective now. A control that is clean this year can still owe this element. Note also that neither text defines how many prior years are in scope, or whether previously reported means reported under this provision or anywhere in the annual report, so the lookback is a board judgement this assessment consumes rather than sets.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity summary" cf="100"
           name="[US] G7 E4 - plain language summary of the most severe US finding (AS 2201 paras A7 and 78, Regulation S-K Item 308 a 3)"
           alt="Gives a control owner the most severe US outcome in plain words and says what follows from it">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition expression="'In plain terms: this is the most serious finding available. There is a reasonable possibility that the control, as it stands, could let a material misstatement through - whether or not one has actually happened. It is disclosed publicly in the annual internal control report, and it means internal control over financial reporting cannot be reported as effective at the period end date. Remediation and a retest are needed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity summary" cf="100"
           name="[US] G7 E3 - plain language summary of the middle US finding (AS 2201 paras A11 and 80, SEC Release 33-8810 II B 3)"
           alt="Gives a control owner the middle US outcome in plain words and says where it goes">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
    <condition expression="'In plain terms: less serious than the most severe class, but important enough that the people overseeing financial reporting need to know. It goes in writing to the audit committee, promptly. It is not disclosed publicly and it does not by itself stop internal control being reported as effective. It still needs fixing, and the fix needs testing before anyone can say the control works.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity summary" cf="100"
           name="[US] G7 E2 D13c - plain language summary of the lowest US finding (AS 2201 paras A3 and 81)"
           alt="Gives a control owner the lowest US outcome in plain words and warns against reading it as clean">
    <condition rel="has us severity determination" subject="%S" object="Deficiency"/>
    <condition expression="'In plain terms: a shortfall worth recording and fixing, which does not reach either reporting threshold. It is still put in writing to management, and the audit committee is told that the communication was made. Nothing is disclosed publicly. The absence of a higher finding is not a clean bill of health: the control did not do what it was designed to do, and this can be drawn into a combination later.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity summary" cf="100"
           name="[US] G7 G6 - plain language summary where no US severity was reached (AS 2201 paras 63 and 64)"
           alt="Tells a control owner that no severity was reached and that nothing has been assumed either way">
    <condition rel="deficiency of control" subject="%S" object="%SC1"/>
    <condition rel="has framework" subject="%SC1" object="US ICFR" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has us severity determination',*) is equal to 0" weight="1"
               alt="No severity has been determined for this deficiency on the facts supplied"/>
    <condition expression="'In plain terms: no severity has been reached. Two judgements decide it, and at least one of them is missing: how much could go wrong, and how likely that is. Neither is guessed here, because guessing would mean answering the very question you asked. The open questions listed with this result name exactly what is needed. An unevaluated deficiency is not a minor one - it is an unanswered one.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has prior communication position" object="true" cf="100"
           name="[US] D14 - a stated prior written communication is taken as supplied (AS 2201 para 81)"
           alt="This finding is recorded as already covered by a written communication, so that is taken as supplied">
    <condition rel="already communicated in writing" subject="%S" object="true"/>
  </relinst>
  <relinst type="has prior communication position" object="false" cf="100"
           name="[US] D14 J4 - absent a stated prior written communication the duty is treated as still owed (AS 2201 paras 78 and 81)"
           alt="No prior written communication is recorded against this finding, so the communication duty is treated as still owed">
    <condition rel="deficiency of control" subject="%S" object="%PCC" weight="1"/>
    <condition rel="has framework" subject="%PCC" object="US ICFR" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'already communicated in writing',*) is equal to 0" weight="1"
               alt="Whether this finding was already communicated in writing is not recorded"/>
  </relinst>
  <relinst type="has oversight position" object="true" cf="100"
           name="[US] D14 - a stated judgement that audit committee oversight is ineffective is taken as supplied (AS 2201 para 79)"
           alt="Oversight of financial reporting and internal control by the audit committee is recorded as ineffective, so that is taken as supplied">
    <condition rel="audit committee oversight ineffective" subject="%S" object="true"/>
  </relinst>
  <relinst type="has oversight position" object="false" cf="100"
           name="[US] D14 - a stated judgement that audit committee oversight is not ineffective is taken as supplied (AS 2201 para 79)"
           alt="Oversight of financial reporting and internal control by the audit committee is recorded as not ineffective, so that is taken as supplied">
    <condition rel="audit committee oversight ineffective" subject="%S" object="false"/>
  </relinst>
  <relinst type="has oversight position" object="false" cf="100"
           name="[US] D14 J4 - absent a judgement on audit committee oversight it is not treated as ineffective (AS 2201 paras 69 78 and 79)"
           alt="No judgement on the effectiveness of audit committee oversight is recorded, so it is not treated as ineffective and the finding keeps the wider addressee list">
    <condition rel="deficiency of control" subject="%S" object="%OVC" weight="1"/>
    <condition rel="has framework" subject="%OVC" object="US ICFR" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'audit committee oversight ineffective',*) is equal to 0" weight="1"
               alt="Whether audit committee oversight is ineffective is not recorded"/>
  </relinst>
  <relinst type="has communication requirement" object="In writing to management and the audit committee before the report is issued" cf="100"
           name="[US] E10 - the most severe finding is communicated in writing to management and the audit committee before the report is issued (AS 2201 para 78)"
           alt="The most severe finding is communicated in writing to both management and the audit committee before the internal control report is issued">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="has oversight position" subject="%S" object="false" weight="1"/>
    <condition rel="has prior communication position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="In writing to the audit committee on a timely basis" cf="100"
           name="[US] E10 - the middle finding is communicated in writing to the audit committee on a timely basis (AS 2201 para 80)"
           alt="The middle finding is communicated in writing to the audit committee on a timely basis">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
    <condition rel="has oversight position" subject="%S" object="false" weight="1"/>
    <condition rel="has prior communication position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="In writing to management with the audit committee informed that it was made" cf="100"
           name="[US] D13c - the lowest finding is communicated in writing to management with the audit committee informed (AS 2201 para 81)"
           alt="The lowest finding is communicated in writing to management, and the audit committee is informed that the communication was made">
    <condition rel="has us severity determination" subject="%S" object="Deficiency"/>
    <condition rel="has prior communication position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="To the board because audit committee oversight is ineffective" cf="100"
           name="[US] E10 - the most severe finding goes to the board where audit committee oversight is itself ineffective (AS 2201 para 79)"
           alt="Audit committee oversight has been judged ineffective, so the most severe finding is communicated to the board">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="has oversight position" subject="%S" object="true" weight="1"/>
    <condition rel="has prior communication position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="To the board because audit committee oversight is ineffective" cf="100"
           name="[US] E10 - the middle finding goes to the board where audit committee oversight is itself ineffective (AS 2201 paras 79 and 80)"
           alt="Audit committee oversight has been judged ineffective, so the middle finding is communicated to the board">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
    <condition rel="has oversight position" subject="%S" object="true" weight="1"/>
    <condition rel="has prior communication position" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="No further communication required because it was already communicated in writing" cf="100"
           name="[US] D13c - the relief where the finding is already covered by a written communication (AS 2201 para 81)"
           alt="This finding is already covered by a written communication, so it need not be communicated again">
    <condition rel="has prior communication position" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%CC1" weight="1"/>
    <condition rel="has framework" subject="%CC1" object="US ICFR" weight="1"/>
    <condition rel="has us severity determination" subject="%S" object="%CS1" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[US] E10 D13 D13b - recipient of the most severe finding (AS 2201 para 78)"
           alt="Names the recipients of the communication of the most severe finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to management and the audit committee before the report is issued"/>
    <condition expression="'Recipient: management AND the audit committee - both, not either. The standard names the audit committee as those responsible for oversight of the company s external financial reporting and internal control over financial reporting, and where no such committee exists that oversight role falls to the board or its equivalent, AS 2201 paragraph 78 and footnote 16.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[US] E10 D13 - deadline for the most severe finding (AS 2201 para 78)"
           alt="States the deadline for communicating the most severe finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to management and the audit committee before the report is issued"/>
    <condition expression="'Deadline: before the internal control report is issued. The clock is the report and not the period end date, so this communication cannot be deferred to the following cycle.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[US] E10 D13 - form of the communication of the most severe finding (AS 2201 para 78)"
           alt="States that the communication of the most severe finding must be in writing">
    <condition rel="has communication requirement" subject="%S" object="In writing to management and the audit committee before the report is issued"/>
    <condition expression="'Form: in writing. An oral briefing does not discharge this, however senior the audience.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[US] E10 D13 A12 - the paragraph the most severe communication rests on (AS 2201 para 78)"
           alt="Names the instrument and paragraph the most severe communication duty rests on">
    <condition rel="has communication requirement" subject="%S" object="In writing to management and the audit committee before the report is issued"/>
    <condition expression="'Basis: PCAOB AS 2201 paragraph 78. The duty is triggered by the identification of a finding in the most severe class and does not depend on a misstatement having occurred.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[US] E10 D13 - recipient of the middle finding (AS 2201 para 80)"
           alt="Names the recipient of the communication of the middle finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to the audit committee on a timely basis"/>
    <condition expression="'Recipient: the audit committee. Management is not a required recipient of this one under the paragraph relied on, which is a narrower addressee list than the most severe class carries, AS 2201 paragraph 80.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[US] E10 D13 - deadline for the middle finding (AS 2201 para 80)"
           alt="States the deadline for communicating the middle finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to the audit committee on a timely basis"/>
    <condition expression="'Deadline: timely. The paragraph fixes no date and no filing event, so timeliness is a judgement against the facts - and a finding held until the next scheduled committee meeting may well fail it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[US] E10 D13 - form of the communication of the middle finding (AS 2201 para 80)"
           alt="States that the communication of the middle finding must be in writing">
    <condition rel="has communication requirement" subject="%S" object="In writing to the audit committee on a timely basis"/>
    <condition expression="'Form: in writing.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[US] E10 D13 A12 - the paragraph the middle communication rests on (AS 2201 para 80)"
           alt="Names the instrument and paragraph the middle communication duty rests on">
    <condition rel="has communication requirement" subject="%S" object="In writing to the audit committee on a timely basis"/>
    <condition expression="'Basis: PCAOB AS 2201 paragraph 80. This communication is private. It is not a public disclosure and it does not become one by being made.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[US] D13c D13 - recipient of the lowest finding (AS 2201 para 81)"
           alt="Names the recipients of the communication of the lowest finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to management with the audit committee informed that it was made"/>
    <condition expression="'Recipient: management, in writing - and the audit committee is INFORMED THAT THE COMMUNICATION WAS MADE. Two different acts with two different addressees: the committee receives notice that the communication happened rather than the communication itself, AS 2201 paragraph 81.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[US] D13c D13 - deadline for the lowest finding (AS 2201 para 81)"
           alt="States the deadline for communicating the lowest finding">
    <condition rel="has communication requirement" subject="%S" object="In writing to management with the audit committee informed that it was made"/>
    <condition expression="'Deadline: the paragraph relied on fixes none for this class. That is not a licence to wait: the finding is on the record from the moment it is identified, and an undated obligation is still an obligation.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[US] D13c D13 - form of the communication of the lowest finding (AS 2201 para 81)"
           alt="States that the communication of the lowest finding must be in writing">
    <condition rel="has communication requirement" subject="%S" object="In writing to management with the audit committee informed that it was made"/>
    <condition expression="'Form: in writing to management. The notice to the audit committee that it was made is not itself required to be in writing by the paragraph relied on.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[US] D13c D13 A12 - the paragraph the lowest communication rests on, and the correction it records (AS 2201 para 81)"
           alt="Names the paragraph the lowest communication duty rests on and records the earlier misreading it corrects">
    <condition rel="has communication requirement" subject="%S" object="In writing to management with the audit committee informed that it was made"/>
    <condition expression="'Basis: PCAOB AS 2201 paragraph 81 - ALL deficiencies of a lesser magnitude than the most severe class. This is the most commonly mishandled duty on this path, because a programme that reports only the two upper classes will show no communication here at all. An earlier reading used in building this method had this class carrying no communication duty; the fetched text says the opposite, and the correction is recorded rather than quietly applied.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[US] E10 D13 - recipient where audit committee oversight is ineffective (AS 2201 para 79)"
           alt="Names the recipient where audit committee oversight has been judged ineffective">
    <condition rel="has communication requirement" subject="%S" object="To the board because audit committee oversight is ineffective"/>
    <condition expression="'Recipient: the board of directors. The ineffectiveness of the audit committee s own oversight of external financial reporting and internal control is itself a matter to be communicated, in writing, to the board, AS 2201 paragraph 79. The finding is not reduced by the change of addressee, and the committee s ineffectiveness is separately an indicator of the most severe class.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[US] E10 D13 - deadline where audit committee oversight is ineffective (AS 2201 para 79)"
           alt="States the deadline where the communication is redirected to the board">
    <condition rel="has communication requirement" subject="%S" object="To the board because audit committee oversight is ineffective"/>
    <condition expression="'Deadline: as for the underlying class. Redirecting the communication to the board does not extend the time allowed for making it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[US] E10 D13 - form where audit committee oversight is ineffective (AS 2201 para 79)"
           alt="States that the communication redirected to the board must be in writing">
    <condition rel="has communication requirement" subject="%S" object="To the board because audit committee oversight is ineffective"/>
    <condition expression="'Form: in writing.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[US] E10 D13 A12 - the paragraph the redirected communication rests on (AS 2201 para 79)"
           alt="Names the paragraph the redirected communication duty rests on">
    <condition rel="has communication requirement" subject="%S" object="To the board because audit committee oversight is ineffective"/>
    <condition expression="'Basis: PCAOB AS 2201 paragraph 79. Note what this input is and is not: whether the committee s oversight is ineffective is a judgement supplied to this assessment, not one derived by it, and the paragraph does not say who should make it. An institution that lets the committee answer the question about itself has not really answered it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[US] D13c D13 A12 - the relief is relief from repeating and not from owing (AS 2201 para 81)"
           alt="States that the already-communicated relief removes the repetition and not the duty">
    <condition rel="has communication requirement" subject="%S" object="No further communication required because it was already communicated in writing"/>
    <condition expression="'Basis: PCAOB AS 2201 paragraph 81 - a deficiency already covered by a written communication from the auditor, internal audit or others within the organisation need not be communicated again. Read this precisely. The duty was owed and was discharged; the relief is from REPEATING the communication, not from owing one. Two things follow: the earlier written communication is part of the record for this finding, and relief claimed against a communication that cannot be produced is not relief at all.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[US] G7 E10 - plain language summary of the most severe communication (AS 2201 para 78)"
           alt="Gives a control owner the most severe communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="In writing to management and the audit committee before the report is issued"/>
    <condition expression="'In plain terms: write it up, and get it to management and the audit committee before the internal control report goes out. Both audiences, in writing, and the deadline is the report rather than the year end.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[US] G7 E10 - plain language summary of the middle communication (AS 2201 para 80)"
           alt="Gives a control owner the middle communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="In writing to the audit committee on a timely basis"/>
    <condition expression="'In plain terms: write it up and get it to the audit committee promptly. There is no public disclosure and no fixed filing date, but timely means timely, and the next scheduled meeting may be too late.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[US] G7 D13c - plain language summary of the lowest communication (AS 2201 para 81)"
           alt="Gives a control owner the lowest communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="In writing to management with the audit committee informed that it was made"/>
    <condition expression="'In plain terms: write it to management, and tell the audit committee that you did. A lower severity does not mean no paperwork. This is the step most often missed, because people assume the smaller findings go unreported.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[US] G7 E10 - plain language summary where the communication is redirected to the board (AS 2201 para 79)"
           alt="Gives a control owner the redirected communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="To the board because audit committee oversight is ineffective"/>
    <condition expression="'In plain terms: the usual route runs through the audit committee, and here that committee s own oversight has been judged ineffective. So this goes to the board instead, in writing, on the same timetable. Nothing about the finding is softened by the detour.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[US] G7 D13c - plain language summary of the already communicated relief (AS 2201 para 81)"
           alt="Gives a control owner the already-communicated relief in plain words">
    <condition rel="has communication requirement" subject="%S" object="No further communication required because it was already communicated in writing"/>
    <condition expression="'In plain terms: this was already covered by a written communication, so nothing needs saying twice. That is relief from repeating it, not a finding that nothing was owed - and it only holds if the earlier written communication can actually be produced.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] D13d D13a - the communication output asserts nothing about what was not found (AS 2201 paras 82 and 83 and AS 1305 para 08)"
           alt="States that no negative assurance about the absence of further deficiencies is expressed">
    <condition rel="has us severity determination" subject="%S" object="%DF1"/>
    <condition expression="'What this output does not say, stated so nobody reads it in. The procedures behind an assessment of this kind are not required to identify every deficiency - only those the assessor is AWARE OF, AS 2201 paragraph 82 - and no report may state that no deficiencies were noted, paragraph 83 and AS 1305 paragraph 08. So this result reports what was found and what is owed, and asserts nothing whatever about what was not found. A clean line here is the absence of a finding and not the presence of assurance.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Public disclosure in the annual internal control report" cf="100"
           name="[US] E13 - the most severe finding is publicly disclosed in the annual internal control report (Regulation S-K Item 308 a 3 and SEC Release 33-8810 II B 3)"
           alt="The most severe finding is disclosed publicly in the annual internal control report">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="No public disclosure of this severity is required" cf="100"
           name="[US] E13 - the middle finding is communicated privately and is not publicly disclosed (Regulation S-K Item 308 a 3 and SEC Release 33-8810 II B 3 and footnote 52)"
           alt="The middle finding is communicated privately and carries no public disclosure requirement">
    <condition rel="has us severity determination" subject="%S" object="Significant Deficiency"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="No public disclosure of this severity is required" cf="100"
           name="[US] E13 - the lowest finding carries neither public disclosure nor an audit committee channel of its own (Regulation S-K Item 308 a 3 and AS 2201 para 81)"
           alt="The lowest finding carries no public disclosure requirement">
    <condition rel="has us severity determination" subject="%S" object="Deficiency"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E13 - the two disclosure channels are distinct and neither discharges the other (SEC 33-8810 II B 3 fn 52, SOX 302 a 5, Item 601 b 31 i)"
           alt="Explains that private communication and public disclosure are two separate channels">
    <condition rel="has us severity determination" subject="%S" object="%DF2"/>
    <condition expression="'Two channels, and they are not substitutes. PRIVATE: the certifying officers disclose to the auditor and the audit committee all findings in the most severe class and all findings in the middle class, section 302 a 5 and Item 601 b 31 i paragraph 5. PUBLIC: only the most severe class is disclosed in the annual internal control report, Item 308 a 3 and Release 33-8810 II B 3 with footnote 52. So a middle-class finding is reported privately and never publicly, and for the most severe class BOTH channels run - the public disclosure does not discharge the private communication and the private communication does not substitute for the disclosure.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Nature of the weakness" cf="100"
           name="[US] E14 - the disclosure conveys the nature of the finding (SEC Release 33-8810 II B 3)"
           alt="The public disclosure must convey the nature of the finding">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Impact on financial reporting and on internal control" cf="100"
           name="[US] E14 - the disclosure conveys the impact on financial reporting and on internal control (SEC Release 33-8810 II B 3)"
           alt="The public disclosure must convey the impact on financial reporting and on internal control over financial reporting">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Remediation planned or undertaken" cf="100"
           name="[US] E14 - the disclosure conveys the remediation planned or undertaken (SEC Release 33-8810 II B 3)"
           alt="The public disclosure must convey the remediation planned or already undertaken">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
  </relinst>
  <relinst type="has us disclosure requirement" object="Whether the weakness is pervasive or not pervasive" cf="100"
           name="[US] E14 - the disclosure distinguishes a pervasive finding from one that is not (SEC Release 33-8810 II B 3)"
           alt="The public disclosure must distinguish a pervasive finding from one that is not pervasive">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E14 - pervasiveness is undefined in the primary sources and is taken as an input (SEC Release 33-8810 II B 3)"
           alt="States that pervasiveness is an input because no primary source checked defines it">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition expression="'A word the sources use and do not define. The disclosure should distinguish a finding that is PERVASIVE to the whole of internal control from one that is not, Release 33-8810 II B 3, and no primary source fetched for this method defines pervasive, gives a test for it, or says who decides. It is therefore taken as an input here and never derived. A rough working distinction, offered as practice and not as a rule: a finding confined to one process or one account is ordinarily not pervasive, while one in the control environment, in general IT controls, or in the competence of the people who run many controls ordinarily is.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E14 - the pervasiveness judgement supplied for this finding (SEC Release 33-8810 II B 3)"
           alt="Reports that this finding has been judged pervasive to internal control as a whole">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="is pervasive" subject="%S" object="true" weight="1"/>
    <condition expression="'This finding has been supplied as PERVASIVE to internal control as a whole, and the disclosure should say so. Two practical consequences: a pervasive finding is rarely cured by fixing one control, and a remediation plan addressed to a single process will not usually support a later conclusion that the finding has been resolved.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has us severity finding" cf="100"
           name="[US] E14 - the finding has been supplied as not pervasive (SEC Release 33-8810 II B 3)"
           alt="Reports that this finding has been judged not pervasive to internal control as a whole">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition rel="is pervasive" subject="%S" object="false" weight="1"/>
    <condition expression="'This finding has been supplied as NOT pervasive to internal control as a whole, and the disclosure should distinguish it from one that is. Not pervasive does not mean not severe: the severity is settled by magnitude and likelihood, and this judgement affects only how the disclosure describes the reach of the problem.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[US] E14 G6 - the pervasiveness judgement has not been supplied for a finding that will be disclosed (SEC Release 33-8810 II B 3)"
           alt="No pervasiveness judgement has been supplied for a finding that will be publicly disclosed">
    <condition rel="has us severity determination" subject="%S" object="Material Weakness"/>
    <condition expression="countRelationshipInstances(%S,'is pervasive',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether this finding is pervasive to internal control as a whole"/>
    <condition expression="'Whether this finding is pervasive to internal control as a whole. The public disclosure should distinguish a pervasive finding from one that is not, Release 33-8810 II B 3, so the disclosure cannot be drafted without an answer. No default is shipped because no primary source fetched for this method defines the term, and a default would be this pack inventing a definition the Commission did not give. The judgement belongs to management, and the reasoning for it should be recorded alongside the answer.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="assessment has material weakness deficiency" cf="100"
           name="[US] E11 - projects a finding in the most severe class standing at the period end date onto the assessment (Regulation S-K Item 308 a 3 and 12 CFR 363.2 b 3 iii)"
           alt="Carries a finding in the most severe class that still stands at the period end date onto the assessment, so the conclusion can be reached without counting across three hops">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment covers control" subject="%S" object="%AC1" weight="1"/>
    <condition rel="has deficiency" subject="%AC1" object="%O" weight="1"/>
    <condition rel="has us severity determination" subject="%O" object="Material Weakness" weight="1"/>
    <condition rel="persists at period end" subject="%O" object="true" weight="1"/>
  </relinst>
  <relinst type="assessment has unevaluated deficiency" cf="100"
           name="[US] E11 G6 - projects a deficiency that reached no severity onto the assessment (AS 2201 paras 63 and 64)"
           alt="Carries a deficiency that reached no severity determination onto the assessment, so an unevaluated deficiency cannot be read as a clean one">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment covers control" subject="%S" object="%AC2" weight="1"/>
    <condition rel="has deficiency" subject="%AC2" object="%O" weight="1"/>
    <condition rel="has deficiency type" subject="%O" object="%ADT2" weight="1"/>
    <condition expression="countRelationshipInstances(%O,'has us severity determination',*) is equal to 0" weight="1"
               alt="This deficiency reached no severity determination on the facts supplied"/>
  </relinst>
  <relinst type="has icfr conclusion" object="ICFR Not Effective" cf="100"
           name="[US] E11 - a finding in the most severe class standing at the period end date precludes an effective conclusion (Regulation S-K Item 308 a 3 and 12 CFR 363.2 b 3 iii)"
           alt="A finding in the most severe class stood at the period end date, so internal control over financial reporting cannot be concluded effective">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment evaluation driver" subject="%S" object="%DRV1" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'assessment has material weakness deficiency',*) is greater than or equal to 1" weight="1"
               alt="At least one finding in the most severe class stood at the period end date"/>
  </relinst>
  <relinst type="has icfr conclusion" object="ICFR Not Effective" cf="100"
           name="[US] E11 - an entity level finding in the most severe class supplied directly precludes an effective conclusion (Regulation S-K Item 308 a 3 and 12 CFR 363.2 b 3 iii)"
           alt="A finding in the most severe class at the period end date has been supplied at the assessment level, so an effective conclusion is precluded">
    <condition rel="assessment severe finding position" subject="%S" object="true"/>
    <condition rel="assessment has framework" subject="%S" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="assessment severe finding position" object="true" cf="100"
           name="[US] E11a - a stated entity level finding in the most severe class is taken as supplied (Regulation S-K Item 308 a 3)"
           alt="An entity level finding in the most severe class has been stated for this assessment, so that is taken as supplied">
    <condition rel="assessment has material weakness at period end" subject="%S" object="true"/>
  </relinst>
  <relinst type="assessment severe finding position" object="false" cf="100"
           name="[US] E11a - a stated absence of an entity level finding is taken as supplied (Regulation S-K Item 308 a 3)"
           alt="The absence of an entity level finding in the most severe class has been stated for this assessment, so that is taken as supplied">
    <condition rel="assessment has material weakness at period end" subject="%S" object="false"/>
  </relinst>
  <relinst type="assessment severe finding position" object="false" cf="100"
           name="[US] E11a - absent a stated entity level finding none is asserted above the control level (Regulation S-K Item 308 a 3)"
           alt="No entity level finding has been stated for this assessment, so none is treated as asserted above the control level and the conclusion rests on the controls themselves">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment has period end" subject="%S" object="%EPD1" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'assessment has material weakness at period end',*) is equal to 0" weight="1"
               alt="No entity level finding in the most severe class has been stated for this assessment"/>
  </relinst>
  <relinst type="assessment evaluation driver" object="true" cf="100"
           name="[US] E11a - drives the severity evaluation of each deficiency on each covered control before the conclusion is read (AS 2201 paras 63 and 64)"
           alt="Reaches the severity determination of a deficiency on a control this assessment covers, so the entity level conclusion is read from an evaluated record and not an empty one">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment covers control" subject="%S" object="%DRC" weight="1"/>
    <condition rel="has deficiency" subject="%DRC" object="%DRD" weight="1"/>
    <condition rel="has us severity determination" subject="%DRD" object="%DRS" weight="1"/>
  </relinst>
  <relinst type="assessment evaluation driver" object="false" cf="100"
           name="[US] E11a - records that a covered control carries no deficiency to evaluate (AS 2201 para 63)"
           alt="A control this assessment covers carries no deficiency, so there is nothing to evaluate for it">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment covers control" subject="%S" object="%NDC" weight="1"/>
    <condition expression="countRelationshipInstances(%NDC,'has deficiency',*) is equal to 0" weight="1"
               alt="This control carries no deficiency on the facts supplied"/>
  </relinst>
  <relinst type="has icfr conclusion" object="ICFR Effective" cf="100"
           name="[US] E11 - effective conclusion where nothing in the most severe class stood at period end and every deficiency is evaluated (Item 308 a 3, 12 CFR 363.2 b 3 iii)"
           alt="Nothing in the most severe class stood at the period end date and every deficiency on record has been evaluated, so an effective conclusion is available">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition rel="assessment severe finding position" subject="%S" object="false" weight="1"/>
    <condition rel="assessment has period end" subject="%S" object="%APE3" weight="1"/>
    <condition rel="assessment evaluation driver" subject="%S" object="%DRV3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'assessment covers control',*) is greater than or equal to 1" weight="1"
               alt="At least one control is covered by this assessment"/>
    <condition expression="countRelationshipInstances(%S,'assessment has material weakness deficiency',*) is equal to 0" weight="1"
               alt="No finding in the most severe class stood at the period end date"/>
    <condition expression="countRelationshipInstances(%S,'assessment has unevaluated deficiency',*) is equal to 0" weight="1"
               alt="Every deficiency on record for this assessment has reached a severity determination"/>
  </relinst>
  <relinst type="has icfr disclosure requirement" object="Conclusion that internal control over financial reporting is not effective" cf="100"
           name="[US] E11 - the adverse conclusion is itself a disclosure (Regulation S-K Item 308 a 3 and 12 CFR 363.2 b 3 iii)"
           alt="The conclusion that internal control over financial reporting is not effective is itself a required disclosure">
    <condition rel="has icfr conclusion" subject="%S" object="ICFR Not Effective"/>
  </relinst>
  <relinst type="has icfr disclosure requirement" object="Public disclosure in the annual internal control report" cf="100"
           name="[US] E11 E13 - the adverse conclusion and the findings behind it appear in the annual internal control report (Regulation S-K Item 308 a 3 and SEC Release 33-8810 II B 3)"
           alt="The adverse conclusion and the findings behind it are disclosed in the annual internal control report">
    <condition rel="has icfr conclusion" subject="%S" object="ICFR Not Effective"/>
  </relinst>
  <relinst type="has icfr finding" cf="100"
           name="[US] E11 - the preclusion is in both instruments, serving a listed issuer and an insured depository institution alike (17 CFR 229.308 a 3, 12 CFR 363.2 b 3 iii)"
           alt="States that the preclusion appears in identical terms in the listed issuer rule and the insured depository institution rule">
    <condition rel="has icfr conclusion" subject="%S" object="%IF1"/>
    <condition expression="'Why one rule here carries two citations. Management s annual report must disclose any finding in the most severe class and may not conclude that internal control over financial reporting is effective if one exists - explicit in the text of Regulation S-K Item 308 a 3, 17 CFR 229.308 a 3 - and in identical terms, for an insured depository institution, at 12 CFR 363.2 b 3 iii. The preclusion is therefore not a listing consequence: an unlisted bank inside the Part 363 asset threshold reaches the same answer by its own rule. That is what lets this path serve both populations without a second overlay.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr finding" cf="100"
           name="[US] E12 - no qualified or except for conclusion on internal control is available (SEC Release 33-8810 II B 2)"
           alt="States that management may not conclude internal control is effective except for an identified finding">
    <condition rel="has icfr conclusion" subject="%S" object="%IF2"/>
    <condition expression="'There is no middle answer here, and this is where assessments most often try to invent one. Management may NOT conclude that internal control over financial reporting is effective EXCEPT FOR an identified finding in the most severe class, Release 33-8810 II B 2. What is permitted is the opposite shape: a statement that internal control is NOT effective, with the specific reasons. So the conclusion is binary - effective, or not effective with reasons - and a qualified, scoped or except-for formulation is not available however narrow the finding looks.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr finding" cf="100"
           name="[US] E11 G6 - a deficiency on this assessment has not been evaluated, so no conclusion is reached (AS 2201 paras 63 and 64)"
           alt="States that an unevaluated deficiency blocks a conclusion rather than being treated as clean">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition expression="countRelationshipInstances(%S,'assessment has unevaluated deficiency',*) is greater than or equal to 1" weight="1"
               alt="At least one deficiency on this assessment has reached no severity determination"/>
    <condition expression="'At least one deficiency covered by this assessment has reached no severity at all, so a favourable conclusion is not available and none has been reached by default. The severity of each deficiency must be evaluated, AS 2201 paragraph 63, and the evaluation turns on magnitude and likelihood, paragraph 64 - neither of which is assumed here. Treating an unevaluated deficiency as if it were below the reporting threshold would be exactly the error this gate exists to prevent, because the only thing known about it is that nobody has judged it yet.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr open question" cf="100"
           name="[US] E11 G6 - the facts the entity level conclusion needs have not been supplied (Regulation S-K Item 308 a 3 and 12 CFR 363.2 b 3 iii)"
           alt="No entity level conclusion was reached, so the facts it rests on are still needed">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
    <condition expression="countRelationshipInstances(%S,'has icfr conclusion',*) is equal to 0" weight="1"
               alt="No entity level conclusion has been reached on the facts supplied"/>
    <condition expression="'The entity level conclusion rests on four things: the period end DATE, the CONTROLS the assessment covers, a severity determination for EVERY deficiency recorded against them, and whether each of those findings still STOOD at the period end date. At least one is missing. No conclusion has been assumed in either direction, because an effective conclusion reached on incomplete facts is the single most consequential error available on this path - it is a public statement, made by officers who certify it personally.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr summary" cf="100"
           name="[US] G7 E11 - plain language summary of an adverse entity level conclusion (Regulation S-K Item 308 a 3 and SEC Release 33-8810 II B 2)"
           alt="Gives a reader the adverse entity level conclusion in plain words">
    <condition rel="has icfr conclusion" subject="%S" object="ICFR Not Effective"/>
    <condition expression="'In plain terms: a finding in the most severe class stood at the period end date, so internal control over financial reporting cannot be reported as effective. There is no partial answer available - you cannot say effective except for this. What you can say is not effective, and why. The finding is described publicly, with its impact and the remediation.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr summary" cf="100"
           name="[US] G7 E11 - plain language summary of a favourable entity level conclusion (Regulation S-K Item 308 a 3 and AS 2201 para 82)"
           alt="Gives a reader the favourable entity level conclusion in plain words and says what it does not cover">
    <condition rel="has icfr conclusion" subject="%S" object="ICFR Effective"/>
    <condition expression="'In plain terms: nothing in the most severe class stood at the period end date, and every deficiency on the record has been evaluated rather than left open. So internal control over financial reporting can be reported as effective. That is a conclusion about that date and about what was examined. It is not a promise about anything nobody looked at.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has icfr judgement input" object="Management" cf="100"
           name="[US] E11 G5 - the entity level conclusion is management s own (Regulation S-K Item 308 a 3 and 17 CFR 240.13a-15 c)"
           alt="Names the entity level conclusion as management's judgement">
    <condition rel="has icfr conclusion" subject="%S" object="%IJ1"/>
  </relinst>
  <relinst type="has icfr applied instrument" object="Regulation S-K Item 308 as amended" cf="100"
           name="[US] G8 E11 - Item 308 is applied to the entity level conclusion (Regulation S-K Item 308, 17 CFR 229.308)"
           alt="Names the version of Regulation S-K Item 308 the entity level conclusion applied">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
  </relinst>
  <relinst type="has icfr applied instrument" object="SEC Release 33-8810 of 20 June 2007" cf="100"
           name="[US] G8 E12 - Release 33-8810 is applied to the entity level conclusion (SEC Release 33-8810 of 20 June 2007)"
           alt="Names the version of SEC Release 33-8810 the entity level conclusion applied">
    <condition rel="assessment has framework" subject="%S" object="US ICFR"/>
  </relinst>
  <relinst type="has icfr applied instrument" object="FDIC 12 CFR Part 363 effective 1 January 2026" cf="100"
           name="[US] G8 E11 - Part 363 is applied where the reporting regime is the insured depository institution regime (12 CFR Part 363)"
           alt="Names the version of 12 CFR Part 363 the entity level conclusion applied">
    <condition rel="assessment has reporting regime" subject="%S" object="FDICIA Part 363"/>
    <condition rel="assessment has framework" subject="%S" object="US ICFR" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="In writing to those charged with governance on a timely basis" cf="100"
           name="[UK] F10 - a significant deficiency is communicated in writing to those charged with governance on a timely basis (ISA UK 265 para 9)"
           alt="This deficiency is a significant deficiency, so it is communicated in writing to those charged with governance on a timely basis">
    <condition rel="has international classification" subject="%S" object="Significant Deficiency Reportable To Those Charged With Governance"/>
  </relinst>
  <relinst type="has communication requirement" object="To management at an appropriate level of responsibility on a timely basis" cf="100"
           name="[UK] F10 - a deficiency meriting management attention is communicated to management at an appropriate level (ISA UK 265 para 10 b)"
           alt="This deficiency merits management's attention, so it is communicated to management at an appropriate level of responsibility">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Management Attention"/>
  </relinst>
  <relinst type="has communication requirement" object="No communication requirement identified on the facts supplied" cf="100"
           name="[UK] F10 F10i - no communication requirement arises from the classification where the deficiency merits neither (ISA UK 265 paras 3 and 10 b)"
           alt="This deficiency merits neither the attention of those charged with governance nor management's attention, so no communication requirement arises from the classification">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition expression="countRelationshipInstances(%S,'is near miss','true') is equal to 0" weight="1"
               alt="This deficiency has not been recorded as an instance where the control only narrowly delivered the intended outcome"/>
    <condition expression="countRelationshipInstances(%S,'is significant control failing','true') is equal to 0" weight="1"
               alt="This deficiency has not been recorded as a significant control failing"/>
  </relinst>
  <relinst type="has communication requirement" object="Reported to the board even though it has been remediated" cf="100"
           name="[UK] F4b - a significant issue is reported to the board even where it has been remediated (FRC Corporate Governance Code Guidance 2024 para 262)"
           alt="This is a significant control failing that has been remediated, and the guidance still expects it to be reported to the board with the actions taken">
    <condition rel="is significant control failing" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%VC1" weight="1"/>
    <condition rel="has framework" subject="%VC1" object="UK Material Controls" weight="1"/>
    <condition rel="persists at period end" subject="%S" object="false" weight="1"/>
  </relinst>
  <relinst type="has communication requirement" object="Reported to the board even though it has been remediated" cf="100"
           name="[UK] F11 - a near miss is reported to the board (FRC Corporate Governance Code Guidance 2024 para 289)"
           alt="This is a near miss, which the guidance expects to be reported to the board even though it is not a clear deficiency">
    <condition rel="is near miss" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%VC2" weight="1"/>
    <condition rel="has framework" subject="%VC2" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[UK] F10 D13b - recipient of a significant deficiency communication (ISA UK 265 para 9 and ISA UK 260 definition of those charged with governance)"
           alt="Names the recipient of the communication of a significant deficiency on the international path">
    <condition rel="has communication requirement" subject="%S" object="In writing to those charged with governance on a timely basis"/>
    <condition expression="'Recipient: THOSE CHARGED WITH GOVERNANCE. That is the term the international standard uses and it is not a synonym for the board: it means the persons or organisations with responsibility for overseeing the strategic direction of the entity and the obligations related to its accountability, which in a bank is ordinarily the audit committee acting for the board. Where a deficiency concerns the oversight body itself, communicating only to it does not discharge the duty.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[UK] F10 - deadline for a significant deficiency communication (ISA UK 265 paras 9 and A12-1)"
           alt="States the deadline for communicating a significant deficiency on the international path">
    <condition rel="has communication requirement" subject="%S" object="In writing to those charged with governance on a timely basis"/>
    <condition expression="'Deadline: on a timely basis, ISA UK 265 paragraph 9 - not at the year end and not with the annual report. The standard adds that PROMPT communication to the directors of a listed entity can assist them to comply with the Code s provisions on internal control and on reporting to shareholders, paragraph A12-1, so the practical test is whether the communication arrives early enough to be acted on rather than merely recorded.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[UK] F10 - form and required content of a significant deficiency communication (ISA UK 265 paras 9 and 11)"
           alt="States the form and the required content of the written communication of a significant deficiency">
    <condition rel="has communication requirement" subject="%S" object="In writing to those charged with governance on a timely basis"/>
    <condition expression="'Form: IN WRITING, and the content is prescribed rather than left open. The written communication must include a description of the deficiency and an explanation of its POTENTIAL EFFECTS, together with sufficient information to enable the recipients to understand its context, ISA UK 265 paragraph 11. Potential effects, not actual ones - the explanation is owed whether or not anything has gone wrong - and the context element means the communication must say what the control was for, not only that it failed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[UK] F10 A12 - the paragraph a significant deficiency communication rests on (ISA UK 265 paras 6 b and 9)"
           alt="Names the instrument and paragraph the significant deficiency communication duty rests on">
    <condition rel="has communication requirement" subject="%S" object="In writing to those charged with governance on a timely basis"/>
    <condition expression="'Basis: ISA UK 265 paragraph 9, on a deficiency that in professional judgement merits the attention of those charged with governance, paragraph 6 b. This duty comes from the auditing standard and not from the Code. It therefore runs on its own timetable, it is owed whatever the declaration eventually says, and it is not discharged by anything published in the annual report.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication recipient" cf="100"
           name="[UK] F10 - recipient of a management level communication (ISA UK 265 paras 10 b and A26)"
           alt="Names the recipient of the communication of a deficiency meriting management attention">
    <condition rel="has communication requirement" subject="%S" object="To management at an appropriate level of responsibility on a timely basis"/>
    <condition expression="'Recipient: MANAGEMENT AT AN APPROPRIATE LEVEL OF RESPONSIBILITY, ISA UK 265 paragraph 10 b. Appropriate means a level with the authority to evaluate the deficiency and take the remedial action needed - ordinarily the person with direct responsibility for the control, which will not always be the control owner and is rarely the person who performed the failed instance.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication deadline" cf="100"
           name="[UK] F10 - deadline for a management level communication (ISA UK 265 para 10)"
           alt="States the deadline for communicating a deficiency meriting management attention">
    <condition rel="has communication requirement" subject="%S" object="To management at an appropriate level of responsibility on a timely basis"/>
    <condition expression="'Deadline: on a timely basis, the same standard as the higher class. A lower classification changes the addressee and not the urgency.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication form" cf="100"
           name="[UK] F10 - form of a management level communication (ISA UK 265 paras 10 b and A27)"
           alt="States that the form of a management level communication is not prescribed as written by the standard">
    <condition rel="has communication requirement" subject="%S" object="To management at an appropriate level of responsibility on a timely basis"/>
    <condition expression="'Form: not prescribed as written by paragraph 10 b, which is a real difference from the higher class. Writing it down is nonetheless the ordinary practice and the only way the communication can later be evidenced - and evidence matters here, because an unremediated deficiency that was previously communicated carries a heavier significance than one raised for the first time.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[UK] F10 A12 - the paragraph a management level communication rests on (ISA UK 265 paras 10 b and A22)"
           alt="Names the instrument and paragraph the management level communication duty rests on">
    <condition rel="has communication requirement" subject="%S" object="To management at an appropriate level of responsibility on a timely basis"/>
    <condition expression="'Basis: ISA UK 265 paragraph 10 b, on other deficiencies of sufficient importance to merit management s attention. The standard gives no threshold for sufficient importance and names only the likelihood and potential magnitude of misstatement as the test, paragraph A22, so this outcome rests on a judgement supplied to the assessment rather than on a rule inside it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[UK] F4b F11 A12 - basis of the board report for a remediated issue or a narrow escape (FRC Guidance 2024 paras 262 284 and 289)"
           alt="Names the paragraphs the internal board report rests on for a remediated issue or a near miss">
    <condition rel="has communication requirement" subject="%S" object="Reported to the board even though it has been remediated"/>
    <condition expression="'Basis: FRC guidance paragraph 262 - any significant issue should be reported to the board EVEN IF IT HAS BEEN REMEDIATED, together with the actions taken - and paragraph 289 for an instance where a control only narrowly delivered the intended outcome. The annual review must also consider the incidence of significant control failings and the action taken, paragraph 284. This is an internal reporting obligation and not a disclosure one: it runs whatever the declaration says and it is not satisfied by a clean declaration.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication basis" cf="100"
           name="[UK] F10i A12 - no communication duty is created merely by completing an assessment (ISA UK 265 paras 3 and 9)"
           alt="States that the absence of a communication requirement is not an assurance that nothing further exists">
    <condition rel="has communication requirement" subject="%S" object="No communication requirement identified on the facts supplied"/>
    <condition expression="'Basis: none arises. The written communication duty is triggered only by an IDENTIFIED significant deficiency, ISA UK 265 paragraph 9, and other communication is permitted but not required, paragraph 3 - so there is no nil-report obligation and none is asserted. Read this as the absence of a duty on these facts and not as an assurance that nothing further exists. The deficiency itself remains on the record and can be drawn into a combination later.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[UK] G7 F10 - plain language summary of a significant deficiency communication (ISA UK 265 paras 9 and 11)"
           alt="Gives a control owner the significant deficiency communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="In writing to those charged with governance on a timely basis"/>
    <condition expression="'In plain terms: write this up and get it to the audit committee promptly. Say what the control was for, what went wrong, and what COULD go wrong as a result - potential effects, even if nothing has actually gone wrong yet. Do not wait for the annual report: this duty runs on its own clock and the report does not discharge it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[UK] G7 F10 - plain language summary of a management level communication (ISA UK 265 para 10 b)"
           alt="Gives a control owner the management level communication duty in plain words">
    <condition rel="has communication requirement" subject="%S" object="To management at an appropriate level of responsibility on a timely basis"/>
    <condition expression="'In plain terms: tell the manager who can actually fix this, promptly. Not the person who performed the failed instance, and not necessarily the control owner - the level with authority to act. It need not be in writing, but write it down anyway: if the same thing comes back unfixed next year, the earlier communication is what makes it serious.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[UK] G7 F4b F11 - plain language summary of a board report for a remediated issue or near miss (FRC Corporate Governance Code Guidance 2024 paras 262 and 289)"
           alt="Gives a control owner the internal board report in plain words">
    <condition rel="has communication requirement" subject="%S" object="Reported to the board even though it has been remediated"/>
    <condition expression="'In plain terms: this still goes to the board, even though it has been fixed or was only narrowly avoided. Say what happened and what was done about it. Fixing something does not remove the need to report it internally, and a clean declaration in the annual report is a different question with a different answer.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has communication summary" cf="100"
           name="[UK] G7 F10i - plain language summary where no communication requirement arises (ISA UK 265 paras 3 and 9)"
           alt="Tells a control owner that no communication duty arises and that this is not a clean result">
    <condition rel="has communication requirement" subject="%S" object="No communication requirement identified on the facts supplied"/>
    <condition expression="'In plain terms: nothing has to be reported to anyone on these facts. That is the absence of an obligation, not a clean bill of health - the control still did not do what it was designed to do, and that stays on the record. If this looks wrong, the two significance judgements behind it are what to check.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F11 - a near miss is reportable and is not a clear deficiency (FRC Corporate Governance Code Guidance 2024 para 289)"
           alt="States that a near miss is reportable to the board and is not itself a clear deficiency">
    <condition rel="is near miss" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%VC3" weight="1"/>
    <condition rel="has framework" subject="%VC3" object="UK Material Controls" weight="1"/>
    <condition expression="'A category of its own, easily mishandled in both directions. Instances where a control only narrowly delivers the intended outcome - PARTICULARLY REPEATEDLY WITHIN A REPORTING PERIOD - should be reported to the board, and while they are not clear deficiencies they suggest the framework is not operating as intended, FRC guidance paragraph 289. So a near miss is not a declaration matter and it is not nothing either: it is an early signal about the framework rather than a finding against the control. The repetition qualifier is the part to watch - one narrow escape is noise, the same narrow escape four times is a pattern, and the guidance singles that out.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F12 - an improvement area brings a root cause and monitoring obligation (FRC Corporate Governance Code Guidance 2024 paras 287 and 288)"
           alt="States the root cause and monitoring obligations the guidance attaches to an improvement area">
    <condition rel="is improvement area" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%VC4" weight="1"/>
    <condition rel="has framework" subject="%VC4" object="UK Material Controls" weight="1"/>
    <condition expression="'What the guidance expects once an improvement area emerges, which goes further than fixing the control. The board should establish HOW IT AROSE, its impact, and how effective the remedial measures were - and should then RE-EVALUATE ITS MONITORING PROCESSES, FRC guidance paragraph 287. That last limb is the one most often skipped: if a material shortcoming had to be found by a test rather than by monitoring, the monitoring is part of what needs attention. Remediation of the control alone does not answer paragraph 287.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F11 F13 - a repeated narrow escape within the period is singled out by the guidance (FRC Corporate Governance Code Guidance 2024 para 289)"
           alt="States that a narrow escape recurring within the period is the case the guidance singles out">
    <condition rel="is near miss" subject="%S" object="true"/>
    <condition rel="recurred within the period" subject="%S" object="true" weight="1"/>
    <condition rel="deficiency of control" subject="%S" object="%VC5" weight="1"/>
    <condition rel="has framework" subject="%VC5" object="UK Material Controls" weight="1"/>
    <condition expression="'This narrow escape recurred within the reporting period, which is the case the guidance names expressly: such instances should be reported to the board PARTICULARLY WHERE THEY HAPPEN REPEATEDLY within a reporting period, FRC guidance paragraph 289. Recurrence is what turns a tolerance into a signal. The guidance does not say how many occurrences make a pattern, and no threshold is asserted here - but a control that keeps only just working is one whose design margin should be re-examined rather than one whose instances should keep being counted.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk reportable statement" object="Reporting against a publicised in year failure alongside a clean declaration" cf="100"
           name="[UK] F4a - a failure publicised during the year is reported against even where the declaration is clean (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="A failure in this material control was publicised during the year, so reporting against it is expected even though the declaration at the balance sheet date is clean">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Operated Effectively"/>
    <condition rel="has deficiency" subject="%S" object="%VD1" weight="1"/>
    <condition rel="publicly disclosed during the year" subject="%VD1" object="true" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F4a - the publicised failure carve back, and the question the sources leave open (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="Explains the carve-back for a failure publicised during the year and that the sources do not say where the reporting sits">
    <condition rel="has uk reportable statement" subject="%S" object="Reporting against a publicised in year failure alongside a clean declaration"/>
    <condition expression="'A carve-back to the remediated-failure rule, and an open question inside it. Ordinarily a failure rectified by the balance sheet date need not be reported. Where it was PUBLICISED DURING THE YEAR the FRC expects reporting against it even so, because shareholders and stakeholders are already aware of it, Provision 29 Mythbuster of 29 January 2026. Two things this is NOT. It is not a qualification of the declaration: the declaration here is clean and stays clean, and this reporting sits alongside it. And no fetched source says WHERE it sits - inside the Provision 29 section of the annual report or elsewhere in it - so the expectation is stated here without asserting a location. An institution should take that placement decision deliberately and record it.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has control judgement input" object="The Board" cf="100"
           name="[UK] F4a G5 - where the reporting against a publicised failure sits is a board judgement (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="Names the placement of the reporting against a publicised failure as a board judgement">
    <condition rel="has uk reportable statement" subject="%S" object="Reporting against a publicised in year failure alongside a clean declaration"/>
  </relinst>
  <relinst type="has uk declaration summary" cf="100"
           name="[UK] G7 F2 - plain language summary of an adverse declaration outcome (UK Corporate Governance Code 2024 Provision 29 third bullet)"
           alt="Gives a control owner the adverse declaration outcome in plain words">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Did Not Operate Effectively"/>
    <condition expression="'In plain terms: this is a material control and it was not working at the balance sheet date, so the annual report has to say so. It must describe the control and what went wrong, and the action taken OR PROPOSED to put it right - a plan is enough, so there is no reason to delay the disclosure until the work is finished. The board may hold back commercially sensitive detail; it cannot hold back the disclosure.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration summary" cf="100"
           name="[UK] G7 F1 F1b F4 - plain language summary of a favourable declaration outcome (FRC Corporate Governance Code Guidance 2024 paras 296 and 297)"
           alt="Gives a control owner the favourable declaration outcome in plain words and says how far it goes">
    <condition rel="has uk declaration determination" subject="%S" object="Material Control Operated Effectively"/>
    <condition expression="'In plain terms: this material control was working at the balance sheet date, properly designed and properly run, so the declaration is clean and nothing needs describing. A failure during the year that was fixed and retested before that date does not change this. It is a reasonable conclusion from the work done, not a guarantee, and it is about this control rather than the whole framework.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration summary" cf="100"
           name="[UK] G7 F9a - plain language summary of the not determinable declaration outcome (FRC Corporate Governance Code Guidance 2024 para 298)"
           alt="Gives a control owner the not determinable declaration outcome in plain words">
    <condition rel="has uk declaration determination" subject="%S" object="Effectiveness Not Determinable"/>
    <condition expression="'In plain terms: there is not enough to say whether this material control was working at the balance sheet date. Nothing has been found against it and nothing in its favour. Where the board cannot determine effectiveness it can use the comply or explain nature of the Code and explain the position in the annual report. Treating this as a clean declaration would not be right. The open questions say what is missing.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration summary" cf="100"
           name="[UK] G7 F5 - plain language summary where the control is outside the designation (UK Corporate Governance Code 2024 Provision 29 second bullet)"
           alt="Gives a control owner the no declaration consequence outcome in plain words">
    <condition rel="has uk declaration determination" subject="%S" object="No Declaration Consequence"/>
    <condition expression="'In plain terms: this is not one of the board s material controls, so the declaration in the annual report does not cover it and nothing about it goes there. It is not off the hook. Anything found is still recorded, still classified, and still reported to whoever needs to know. The designation is the board s and it can change from year to year.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] G7 F10e - plain language summary of a significant deficiency classification (ISA UK 265 paras 6 b 9 and 11)"
           alt="Gives a control owner the significant deficiency classification in plain words">
    <condition rel="has international classification" subject="%S" object="Significant Deficiency Reportable To Those Charged With Governance"/>
    <condition expression="'In plain terms: this is serious enough that the people overseeing the bank s reporting need to hear about it, in writing and promptly. The write-up has to say what could go wrong as a result, not just what did. This is about who gets told. Whether anything appears in the annual report is a separate question answered by the declaration, and the answer there can be different.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] G7 F10e - plain language summary of a management attention classification (ISA UK 265 para 10 b)"
           alt="Gives a control owner the management attention classification in plain words">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Management Attention"/>
    <condition expression="'In plain terms: worth a manager s attention but not the oversight committee s. It goes to someone senior enough to fix it, promptly. The line between this and the lowest class is a judgement rather than a rule - the standard gives no threshold - so if this feels like the wrong box, the judgement behind it is what to revisit.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] G7 F10e F10i - plain language summary of the lowest classification where nothing else creates a duty (ISA UK 265 paras 3 10 b and A22)"
           alt="Gives a control owner the lowest classification in plain words and warns against reading it as clean">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition expression="countRelationshipInstances(%S,'is near miss','true') is equal to 0" weight="1"
               alt="This deficiency has not been recorded as an instance where the control only narrowly delivered the intended outcome"/>
    <condition expression="countRelationshipInstances(%S,'is significant control failing','true') is equal to 0" weight="1"
               alt="This deficiency has not been recorded as a significant control failing"/>
    <condition expression="'In plain terms: on the judgements given, this does not need escalating to anyone. It is not a clean result - the control did not do its job, the shortfall stays on the record, and it can be grouped with others later to reach something more serious. Nothing here says no other problems exist, only that nothing was found that had to be reported.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] G7 F10e F11 - plain language summary of the lowest classification where the matter is a near miss (FRC Corporate Governance Code Guidance 2024 para 289)"
           alt="Tells a control owner that the classification creates no duty but the narrow escape still goes to the board">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition rel="is near miss" subject="%S" object="true" weight="1"/>
    <condition expression="'In plain terms: the classification itself asks nothing of you - on the judgements given this merits neither the oversight committee s attention nor a manager s. The narrow escape does. Report it to the board as a signal about the framework rather than a finding against the control, and say whether it has happened before in the period, because repetition is the part the guidance singles out.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] G7 F10e G6 - plain language summary where the classification could not be determined (ISA UK 265 paras 6 b and 10 b)"
           alt="Tells a control owner that the classification could not be determined and that nothing has been assumed">
    <condition rel="has international classification" subject="%S" object="Classification Not Determinable"/>
    <condition expression="'In plain terms: this cannot be classified yet. Two judgements decide it - does the oversight committee need to know, and does a manager need to know - and at least one is missing. Neither has been guessed. Guessing low would hide a report that may be owed; guessing high would invent one. The open questions say exactly what is needed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has uk declaration finding" cf="100"
           name="[UK] F10a - the declaration is other information and this output is not an audit opinion (FRC Mythbuster of 24 June 2026 and ISA UK 720)"
           alt="States that the declaration is other information read by the auditor and that this result is a board determination">
    <condition rel="has uk declaration determination" subject="%S" object="%VF1"/>
    <condition rel="is material control" subject="%S" object="true" weight="1"/>
    <condition expression="'What this result is, and what no reader should take it for. Auditing standards were NOT changed or extended in response to the Code: the auditor reads and considers the declaration as OTHER INFORMATION for material inconsistency under ISA UK 720, and performing those procedures DOES NOT REPRESENT AN ASSURANCE ENGAGEMENT, Provision 29 Mythbuster of 24 June 2026. The board s material controls and the controls relevant to the audit overlap but are not identical and serve different purposes. So this is a board and management determination. It is not an audit opinion, it is not assured, and it does not become either by being published.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has international classification finding" cf="100"
           name="[UK] F10g F10e - the classification turns on potential and not on what happened (ISA UK 265 paras A5 and A22)"
           alt="States that the classification rests on the likelihood and potential magnitude of misstatement">
    <condition rel="has international classification" subject="%S" object="%VF2"/>
    <condition rel="merits attention of those charged with governance" subject="%S" object="%VG2" weight="1"/>
    <condition expression="'The test behind both judgements, stated once. Significance turns on the LIKELIHOOD that a misstatement could occur and on its POTENTIAL MAGNITUDE, ISA UK 265 paragraphs A5 and A22, and a significant deficiency may exist even though no misstatement was identified. So a year in which nothing went wrong is not evidence that a weak control is insignificant, and a deficiency should not be classified downwards because its consequences happened not to materialise.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="ISA UK 265 Updated September 2025" cf="100"
           name="[UK] G8 F10 - ISA UK 265 is applied to the classification and communication layer (ISA UK 265, communicating deficiencies in internal control)"
           alt="Names the version of ISA UK 265 the classification and communication determination applied">
    <condition rel="has international classification" subject="%S" object="%VI1"/>
  </relinst>
  <relinst type="has deficiency applied instrument" object="ISA UK 330 Revised July 2017 Updated September 2025" cf="100"
           name="[UK] G8 F10h - ISA UK 330 is applied where a material misstatement was not detected by the control (ISA UK 330 para A41)"
           alt="Names the version of ISA UK 330 relied on for the strong indicator">
    <condition rel="material misstatement not detected by control" subject="%S" object="true"/>
    <condition rel="deficiency of control" subject="%S" object="%VC6" weight="1"/>
    <condition rel="has framework" subject="%VC6" object="UK Material Controls" weight="1"/>
  </relinst>
  <relinst type="has deficiency open question" cf="100"
           name="[UK] F11 G6 - whether the control only narrowly delivered the intended outcome (FRC Corporate Governance Code Guidance 2024 para 289)"
           alt="No answer has been recorded on whether this was a near miss rather than a failure">
    <condition rel="has international classification" subject="%S" object="Deficiency Meriting Neither"/>
    <condition expression="countRelationshipInstances(%S,'is near miss',*) is equal to 0" weight="1"
               alt="No answer has been recorded on whether the control only narrowly delivered the intended outcome"/>
    <condition expression="'Whether this was a NEAR MISS - an instance where the control only narrowly delivered the intended outcome, FRC guidance paragraph 289. It matters precisely because this classification reaches no communication duty: a near miss is reportable to the board even though it is not a clear deficiency, and especially where it recurred within the period. So a yes here adds a reporting obligation that the classification on its own does not produce.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[UK] G1 G9 G11 - relays the declaration outcome onto the umbrella surface (UK Corporate Governance Code 2024 Provision 29 second bullet)"
           alt="Carries the declaration outcome reached for this control onto the single surface a caller can query">
    <condition rel="has uk declaration determination" subject="%S" object="%UK1"/>
    <condition expression="'Declaration outcome: ' + %UK1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[UK] G1 G9 - relays a required disclosure element onto the umbrella surface (UK Corporate Governance Code 2024 Provision 29 third bullet)"
           alt="Carries a disclosure element required for this control onto the single surface a caller can query">
    <condition rel="has uk disclosure element" subject="%S" object="%UE1"/>
    <condition expression="'Required disclosure: ' + %UE1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[UK] G1 G9 G12 - relays a reportable statement attached to a clean declaration onto the umbrella surface (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="Carries a reportable statement attached to this control onto the single surface a caller can query">
    <condition rel="has uk reportable statement" subject="%S" object="%UR1"/>
    <condition expression="'Reportable alongside the declaration: ' + %UR1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[UK] G1 G9 - the failure in this control must be described in the declaration (UK Corporate Governance Code 2024 Provision 29 third bullet)"
           alt="Records on the umbrella surface that the failure in this control must be described">
    <condition rel="must be described in the declaration" subject="%S" object="true"/>
    <condition expression="'Must be described in the declaration: yes.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[UK] G1 G9 G3 - the failure in this control need not be described in the declaration (FRC Provision 29 Mythbuster of 29 January 2026)"
           alt="Records on the umbrella surface that nothing about this control need be described in the declaration">
    <condition rel="must be described in the declaration" subject="%S" object="false"/>
    <condition expression="'Must be described in the declaration: no. Nothing is owed to the declaration about this control on these facts. That is a conclusion about the declaration only - any communication obligation and any internal reporting obligation are separate questions, answered separately, and may still be owed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has determination" cf="100"
           name="[US] G1 G9 A3 - relays a scope decline onto the umbrella surface (17 CFR 240.13a-15 f and 17 CFR 229.308 a 2)"
           alt="Carries onto the umbrella surface the fact that this control falls outside the internal control over financial reporting a US determination covers">
    <condition rel="is out of scope for the framework" subject="%S" object="true"/>
    <condition rel="has framework" subject="%S" object="US ICFR" weight="1"/>
    <condition expression="'Scope: this control falls outside internal control over financial reporting as defined at 17 CFR 240.13a-15 f, which is what Item 308 a 2 asks management to assess, so no determination on its effectiveness has been reached on this path. The scope decline reasons on this result say which boundary it fell outside. This is a statement about the boundary of the framework and not a finding against the control.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has framework statement" cf="100"
           name="[CORE] G8 G9 - names the framework the control level determinations applied (brief section 4, one framework parameter selects the overlay)"
           alt="Names on the umbrella surface the reporting framework these determinations were reached under">
    <condition rel="has framework" subject="%S" object="%UF1"/>
    <condition expression="'Framework applied to this control: ' + %UF1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has framework statement" cf="100"
           name="[CORE] G4 G9 - the determinations on this surface run at full certainty (brief section 8, no probabilistic score is presented)"
           alt="States that the determinations relayed onto this surface carry no probabilistic score">
    <condition rel="has framework" subject="%S" object="%UF2"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'How to read these determinations. Each one is reached at full certainty or not reached at all: there is no score, no confidence percentage and no ranking of alternatives. Where the facts do not support a determination the method says so and lists what is missing, rather than returning a weaker version of an answer. A missing determination is therefore informative - it means a question is open, not that the answer is marginal.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has framework statement" cf="100"
           name="[CORE] G1 G2 G9 - what this surface is and where the reasoning sits (brief section 8, the evidence tree cites every rule)"
           alt="Explains that this surface relays conclusions and that the reasoning sits with each decision point">
    <condition rel="has framework" subject="%S" object="%UF3"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="'What this surface is. It collects, in one place, every determination reached about this control, whichever decision points the facts could reach. It decides nothing itself: each line is relayed from the decision point that produced it, and the reasoning, the findings and the source paragraph for each live with that decision point rather than here. Query the individual decision point to see why an answer was reached; query this one to see what was reached.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has framework statement" cf="100"
           name="[CORE] G6 G9 - no determination at all was reached for this control (brief section 8, open questions are listed rather than guessed)"
           alt="States that no determination was reached for this control and points to the open questions">
    <condition rel="has framework" subject="%S" object="%UF4"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has determination',*) is equal to 0" weight="1"
               alt="No determination of any kind was reached for this control on the facts supplied"/>
    <condition expression="'No determination of any kind has been reached for this control. That is a statement about the facts supplied and not about the control: nothing has been found for it or against it. The rolled up open questions on this result list every fact still needed, in the order the reasoning needs them. Supply those and query again.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 - relays the severity determination onto the deficiency surface (AS 2201 paras 63 to 70)"
           alt="Carries the severity determination reached for this deficiency onto the single surface a caller can query">
    <condition rel="has us severity determination" subject="%S" object="%US1"/>
    <condition expression="'Severity: ' + %US1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 - relays the international classification onto the deficiency surface (ISA UK 265 paras 6 b and 10 b)"
           alt="Carries the classification reached for this deficiency onto the single surface a caller can query">
    <condition rel="has international classification" subject="%S" object="%UI1"/>
    <condition expression="'Classification: ' + %UI1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G10 G9 - relays the communication determination onto the deficiency surface (AS 2201 paras 78 to 81 and ISA UK 265 paras 9 and 10 b)"
           alt="Carries the communication determination reached for this deficiency onto the single surface a caller can query">
    <condition rel="has communication requirement" subject="%S" object="%UC1"/>
    <condition expression="'Communication: ' + %UC1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 - relays a disclosure requirement onto the deficiency surface (Regulation S-K Item 308 a 3)"
           alt="Carries a disclosure requirement reached for this deficiency onto the single surface a caller can query">
    <condition rel="has us disclosure requirement" subject="%S" object="%UQ1"/>
    <condition expression="'Disclosure: ' + %UQ1" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 D12 - a retest of the remediated control is required (AS 2201 paras 52 and 53)"
           alt="Records on the deficiency surface that a retest is required">
    <condition rel="requires retest" subject="%S" object="true"/>
    <condition expression="'Retest required: yes. The retest conditions on this result say what the retest must cover. Remediation planning beyond stating that a retest is needed is outside what this method decides.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 G3 D12 - no retest of the control is required on these facts (AS 2201 paras 52 and 53)"
           alt="Records on the deficiency surface that no retest is required">
    <condition rel="requires retest" subject="%S" object="false"/>
    <condition expression="'Retest required: no. Nothing on these facts calls for the control to be retested before the conclusion stands. This is not a statement that the control needs no further attention - the severity or classification on this result, and any communication owed, are separate answers.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 D9 - the deficiency still stood at the period end date (AS 2201 para B2 and 17 CFR 229.308 a 2)"
           alt="Records on the deficiency surface that the deficiency still stood at the period end date">
    <condition rel="persists at period end" subject="%S" object="true"/>
    <condition expression="'Standing at the period end date: yes. The assessment is as of that date, so a deficiency still standing then carries its full consequences into the reporting outcome.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G1 G9 G3 D9 - the deficiency no longer stood at the period end date (AS 2201 paras 52 and 53 and SEC Release 33-8810 II A 2 b)"
           alt="Records on the deficiency surface that the deficiency no longer stood at the period end date">
    <condition rel="persists at period end" subject="%S" object="false"/>
    <condition expression="'Standing at the period end date: no - it was remediated, and the remediated control was retested over a sufficient period before that date. Note what this does and does not do. It removes the deficiency from the period end position, which is what the reporting outcome turns on. It does not erase the deficiency: it happened, it is on the record, and any internal reporting obligation it carries is unaffected by its having been fixed.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency framework statement" cf="100"
           name="[CORE] G8 G9 - names the framework the deficiency level determinations applied (brief section 4, one framework parameter selects the overlay)"
           alt="Names on the deficiency surface the reporting framework these determinations were reached under">
    <condition rel="deficiency of control" subject="%S" object="%UB1"/>
    <condition rel="has framework" subject="%UB1" object="%UF5" weight="1"/>
    <condition expression="'Framework applied to this deficiency: ' + %UF5" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency framework statement" cf="100"
           name="[CORE] G14 G9 - names the control and the component the deficiency was evaluated in (COSO Internal Control Integrated Framework 2013 executive summary, five components)"
           alt="Names on the deficiency surface the control the deficiency belongs to and the component it sits in">
    <condition rel="deficiency of control" subject="%S" object="%UB2"/>
    <condition rel="for coso component" subject="%S" object="%UP2" weight="1"/>
    <condition expression="'Evaluated against control ' + %UB2" value="%UX2" weight="1"/>
    <condition expression="%UX2 + ', in internal control component: '" value="%UY2" weight="1"
               alt="Composes the control and component line for the deficiency surface"/>
    <condition expression="%UY2 + %UP2" value="%O" weight="1"
               alt="Completes the control and component line for the deficiency surface"/>
  </relinst>
  <relinst type="has deficiency framework statement" cf="100"
           name="[CORE] G6 G9 - no determination at all was reached for this deficiency (brief section 8, open questions are listed rather than guessed)"
           alt="States that no determination was reached for this deficiency and points to the open questions">
    <condition rel="deficiency of control" subject="%S" object="%UB3"/>
    <condition rel="has deficiency type" subject="%S" object="%UT3" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has deficiency determination',*) is equal to 0" weight="1"
               alt="No determination of any kind was reached for this deficiency on the facts supplied"/>
    <condition expression="'No determination of any kind has been reached for this deficiency. It is recorded, and it is unevaluated - which is not the same as minor. The open questions on this result name the judgements still needed. An unevaluated deficiency also blocks a favourable conclusion at the entity level, so leaving it open has a consequence beyond this one record.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] G10 D13 - the communication determination has five parts and all five are stated (brief section 8, communication is determined for every finding)"
           alt="States the five parts of the communication determination and that it is an output in its own right">
    <condition rel="has communication requirement" subject="%S" object="%UC2"/>
    <condition expression="'How to read the communication determination. It is an answer in its own right and not a footnote to the severity: WHETHER anything must be communicated, TO WHOM, BY WHEN, IN WHAT FORM, and the PARAGRAPH that makes it so - five parts, stated separately on this result. It is reached on both reporting frameworks, from different instruments, so the paragraph relied on tells you which one produced it. And it is stated even where the determination is that nothing further is owed, because a recorded nothing-owed is auditable and a silence is not.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has deficiency determination" cf="100"
           name="[CORE] D13a D13d - the output never asserts that no other deficiency exists (AS 2201 paras 82 and 83, AS 1305 para 08, ISA UK 265 paras 3 and 9)"
           alt="States that no negative assurance is expressed about deficiencies that were not found">
    <condition rel="deficiency of control" subject="%S" object="%UB4"/>
    <condition rel="has deficiency type" subject="%S" object="%UT4" weight="1"/>
    <condition expression="'The one limit both reporting frameworks place on an output like this, stated because it is easy to forget. Neither permits negative assurance about what was not found: an assessment is not required to identify every deficiency, no report may say that none were noted, and a communication duty is triggered only by something actually identified. So this result reports what was found and what is owed on it. It says nothing whatever about deficiencies nobody looked for, and the absence of a line here is never evidence of a control working.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has rolled up open question" cf="100"
           name="[CORE] G6 - rolls up this control's own open questions (brief section 8, open questions are listed rather than concluded on a guess)"
           alt="Carries an open question raised about this control onto the single rolled up list">
    <condition rel="has open question" subject="%S" object="%O"/>
  </relinst>
  <relinst type="has rolled up open question" cf="100"
           name="[CORE] G6 - rolls up the open questions raised about this control's deficiencies (brief section 8, open questions are listed rather than concluded on a guess)"
           alt="Carries an open question raised about a deficiency in this control onto the single rolled up list">
    <condition rel="has deficiency" subject="%S" object="%UB5"/>
    <condition rel="has deficiency open question" subject="%UB5" object="%O" weight="1"/>
  </relinst>
  <relinst type="has rolled up open question" cf="100"
           name="[CORE] G6 - states that nothing is outstanding where no deficiency is recorded either (brief section 8, a missing fact is asked for rather than assumed)"
           alt="States that no open question is outstanding for this control and that no deficiency is recorded against it">
    <condition rel="has framework" subject="%S" object="%UF6"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has open question',*) is equal to 0" weight="1"
               alt="No open question was raised about this control itself"/>
    <condition expression="countRelationshipInstances(%S,'has deficiency',*) is equal to 0" weight="1"
               alt="No deficiency is recorded against this control, so no deficiency-level question can be outstanding either"/>
    <condition expression="'Nothing is outstanding: every fact the determinations above needed has been supplied, no judgement was left to a default, and no deficiency is recorded against this control. Read this precisely - it means the reasoning ran to completion on the facts given, not that the facts given were right. Whether each supplied judgement was sound is a matter for the person who made it, and the judgement inputs on this result name who should own each one.'" value="%O" weight="1"/>
  </relinst>
  <relinst type="has rolled up open question" cf="100"
           name="[CORE] G6 - states that nothing is outstanding for the control itself where a deficiency is recorded (brief section 8, a missing fact is asked for rather than assumed)"
           alt="States that no open question is outstanding about the control itself, and that any question listed concerns a deficiency recorded against it">
    <condition rel="has framework" subject="%S" object="%UF7"/>
    <condition rel="is a control under assessment" subject="%S" object="true" weight="1"/>
    <condition rel="has deficiency" subject="%S" object="%UB6" weight="1"/>
    <condition expression="countRelationshipInstances(%S,'has open question',*) is equal to 0" weight="1"
               alt="No open question was raised about this control itself"/>
    <condition expression="'Nothing is outstanding about the CONTROL itself: every fact the design, testing and declaration determinations needed has been supplied. A deficiency is recorded against this control, and a deficiency carries judgements of its own. So any other question on this list concerns that deficiency and not the control - and if this is the only line here, nothing is outstanding anywhere. The distinction matters because the two are answered by different people: the control facts by whoever tested it, the deficiency judgements by whoever must evaluate it.'" value="%O" weight="1"/>
  </relinst>
</rbl:kb>
