Proper Charges Tincture Rule Exemption Checker
Audit the independent basis of a proper-charge tincture exception, not infer an exemption from token alone. Feature columns, independently annotated in order: charge explicitly proper, natural tinctures independently established, reference exemption independently verified. Unknown evidence and compatible classes retained; not automated semantic, historical, identity, legal or safety determination.
Description
A proper-charge exemption review needs evidence that the depiction and adopted exception match.
A proper-charge exemption review needs evidence that the depiction and adopted exception match.1
Candidate evidence is different from an authoritative grant of permission. The tool compares supplied binary annotations with a fixed candidate scheme and distinguishes compatible from fully witnessed candidates.
When to use Proper Charges Tincture Rule Exemption Checker
Use this tool to calculate or review the supplied observations under the stated rules. Establish the source tradition, viewing frame, coordinate units and independently annotated features.
How to use Proper Charges Tincture Rule Exemption Checker and understand its results
- Establish the source tradition, viewing frame, coordinate units and independently annotated features.
- Enter observedFeatureFlags, featureKnownFlags, using the field meanings and rules below, then run the tool.
- Read result.compatibleClasses, result.witnessedClasses, result.unknownFeatureIndices, using the output meanings and calculation rules below. Review unknown feature positions and distinguish compatible from witnessed candidates.
- Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedFeatureFlags | Observed feature flags | list of number | Required |
| featureKnownFlags | Feature known flags; binary 1 means the matched observation is known, 0 means unknown | list of number | Required |
Supply exactly three binary observed and known flags in order: charge explicitly proper, natural tinctures independently established, applicable exemption independently verified. The single proper-charge candidate requires [1,1,1]. Known zero excludes it; unknown retains compatibility without full witnessing.
| Candidate | Explicitly proper charge | Natural tinctures established | Exemption verified |
|---|---|---|---|
| caller-supported-proper-exemption | Known present | Known present | Known present |
properCandidate requires all three declared features known and present Use the matching field units and the exact boundary, ordering and reference rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Calculated observation or reference | object |
| result.compatibleClasses | compatible Classes | list |
| result.witnessedClasses | witnessed Classes | list |
| result.unknownFeatureIndices | unknown Feature Indices; zero-based positions in the relevant supplied record or adjacent-pair list; unresolved records kept separate from known results | list |
{
"input": {
"observedFeatureFlags": [
1,
1,
1
],
"featureKnownFlags": [
1,
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"caller-supported-proper-exemption"
],
"witnessedClasses": [
"caller-supported-proper-exemption"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
The flags are supplied annotations. The tool does not inspect coloration or establish that a particular authority allows the exemption.
Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.
Alternative or Complementary methods
For a related step, use Fimbriation Legality Checker for Tincture Conflicts: Fimbriation review involves the relationship between adjoining categories, the border and an applicable exception. For a complementary comparison, use Divided Field Tincture Pairing Validator: A divided-field review distinguishes partition geometry, adjacent tinctures and reference applicability.
References
Similar or alternative tools
- Fimbriation Legality Checker for Tincture Conflicts
Fimbriation review involves the relationship between adjoining categories, the border and an applicable exception.
- Divided Field Tincture Pairing Validator
A divided-field review distinguishes partition geometry, adjacent tinctures and reference applicability.