Abatement Mark Severity Ranking Lookup
Resolve source/edition abatement claims, including unsupported or disputed historical usage. Exact source/edition/context reference lookup; caller independently verifies text, applicability and uncertainty. No invented current, normative or universal data.
Description
Abatements are described in some heraldic texts as marks of dishonor, with historical use and severity claims requiring careful evidence.
Abatements are described in some heraldic texts as marks of dishonor, with historical use and severity claims requiring careful evidence.1
A source's proposed ranking is distinct from proof that the marks were actually imposed. Use this tool to retrieve the exact caller-supplied record and any source label returned with it.
When to use Abatement Mark Severity Ranking Lookup
Use this tool to retrieve the exact caller-supplied record and any source label returned with it. Establish the source, heraldic authority or layout convention, and use one consistent coordinate and length basis.
How to use Abatement Mark Severity Ranking Lookup and understand its results
- Establish the source, heraldic authority or layout convention, and use one consistent coordinate and length basis.
- Enter callerVerifiedEditionContextKeys, callerVerifiedReferenceTexts, queryEditionContextKey, using the field meanings and rules below, then run the tool.
- Read result.matchedCallerReference. Interpret the fields using their units, signs and evidence conventions below.
- If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedEditionContextKeys | Caller verified edition context keys; caller assertion or measurement requiring independent evidence | list of string | Required |
| callerVerifiedReferenceTexts | Caller verified reference texts; caller assertion or measurement requiring independent evidence | list of string | Required |
| queryEditionContextKey | Query edition context key | string | Required |
Enter nonempty aligned reference keys and texts. Keys must be distinct, nonblank strings of at most 128 UTF-16 units, and texts must be nonblank. Matching uses exact case-sensitive string equality, without trimming, search or approximate matching. The tool finds the query key and returns the text at that position unchanged; an unknown key fails. There is no installed complete reference catalog or live retrieval.
matchedText=texts[indexOfExact(queryKey,keys)] Use the exact units, boundary rules, ordering and missing-evidence conventions above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured calculation or selected reference, with fields listed below | object |
| result.matchedCallerReference | Caller reference text at the exact matched key, returned unchanged | string |
{
"input": {
"callerVerifiedEditionContextKeys": [
"source-a/edition-a/context-a",
"source-b/edition-b/context-b"
],
"callerVerifiedReferenceTexts": [
"AbatementSeverity independently established source-a reference",
"AbatementSeverity independently established source-b reference"
],
"queryEditionContextKey": "source-a/edition-a/context-a"
},
"output": {
"result": {
"matchedCallerReference": "AbatementSeverity independently established source-a reference"
}
}
}Limitations and assumptions
Success establishes a match in the supplied reference list. The tool does not obtain or authenticate the reference, confirm its contextual applicability, or validate the historical or cultural claims in the returned text.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.
Alternative or Complementary methods
Use Barry Stripes Count and Width Solver for this related task: Barry describes a field divided into horizontal bands; the bands occupy the height of the field.
Use Banner Shape Ratio to Shield Converter when its separate inputs and assumptions fit the question: A shield envelope's width-to-height ratio can be reused as a rectangular banner proportion.
References
-
Abatement Mark Severity Ranking Lookup — tool.io
Similar or alternative tools
- Barry Stripes Count and Width Solver
Barry describes a field divided into horizontal bands; the bands occupy the height of the field.
- Banner Shape Ratio to Shield Converter
A shield envelope's width-to-height ratio can be reused as a rectangular banner proportion.