Description
Audit supplied document-version and status flag consistency.
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 supplied document-version and status flag consistency.
When to use this tool
Use it for qa document version obsolete conflict when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter version, effectiveVersion, obsolete, active. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read matchesEffective, conflictingStatus, staleActive. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Compare version with effectiveVersion exactly, flag conflictingStatus when obsolete and active are both true, and flag staleActive when active with a different version.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| version | Literal version label; no semantic version ordering is inferred. | Required. Text; maximum UTF-16 length 8192. |
| effectiveVersion | Effective Version | Required. Text; maximum UTF-16 length 8192. |
| obsolete | Obsolete | Required. Boolean. |
| active | Active | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| matchesEffective | Matches Effective | Required. Boolean. |
| conflictingStatus | Conflicting Status | Required. Boolean. |
| staleActive | Stale Active | Required. Boolean. |
{
"input": {
"version": "v1",
"effectiveVersion": "v2",
"obsolete": true,
"active": true
},
"output": {
"matchesEffective": false,
"conflictingStatus": true,
"staleActive": true
}
}Limitations and assumptions
- Version labels have no inferred ordering. These checks can report different inconsistencies independently without determining which status or version should be authoritative.
- 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 qa document version obsolete conflict, 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
- Document Control Copy Return Balance
Calculate document control copy return balance from explicit caller-supplied inputs.
- Document Copy Edition Token
Preserve explicit document/edition/copy identity without determining a controlled-copy status.