Description
Compare explicit statement/source attribution and versions without verifying a claim.
A regulatory record check applies a supplied rule to labels, dates, identifiers, or amounts. Exact matches and clock boundaries matter, but a consistent record does not itself establish legal compliance. The governing jurisdiction, rule version, and authoritative evidence must be selected separately.
Compare explicit statement/source attribution and versions without verifying a claim.
When to use this tool
Use it for labeling statement claim source pair when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter statementId, claimSourceId, expectedSourceId, sourceVersion, expectedVersion. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read sourceMatches, versionMatches, linkedKey. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Compare claimSourceId with expectedSourceId and sourceVersion with expectedVersion, then return a serialized statement/source/version key.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| statementId | Statement Id | Required. Text; maximum UTF-16 length 8192. |
| claimSourceId | Claim Source Id | Required. Text; maximum UTF-16 length 8192. |
| expectedSourceId | Expected Source Id | Required. Text; maximum UTF-16 length 8192. |
| sourceVersion | Source Version | Required. Text; maximum UTF-16 length 8192. |
| expectedVersion | Expected Version | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| sourceMatches | Source Matches | Required. Boolean. |
| versionMatches | Version Matches | Required. Boolean. |
| linkedKey | Linked Key | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"statementId": "S1",
"claimSourceId": "C1",
"expectedSourceId": "C1",
"sourceVersion": "v2",
"expectedVersion": "v1"
},
"output": {
"sourceMatches": true,
"versionMatches": false,
"linkedKey": "[\"S1\",\"C1\",\"v2\"]"
}
}Limitations and assumptions
- Matching identifiers does not verify the source, substantiate a claim, or establish lawful labeling. The composite key preserves literal metadata only.
- 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 labeling statement claim source pair, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- eCTD Leaf Title File Extension Pair
Inspect supplied leaf-title presence and filename extension under an explicit list.
- Regulatory Country Code Source Crosswalk
Apply an explicitly supplied country-code crosswalk without a built-in registry.