Divided Field Tincture Pairing Validator
Audit partition pairing rather than applying a layered-charge rule to adjacent field regions. Feature columns, independently annotated in order: field actually partitioned, tinctures juxtaposed not superposed, caller convention independently verified. Unknown evidence and compatible classes retained; not automated semantic, historical, identity, legal or safety determination.
Description
A divided-field review distinguishes partition geometry, adjacent tinctures and reference applicability.
A divided-field review distinguishes partition geometry, adjacent tinctures and reference applicability.1
Annotated evidence needs an explicit pairing scheme rather than a universal visual verdict. The tool compares supplied binary annotations with a fixed candidate scheme and distinguishes compatible from fully witnessed candidates.
When to use Divided Field Tincture Pairing Validator
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 Divided Field Tincture Pairing Validator 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: field partition present, juxtaposed rather than overlaid tinctures, and applicable reference independently verified. The single divided-field candidate requires [1,1,1]. Known mismatches exclude it; unknown constrained features retain compatibility but prevent witnessing.
| Candidate | Field partition | Juxtaposed tinctures | Convention verified |
|---|---|---|---|
| caller-supported-juxtaposition | Known present | Known present | Known present |
candidate requires partition=1, juxtaposition=1, verifiedReference=1 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-juxtaposition"
],
"witnessedClasses": [
"caller-supported-juxtaposition"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
The tool does not independently verify the reference or inspect the drawing. Witnessing this annotation scheme is not a universal tincture-rule determination.
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 Proper Charges Tincture Rule Exemption Checker: A proper-charge exemption review needs evidence that the depiction and adopted exception match.
References
-
Divided Field Tincture Pairing Validator — tool.io
Similar or alternative tools
- Fimbriation Legality Checker for Tincture Conflicts
Fimbriation review involves the relationship between adjoining categories, the border and an applicable exception.
- Proper Charges Tincture Rule Exemption Checker
A proper-charge exemption review needs evidence that the depiction and adopted exception match.