Description
Preserve an invented date and its supplied uncertainty wording.
Writing records can represent speakers, scenes, aliases, rhyme labels and revision spans. These representations preserve selected conventions: a character count needs an indexing unit, an alias can be active over an inclusive period, and a stage-direction wrapper is a string pattern rather than a grammar. Mechanical labels do not evaluate literary quality or establish authorship.
Preserve an invented date and its supplied uncertainty wording.
When to use this tool
Use Fictional Date Uncertainty Label when you already have sceneId, dateText, uncertaintyText and need to preserve an invented date and its supplied uncertainty wording.
How to use the tool and how it works
- Enter sceneId, dateText, uncertaintyText. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter sceneId, dateText, uncertaintyText using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| sceneId | Scene Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| dateText | Date Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| uncertaintyText | Uncertainty Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"sceneId": "S17",
"dateText": "third frost",
"uncertaintyText": "approximate"
},
"output": {
"token": "[\"S17\",\"third frost\",\"approximate\"]"
}
}Limitations and assumptions
- The result records supplied values without applying a real-world calendar. Sources and asserted relationships are not independently authenticated.
- 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
Inspect the full passage, draft history and editorial style when interpreting the result. Use complete text or narrative analysis for meaning and structure; local markers, offsets and supplied attribution records only organize the stated information.
References
Similar or alternative tools
- Scene Goal Outcome Tag
Record a scene goal and its explicitly supplied outcome code.
- Fictional Date Weekday Offset
Shift a fictional seven-day weekday index by exact integer days.