Skip to content

Main content

Founder Buyback Deadline Gap Tool

Supplied deadline/pause arithmetic only; no contractual enforceability or notice rule is selected.

Loading tool…

Description

Compare a submission with a supplied notice, deadline and total paused-day convention.

A contractual time budget requires a notice origin, elapsed-time unit and explicit pause convention. Numeric day arithmetic can reconcile supplied coordinates without establishing the actual deadline or legally effective notice.

Compare a submission with a supplied notice, deadline and total paused-day convention.

When to use this tool

Use Founder Buyback Deadline Gap when checking a declared active-time or deadline-offset convention.

How to use the tool and how it works

  1. Enter noticeDay, deadlineDay, submittedDay, pauseDays. 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 elapsedActive, margin. Use the output convention below.

Require nonnegative whole pauseDays, deadlineDay >= noticeDay and submittedDay >= noticeDay+pauseDays. elapsedActive = submittedDay-noticeDay-pauseDays; margin = deadlineDay-submittedDay+pauseDays. Use matching numeric day coordinates.1

Input fieldMeaning and unitsAccepted input
noticeDayNotice DayRequired. Safe integer.
deadlineDayDeadline DayRequired. Safe integer.
submittedDaySubmitted DayRequired. Safe integer.
pauseDaysNonnegative whole paused days, deducted from active elapsed time and added to deadline margin.Required. Safe integer; minimum 0.
Output fieldInterpretationReturned shape
elapsedActiveElapsed ActiveRequired. Safe integer.
marginMarginRequired. Safe integer.
json
{
  "input": {
    "noticeDay": 100,
    "deadlineDay": 130,
    "submittedDay": 125,
    "pauseDays": 5
  },
  "output": {
    "elapsedActive": 20,
    "margin": 10
  }
}

Limitations and assumptions

  • This treats pauses as extending the available interval by their supplied total. No calendar, business-day rule, notice validity or contractual deadline is independently determined.
  • 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 applicable calendar and agreement to establish notice, pauses and deadline rules before interpreting an offset.

References

  1. Calculation and input contract: entrepreneurship-studies/founder-buyback-deadline-gap — tool.io

Similar or alternative tools