in Medias Res Opening Classifier
Audit independently established evidence for in Medias Res Opening Classifier. Feature columns, independently annotated in order: opening within ongoing events, earlier causal events narrated later. Unknown evidence and compatible classes retained; not automated semantic, historical, identity, legal or safety determination.
Description
In medias res describes an opening's relationship to an already developing action.
In medias res describes an opening's relationship to an already developing action.1
This checker audits supplied annotations rather than finding a narrative's starting point automatically. Use in Medias Res Opening Classifier to compare independently annotated features with the fixed rules.
When to use in Medias Res Opening Classifier
Use in Medias Res Opening Classifier 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 in Medias Res Opening Classifier 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 | opening within ongoing events |
| 1 | earlier causal events narrated later |
| Fixed class | Feature 0 | Feature 1 |
|---|---|---|
| in-medias-res-candidate | 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
],
"featureKnownFlags": [
1,
1
]
},
"output": {
"result": {
"compatibleClasses": [
"in-medias-res-candidate"
],
"witnessedClasses": [
"in-medias-res-candidate"
],
"unknownFeatureIndices": []
}
}
}Limitations and assumptions
This checker audits supplied annotations rather than finding a narrative's starting point automatically. 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 Muse Invocation Opening Locator for a related task: A Muse invocation must be identified within a text and edition before its position is counted.
Use Ring Composition Circular Return Checker for a related task: Ring composition compares motifs at corresponding outer positions in a text's structure.
References
-
in Medias Res Opening Classifier — tool.io
Similar or alternative tools
- Muse Invocation Opening Locator
A Muse invocation must be identified within a text and edition before its position is counted.
- Ring Composition Circular Return Checker
Ring composition compares motifs at corresponding outer positions in a text's structure.