Fimbriation Legality Checker for Tincture Conflicts
Audit caller witnessed fimbriation separating otherwise conflicting layers; cannot establish legal grant eligibility. Feature columns, independently annotated in order: same-category layers, continuous separating fimbriation, opposite-category separator, jurisdiction verified exception. Unknown evidence and compatible classes retained; not automated semantic, historical, identity, legal or safety determination.
Description
Fimbriation review involves the relationship between adjoining categories, the border and an applicable exception.
Fimbriation review involves the relationship between adjoining categories, the border and an applicable exception.1
Declared evidence supports a review candidate rather than a legal or heraldic ruling. The tool compares supplied binary annotations with a fixed candidate scheme and distinguishes compatible from fully witnessed candidates.
When to use Fimbriation Legality Checker for Tincture Conflicts
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 Fimbriation Legality Checker for Tincture Conflicts 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 four binary observed and known flags in order: adjacent same-category tinctures, continuous intervening border, opposite-category border tincture and verified applicable exception. The single candidate requires [1,1,1,1]. Known mismatches exclude it; unknown constrained flags retain compatibility without full witnessing.
| Candidate | Same-category layers | Continuous separator | Opposite-category separator | Exception verified |
|---|---|---|---|---|
| caller-supported-separation | Known present | Known present | Known present | Known present |
candidate requires all four 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,
1
],
"featureKnownFlags": [
1,
1,
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"caller-supported-separation"
],
"witnessedClasses": [
"caller-supported-separation"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
The scheme is a bounded review aid. It does not inspect artwork, independently verify the exception or grant heraldic/legal approval.
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 Proper Charges Tincture Rule Exemption Checker: A proper-charge exemption review needs evidence that the depiction and adopted exception match. 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
- Proper Charges Tincture Rule Exemption Checker
A proper-charge exemption review needs evidence that the depiction and adopted exception match.
- Divided Field Tincture Pairing Validator
A divided-field review distinguishes partition geometry, adjacent tinctures and reference applicability.