Description
Audit explicit responsibility flags against task-specific shared-ownership rules.
Quality records separate measured results, reference values, acceptance rules, and supporting evidence. Arithmetic consistency and record coverage can be checked against supplied criteria without establishing traceability, approving a method, or deciding product conformity.
Audit explicit responsibility flags against task-specific shared-ownership rules.
When to use this tool
Use it for quality agreement responsibility overlap check when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter tasks, firstResponsible, secondResponsible, sharedAllowed. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read unowned, conflicting, validShared. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require task and responsibility arrays of matching length. List tasks assigned to neither party as unowned, tasks assigned to both without sharedAllowed as conflicting, and jointly assigned tasks with sharedAllowed as validShared.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| tasks | Tasks | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| firstResponsible | First Responsible | Required. Array of Boolean.; maximum items 256. |
| secondResponsible | Second Responsible | Required. Array of Boolean.; maximum items 256. |
| sharedAllowed | Shared Allowed | Required. Array of Boolean.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| unowned | Unowned | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| conflicting | Conflicting | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| validShared | Valid Shared | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
{
"input": {
"tasks": [
"A",
"B",
"C"
],
"firstResponsible": [
true,
true,
false
],
"secondResponsible": [
true,
true,
false
],
"sharedAllowed": [
false,
true,
false
]
},
"output": {
"unowned": [
"C"
],
"conflicting": [
"A"
],
"validShared": [
"B"
]
}
} Limitations and assumptions
- Results preserve input rows and duplicate task labels. A boolean responsibility assignment does not establish contractual ownership, authority, or performance of a task.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For quality agreement responsibility overlap check, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Quality Change Effective Training Gap
Calculate quality change effective training gap from explicit caller-supplied inputs.
- Quality Charge Refund Base
Supplied charge/refund ledger arithmetic with signed outstanding refunds.