Description
Calculate commitment evidence support share from explicit caller-supplied inputs.
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.
Calculate commitment evidence support share from explicit caller-supplied inputs.
When to use this tool
Use it for commitment evidence support share when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter commitmentIds, evidenceIds, evidenceVerified, commitmentClosed. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read closedCommitments, supportedClosed, share, defined. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Count distinct closed commitment IDs and distinct closed IDs having a nonempty evidenceId and evidenceVerified true. Divide supported closed commitments by closed commitments, or return zero with defined false for an empty base.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| commitmentIds | Commitment Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| evidenceIds | Evidence Ids | Required. Array of Text; maximum UTF-16 length 8192.; maximum items 256. |
| evidenceVerified | Evidence Verified | Required. Array of Boolean.; maximum items 256. |
| commitmentClosed | Commitment Closed | Required. Array of Boolean.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| closedCommitments | Closed Commitments | Required. Safe integer. |
| supportedClosed | Supported Closed | Required. Safe integer. |
| share | Dimensionless fraction using the denominator described above; not a percentage numeral. | Required. Finite number. |
| defined | Whether the associated denominator or quantity is defined; read this before interpreting a zero placeholder. | Required. Boolean. |
{
"input": {
"commitmentIds": [
"a",
"a",
"b"
],
"evidenceIds": [
"e1",
"",
""
],
"evidenceVerified": [
true,
false,
false
],
"commitmentClosed": [
true,
true,
true
]
},
"output": {
"closedCommitments": 2,
"supportedClosed": 1,
"share": 0.5,
"defined": true
}
}Limitations and assumptions
- A single qualifying record supports an ID even if another record for it lacks evidence. The flags and links are caller annotations, not independently verified closure or regulatory compliance.
- 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 commitment evidence support share, 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
- Commitment Deadline Clock Gap
Apply explicitly credited clock exclusions to a supplied administrative deadline; no regulatory calendar is inferred.
- Application Fee Currency Reference Date
Calculate application fee currency reference date from explicit caller-supplied inputs.