Description
Inspect supplied submission hierarchy metadata without interpreting regulatory requirements.
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.
Inspect supplied submission hierarchy metadata without interpreting regulatory requirements.
When to use this tool
Use it for submission reference depth gap when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter referenceParts, expectedDepth, requiredPrefix. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read actualDepth, depthGap, prefixMatches. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Count referenceParts, subtract the nonnegative expectedDepth, and test whether every requiredPrefix token equals its aligned leading reference part.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| referenceParts | Reference Parts | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| expectedDepth | Expected Depth | Required. Safe integer; minimum 0. |
| requiredPrefix | Required Prefix | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| actualDepth | Actual Depth | Required. Safe integer. |
| depthGap | Depth Gap | Required. Safe integer. |
| prefixMatches | Prefix Matches | Required. Boolean. |
{
"input": {
"referenceParts": [
"module",
"section",
"leaf"
],
"expectedDepth": 2,
"requiredPrefix": [
"module"
]
},
"output": {
"actualDepth": 3,
"depthGap": 1,
"prefixMatches": true
}
}Limitations and assumptions
- An empty required prefix matches. Tokens are not path-normalized or interpreted as a regulatory hierarchy; matching depth and prefix do not establish submission completeness.
- 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 submission reference depth gap, 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
- Authority Receipt Submission Time Offset
Compare explicit submission/receipt clocks after supplied common-reference offsets.
- Regulatory Submission Leaf Fragment Flag
Separate a supplied leaf reference at its first fragment marker; not a URI or regulatory submission validator.