Skip to content

Main content

Viewpoint Tense Marked Token Conflict Tool

Audit explicitly annotated person/tense tokens with per-token exemptions; this does not perform natural-language parsing.

Loading tool…

Description

Locate nonexempt viewpoint or tense-label conflicts.

Story planning separates the order of telling from fictional chronology, continuity records and practical writing budgets. Explicit labels, counts and invented calendar rules can make a local convention consistent without deciding narrative quality or inferring facts from manuscript prose.

Locate nonexempt viewpoint or tense-label conflicts.

When to use this tool

Use Viewpoint Tense Marked Token Conflict when checking a supplied story-continuity, chronology, calendar or drafting-budget convention.

How to use the tool and how it works

  1. Enter expectedPerson, expectedTense, markedPersons, markedTenses, exempt. Keep parallel arrays aligned. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read conflictIndexes. Use the output convention below.

Locate nonexempt viewpoint or tense-label conflicts. Require aligned markedPersons/markedTenses/exempt; return zero-based indexes whose nonexempt labels differ from expectedPerson or expectedTense.1

Input fieldMeaning and unitsAccepted input
expectedPersonExpected PersonRequired. Text; maximum UTF-16 length 8192.
expectedTenseExpected TenseRequired. Text; maximum UTF-16 length 8192.
markedPersonsMarked PersonsRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
markedTensesMarked TensesRequired. Array of text; maximum UTF-16 length 8192; maximum items 256.
exemptExemptRequired. Array of boolean; maximum items 256.
Output fieldInterpretationReturned shape
conflictIndexesConflict IndexesRequired. Array of safe integer; maximum items 256.
json
{
  "input": {
    "expectedPerson": "third",
    "expectedTense": "past",
    "markedPersons": [
      "third",
      "first"
    ],
    "markedTenses": [
      "past",
      "past"
    ],
    "exempt": [
      false,
      false
    ]
  },
  "output": {
    "conflictIndexes": [
      1
    ]
  }
}

Limitations and assumptions

  • Labels are supplied; no prose, grammar, narration strategy or permissible tense shift is analyzed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.

Alternative or Complementary methods

Use the manuscript, scene outline and the chosen style/calendar policy for a complete editorial review; interpret numerical budgets in their narrative context.

References

  1. Calculation and input contract: creative-writing/viewpoint-tense-marked-token-conflict — tool.io

Similar or alternative tools