Herodotus Father of History Tall Tales Veracity Checker
Audit independent evidence concerning a specifically selected Herodotus report, not a blanket true/false verdict for the historian; mixed evidence retained. Independently annotated feature columns in order: independent corroboration witnessed, independent contradiction witnessed, source transmission established. Compatible classes are not established identities; unknown evidence retained. No automatic semantic parsing, diagnosis, authenticity or safety determination.
Description
Historical corroboration distinguishes independent support from contradiction and unassessed evidence.
Historical corroboration distinguishes independent support from contradiction and unassessed evidence.1
A feature checker records those annotations rather than issuing a universal truth verdict on Herodotus. Use Herodotus Father of History Tall Tales Veracity Checker to compare independently annotated features with the fixed rules.
When to use Herodotus Father of History Tall Tales Veracity Checker
Use Herodotus Father of History Tall Tales Veracity Checker to compare independently annotated features with the fixed rules. Annotate the ordered features below independently; use separate binary arrays for observed presence and whether each feature is known.
How to use Herodotus Father of History Tall Tales Veracity Checker and understand its results
- Annotate the ordered features below independently; use separate binary arrays for observed presence and whether each feature is known.
- Enter Observed feature flags, Feature known flags using the field table and validation rules below, then run the tool.
- Read Compatible Classes, Witnessed Classes, Unknown Feature Indices in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| observedFeatureFlags | Observed feature flags | array of number | Required; constraints below |
| featureKnownFlags | Feature known flags | array of number | Required; constraints below |
Enter aligned binary observed-feature and known-feature arrays in the exact column order below. The array length must match the fixed rule width. In the rule table, 1 requires presence, 0 requires absence and −1 ignores that column. A known observation contradicting a required value excludes a class; an unknown observation leaves it compatible. A witnessed class requires all nonignored columns to be known and equal to their required values. Unknown-feature indices are zero based and lists preserve rule order. The tool does not annotate grammar, interpret a text or independently verify the historical evidence.
compatible = no known rule contradiction; witnessed = every nonignored rule known and matched Use the field order, units and branch conditions described above.
| Zero-based feature index | Independently annotated feature |
|---|---|
| 0 | independent corroboration witnessed |
| 1 | independent contradiction witnessed |
| 2 | source transmission established |
| Fixed class | Feature 0 | Feature 1 | Feature 2 |
|---|---|---|---|
| corroborated-report-candidate | 1 | -1 | 1 |
| contradicted-report-candidate | -1 | 1 | 1 |
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.compatibleClasses | Fixed-rule classes with no known contradiction; compatibility can depend on unknown features. | array of string |
| result.witnessedClasses | Fixed-rule classes whose nonignored requirements are all known and matched. | array of string |
| result.unknownFeatureIndices | Zero-based indices marked unknown, irrespective of their observed-value placeholders. | array |
{
"input": {
"observedFeatureFlags": [
1,
1,
1
],
"featureKnownFlags": [
1,
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"corroborated-report-candidate",
"contradicted-report-candidate"
],
"witnessedClasses": [
"corroborated-report-candidate",
"contradicted-report-candidate"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
A feature checker records those annotations rather than issuing a universal truth verdict on Herodotus. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use Milvian Bridge in Hoc Signo Two Source Accounts Compare for a related task: Constantinian vision accounts differ in witness, date and narrative form.
Use Tacitus Germania Ethnography Tribes Description Lookup for a related task: Roman ethnography is shaped by its author's literary and political perspective.
References
Similar or alternative tools
- Milvian Bridge in Hoc Signo Two Source Accounts Compare
Constantinian vision accounts differ in witness, date and narrative form.
- Tacitus Germania Ethnography Tribes Description Lookup
Roman ethnography is shaped by its author's literary and political perspective.