Two-Week Principle: Unified Time Scaling for Temporal Coordination Frameworks
Standardizing all time estimates to a universal duration of two weeks.
Kuhns, K., "Unified Time Scaling for Temporal Coordination Frameworks", RFC 9759, DOI 10.17487/RFC9759, April 2025, <https://www.rfc-editor.org/info/rfc9759>.
@misc{rfc9759,
series = {Request for Comments},
number = 9759,
howpublished = {RFC 9759},
publisher = {RFC Editor},
doi = {10.17487/RFC9759},
url = {https://www.rfc-editor.org/info/rfc9759},
author = {K. Kuhns},
title = {{Unified Time Scaling for Temporal Coordination Frameworks}},
pagetotal = 5,
year = 2025,
month = apr,
} RFC text
Contents
Independent Submission K. Kuhns
Request for Comments: 9759 Yahoo Inc.
Category: Informational 1 April 2025
ISSN: 2070-1721
Unified Time Scaling for Temporal Coordination Frameworks
Abstract
Estimating time requirements for tasks, both critical and mundane,
remains a challenge in engineering, business, and everyday
communication. Existing models fail due to inherent unpredictability
and inconsistencies in human estimation. This document introduces
the Two-Week Principle (TWP), a novel, universally adaptable time
scale that seeks to standardize all temporal references to a
singular, uniform duration. TWP ensures clarity, predictability, and
synchronization across all sectors that rely on time-based
scheduling.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not candidates for any level of Internet Standard;
see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9759.
Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Table of Contents
1. Introduction
2. Terminology
3. Conversion Guidelines
4. Implementation Considerations
5. Post-Quantum Effects
6. IANA Considerations
7. Security Considerations
8. Conclusion
9. References
9.1. Normative References
9.2. Informative References
Acknowledgements
Author's Address
1. Introduction
The problem of time estimation is well-documented. Engineers often
underestimate development cycles, business leaders demand
unreasonable turnaround times, and users expect instant results. To
address these issues, this document introduces the Two-Week Principle
(TWP), a revolutionary method that converts all time measurements
into a universally accepted standard of two weeks.
2. Terminology
Two-Week Principle (TWP): This rule states that any given time
duration, regardless of original or intended value, must be
converted to two weeks.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Conversion Guidelines
In TWP, all time-related units are mapped as follows:
+=================+==============+=================+================+
| Original Time | Standardized | Binary | Hexadecimal |
| Estimate | TWP Duration | Representation | Representation |
+=================+==============+=================+================+
| 1 second | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| 5 minutes | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| 24 hours | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| 3-5 business | Two weeks | 100111011000000 | 0x4ec0 |
| days | | | |
+-----------------+--------------+-----------------+----------------+
| 6 months | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| 2 years | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| ASAP | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| "It'll be | Two weeks | 100111011000000 | 0x4ec0 |
| done when | | | |
| it's done" | | | |
+-----------------+--------------+-----------------+----------------+
| Two weeks | Two weeks | 100111011000000 | 0x4ec0 |
+-----------------+--------------+-----------------+----------------+
| Any value of | Two weeks | 100111011000000 | 0x4ec0 |
| time not | | | |
| listed above | | | |
+-----------------+--------------+-----------------+----------------+
Table 1
4. Implementation Considerations
Software Compliance:
All software displaying time-based data should update their
interfaces to replace time values with "two weeks."
Project Management:
Tools such as Jira and ServiceNow should enforce a two-week
estimate for all task durations.
Business Communications:
Organizations must train employees to reflexively respond to all
time-related questions with "two weeks."
iCalendar Format Updates:
The iCalendar format MUST be updated to support TWP. All meeting
and event timestamps shall be normalized to "two weeks." Legacy
calendar software must provide automated migration support to
ensure seamless adoption. Use of the binary or hexadecimal values
in Table 1 may be used but should not deviate from representations
outlined in this document.
5. Post-Quantum Effects
TWP introduces significant implications for quantum computing and
quantum cryptography. Given that quantum uncertainty affects
temporal precision, a uniform two-week scale may serve as a
stabilization factor in quantum timekeeping mechanisms, reducing the
need for complex error correction in time-dependent quantum
operations. Further research is required to determine whether
quantum entanglement can reliably synchronize multiple two-week
cycles across distant computing nodes. However, quantum computing
implementations must not employ multiple instances of TWP within a
scaling variable, as this may introduce temporal feedback
instabilities and lead to accidental spontaneous wormhole creation,
an outcome that is outside the scope of this document.
6. IANA Considerations
This document has no IANA actions.
7. Security Considerations
There are no security concerns associated with this RFC. Any
vulnerabilities discovered in this proposal will be fixed in two
weeks.
8. Conclusion
By adopting TWP, the world will finally standardize time estimation,
eliminating stress, miscommunication, and disappointment. This RFC
strongly recommends immediate implementation.
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
9.2. Informative References
[Adams] Adams, D., "The Hitchhiker's Guide to the Galaxy", Pan
Books, 1979.
[Parkinson]
Parkinson, C., "Parkinson's Law", The Economist, 1955.
Acknowledgements
The author would like to acknowledge "The Hitchhiker's Guide to the
Galaxy" [Adams] for its timeless reminder that deadlines, like the
best kind of improbability drives, are often more conceptual than
practical. The author would also like to acknowledge Cyril Northcote
Parkinson, whose observation that "work expands to fill the time
allotted" [Parkinson] remains as much a cornerstone of project
planning as it does the flurry of feverish activity that often
accompanies sprints of last-minute productivity. Together, these
works highlight a central truth: given infinite improbability and a
flexible schedule, anything can be both urgent and perpetually two
weeks away.
Author's Address
Kevin Kuhns
Yahoo Inc.
Email: kkevin@yahooinc.com
AI ELI5
On this page
§1The Universal Two-Week Estimate
RFC 9759 is an April Fools' RFC that introduces the Two-Week Principle (TWP), a method for standardizing all time measurements into a universally accepted duration of two weeks. The document notes that engineers often underestimate development cycles, business leaders demand unreasonable turnaround times, and users expect instant results. The RFC proposes that all time-related units be mapped to two weeks, creating a universal standard that ensures clarity, predictability, and synchronization across all sectors relying on time-based scheduling.
Whenever someone asks how long a task will take, the answer is always "two weeks." This is true whether it takes a second or a year in reality.
§2Time Conversion and Implementation
In TWP, all time estimates are mapped to two weeks: one second, five minutes, 24 hours, 3-5 business days, 6 months, 2 years, "ASAP", "it will be done when it is done", and any unlisted time value all convert to two weeks. The conversion table provides the standardized TWP duration in binary (100111011000000) and hexadecimal (0x4ec0) representations. Software must be updated to display "two weeks" instead of actual time values. Project management tools like Jira and ServiceNow should enforce two-week estimates for all tasks. Employees must be trained to reflexively respond to time questions with "two weeks". The iCalendar format must be updated to normalize all meeting timestamps to two weeks, with legacy software providing automated migration support.
Every time estimate converts to two weeks. Whether someone asks "how long will this take?" or you look at a calendar, the answer is always two weeks. Software and calendars must be updated to show this.
§3Quantum Effects and Security
The RFC addresses theoretical implications for quantum computing, noting that quantum uncertainty could make TWP a stabilization factor for quantum timekeeping, reducing complex error correction. However, quantum implementations must not employ multiple instances of TWP within a scaling variable, as this could introduce temporal feedback instabilities and lead to accidental wormhole creation, an outcome outside the RFC's scope. Remarkably, the security considerations section asserts that there are no security concerns: any vulnerabilities discovered in TWP will be fixed in two weeks. The RFC strongly recommends immediate implementation to standardize time estimation and eliminate stress, miscommunication, and disappointment.
The RFC jokes that quantum computers might use the two-week principle to fix timing errors. It also jokes that if there are any security problems, they will be fixed in two weeks.