Description
Shift a fictional seven-day weekday index by exact integer days.
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.
Shift a fictional seven-day weekday index by exact integer days.
When to use this tool
Use Fictional Date Weekday Offset when you already have baseWeekday, offsetDaysDecimal and need to shift a fictional seven-day weekday index by exact integer days.
How to use the tool and how it works
- Enter baseWeekday, offsetDaysDecimal. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read weekday. Use the output convention below.
Require baseWeekday a whole 0..6; parse optional-sign 1..128-digit decimal offset text with BigInt. Add and reduce modulo seven, correcting negative residues into 0..6.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| baseWeekday | Whole caller-defined weekday index 0..6; the origin is not chosen by the tool. | Required. Safe integer; minimum 0; maximum 6. |
| offsetDaysDecimal | Signed decimal integer text with optional + or - and 1..128 digits; reduced exactly modulo seven. | Required. Text; maximum UTF-16 length 8192. Integer syntax: optional + or - and 1-128 decimal digits; leading zeros accepted. Apply the sign restriction above. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| weekday | Weekday | Required. Safe integer. |
{
"input": {
"baseWeekday": 1,
"offsetDaysDecimal": "10"
},
"output": {
"weekday": 4
}
}Limitations and assumptions
- The weekday origin is caller-defined. Leading zeros are accepted; no date, leap rule, real calendar or different-length fictional week is modeled.
- 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.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
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
- Cosmological Simulation Snapshot Scale Tag
Label a simulation snapshot's supplied scale factor and corresponding redshift.
- Molecular Trajectory Frame Time Label
Map a supplied trajectory frame index to an affine time label.