Description
Add proposedValues to presentValues for after.
Metadata obligations and relations apply to a declared record scope. Field presence, source coverage, cardinality, and value correctness are independent properties.
Add proposedValues to presentValues for after.
When to use this tool
Use Metadata Cardinality One Property Budget when you need a narrow metadata consistency or coverage check.
How to use the tool and how it works
- Enter presentValues, minimum, maximum, proposedValues. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read after, missing, excess, within. Inspect within before interpreting the associated values.
Add proposedValues to presentValues for after. Compare it with the ordered minimum and maximum to return missing, excess, and inclusive within.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| presentValues | Present Values | Required. Safe integer; minimum 0. |
| minimum | Minimum | Required. Safe integer; minimum 0. |
| maximum | Maximum | Required. Safe integer. |
| proposedValues | Proposed Values | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| after | After | Required. Safe integer. |
| missing | Missing | Required. Safe integer. |
| excess | Excess | Required. Safe integer. |
| within | Whether the complete supplied cardinality lies within both bounds. | Required. Boolean. |
{
"input": {
"presentValues": 2,
"minimum": 1,
"maximum": 3,
"proposedValues": 2
},
"output": {
"after": 4,
"missing": 0,
"excess": 1,
"within": false
}
}Limitations and assumptions
- This models additions only; required cardinality, record structure, and duplicate-value semantics are not inferred.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Apply the complete metadata profile and inspect field values and provenance before accepting a record.
References
Similar or alternative tools
- Metadata Obligation Missing Count
Select requiredFields absent from presentFields, deduplicate in first-occurrence order, and return missingFields and missingCount.
- Metadata Field Obligation Flag
Set obligationApplies when both inScope and required are true; missingRequired additionally requires present false.