Description
Check explicit correction notice links and field vocabulary.
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.
Check explicit correction notice links and field vocabulary.
When to use this tool
Use it for official notice corrigendum parent link when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter noticeId, targetId, originalId, correctedFields, knownFields. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read parentMatches, selfLink, unknownFields. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Compare targetId with originalId, compare noticeId with targetId for self-linking, and return distinct correctedFields absent from knownFields.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| noticeId | Notice Id | Required. Text; maximum UTF-16 length 8192. |
| targetId | Target Id | Required. Text; maximum UTF-16 length 8192. |
| originalId | Original Id | Required. Text; maximum UTF-16 length 8192. |
| correctedFields | Corrected Fields | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| knownFields | Known Fields | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| parentMatches | Parent Matches | Required. Boolean. |
| selfLink | Self Link | Required. Boolean. |
| unknownFields | Unknown Fields | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
{
"input": {
"noticeId": "N1",
"targetId": "R1",
"originalId": "R1",
"correctedFields": [
"title",
"date"
],
"knownFields": [
"title"
]
},
"output": {
"parentMatches": true,
"selfLink": false,
"unknownFields": [
"date"
]
}
}Limitations and assumptions
- The tool neither resolves the notice nor verifies a correction's authority or effect. Exact field tokens and IDs are supplied evidence rather than a regulatory document review.
- 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 official notice corrigendum parent link, 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
- Regulatory Document Lifecycle Parent Token
Audit explicit document lifecycle links without submission validation.
- Application Fee Currency Reference Date
Calculate application fee currency reference date from explicit caller-supplied inputs.