Skip to content

Main content

Fictional Calendar Leap Rule Step Tool

Apply a caller-defined Gregorian-shaped divisibility rule to astronomical integer years, without assuming a fictional calendar epoch.

Loading tool…

Description

Apply a caller-defined fictional leap-year divisibility rule.

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.

Apply a caller-defined fictional leap-year divisibility rule.

When to use this tool

Use Fictional Calendar Leap Rule Step when checking a supplied story-continuity, chronology, calendar or drafting-budget convention.

How to use the tool and how it works

  1. Enter year, divisibleBy, exceptDivisibleBy, restoreDivisibleBy. 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 leap. Inspect leap before interpreting the associated values.

Apply a caller-defined fictional leap-year divisibility rule. Require positive whole divisors with exception divisible by base and restoration divisible by exception; leap follows base AND (not exception OR restoration).1

Input fieldMeaning and unitsAccepted input
yearYearRequired. Safe integer.
divisibleByDivisible ByRequired. Safe integer; minimum 1.
exceptDivisibleByExcept Divisible ByRequired. Safe integer; minimum 1.
restoreDivisibleByRestore Divisible ByRequired. Safe integer; minimum 1.
Output fieldInterpretationReturned shape
leapLeapRequired. Boolean.
json
{
  "input": {
    "year": 2000,
    "divisibleBy": 4,
    "exceptDivisibleBy": 100,
    "restoreDivisibleBy": 400
  },
  "output": {
    "leap": true
  }
}

Limitations and assumptions

  • The year coordinate and rule are supplied; no real historical calendar or date is validated.
  • 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

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/fictional-calendar-leap-rule-step — tool.io

Similar or alternative tools