Hagiography Saint Legend Topos Checklist

Resolve independently annotated hagiographic motifs by source, not prove miracles. Exact caller independently verified reference-registry lookup retaining source/edition/context. No built-in complete dataset, current status or attribution authority fabricated.

Description

Hagiography presents saints' lives using narrative themes such as miracles and exemplary conduct.

Hagiography presents saints' lives using narrative themes such as miracles and exemplary conduct.1

A source-qualified motif record helps distinguish a literary topos from independently established biography. Use this tool to retrieve the exact caller-supplied record and any source label returned with it.

When to use Hagiography Saint Legend Topos Checklist

Use this tool to retrieve the exact caller-supplied record and any source label returned with it. Identify the community, narrative version, source edition and interpretation context; prepare any annotations independently.

How to use Hagiography Saint Legend Topos Checklist and understand its results

  1. Identify the community, narrative version, source edition and interpretation context; prepare any annotations independently.
  2. Enter callerVerifiedSourceEdition, callerVerifiedReferenceKeys, callerVerifiedReferenceTexts, queryReferenceKey, using the field meanings and rules below, then run the tool.
  3. Read result.matchedCallerReference, result.referenceSourceEdition. Interpret the fields using their units, signs and evidence conventions below.
  4. 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 fieldMeaningValue typeRequirement
callerVerifiedSourceEditionCaller verified source edition; caller assertion or measurement requiring independent evidencestringRequired
callerVerifiedReferenceKeysCaller verified reference keys; caller assertion or measurement requiring independent evidencelist of stringRequired
callerVerifiedReferenceTextsCaller verified reference texts; caller assertion or measurement requiring independent evidencelist of stringRequired
queryReferenceKeyQuery reference keystringRequired

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. Also supply a nonblank callerVerifiedSourceEdition of at most 256 UTF-16 units; it is copied to referenceSourceEdition. This is a caller assertion, not independent verification. 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 fieldMeaningValue type
resultStructured calculation or selected reference, with fields listed belowobject
result.matchedCallerReferenceCaller reference text at the exact matched key, returned unchangedstring
result.referenceSourceEditionSupplied nonblank source/edition label, copied unchanged; not authenticatedstring
json
{
  "input": {
    "callerVerifiedSourceEdition": "caller-reviewed-source-edition",
    "callerVerifiedReferenceKeys": [
      "verified-record-a",
      "verified-record-b"
    ],
    "callerVerifiedReferenceTexts": [
      "Saint legend topoi source-qualified context a",
      "Saint legend topoi source-qualified context b"
    ],
    "queryReferenceKey": "verified-record-a"
  },
  "output": {
    "result": {
      "matchedCallerReference": "Saint legend topoi source-qualified context a",
      "referenceSourceEdition": "caller-reviewed-source-edition"
    }
  }
}

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 Fieldwork Collection Consent Ethics Checklist for this related task: Folklore fieldwork creates records involving participants, communities and future reuse.

Use Aesop Attribution Split Fable Lookup when its separate inputs and assumptions fit the question: Fable attribution can differ across editions, translations and compilations.

References

  1. Hagiography Saint Legend Topos Checklist — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies