Digital Twin

ReclamationDay.net is the digital twin of Project Quantum Leap.

It is not simply a website about the physical artifact.

Both systems represent the same transition through time. The physical artifact makes that transition tangible through light, display, and interaction. The digital twin gives the same system room for narrative, documentation, operational milestones, and an archive that can continue growing long after the countdown ends.

The digital twin is built around one central principle:

Time determines state. State determines behavior.

01 // One Journey, Different Expressions

The physical artifact and digital twin do not need identical interfaces.

They have different jobs.

The physical artifact should communicate the current state quickly through:

• time
• light
• status
• physical presence

The digital twin can communicate much more:

• the public Journey
• current system status
• countdown information
• Mission Events
• Field Notes
• project documentation
• progressively unlocked sections
• the story behind each state
• Time Reclaimed

The two systems should share meaning without being forced to share presentation.

02 // Journey State

Journey State represents durable progress through the major milestones of the transition.

The public Journey intentionally contains only five milestones:

1. Final Year
2. Retirement Window
3. Totality
4. Twenty Years
5. Reclamation Day

These are the large narrative markers that remain meaningful when viewed as a complete story.

Journey State is determined by the most recent fixed milestone that has been reached.

It does not change merely because the visual presentation enters a temporary state between milestones.

This distinction became important as the system evolved.

For example, Returning Light begins after Totality, but the Journey remains in the Totality chapter until Twenty Years is reached.

That allows the presentation to evolve without rewriting the underlying Journey.

03 // Display State

Display State determines what the system should feel like right now.

It controls:

• system status
• phase
• narrative
• visual theme
• countdown context

Display State can come from a fixed Journey milestone or from a derived state between milestones.

The current sequence is:

Phase	Display State
0	Standby
1	Final Year
2	Retirement Window
3	Approaching Totality
4	Totality
5	Returning Light
6	Twenty Years
7	Reclamation Day
99	The Future Is Bright

This allows Project Quantum Leap to express a continuous transition without turning every visual change into another public milestone.

04 // Derived States

Some of the most important transitions happen between Journey milestones.

These are modeled as derived states.

Approaching Totality

Beginning 03 FEB 2027, ninety days remain before Totality.

The system enters Phase 3.

The presentation becomes more restrained as the final operational threshold approaches.

Journey State remains linked to the Retirement Window chapter.

Returning Light

Beginning 05 MAY 2027, the final day in uniform has passed.

The system enters Phase 5.

Warmth begins returning to the visual language while the transition continues through SkillBridge and Terminal Leave.

Journey State remains linked to Totality until Twenty Years is reached.

Derived states therefore change the experience of the system without creating false milestones in the Journey.

05 // Mission Events

The public Journey answers:

Where am I in the larger story?

Mission Events answer:

What requires attention during this chapter?

They represent operational transition activity such as:

• retirement processing
• TAP activity
• SkillBridge
• Capstone
• Final Out
• Terminal Leave
• final retirement processing

Mission Events are linked to Journey chapters rather than directly to Display State.

That distinction prevents temporary visual states from disrupting operational information.

For example, Returning Light can change the appearance and system status while SkillBridge and Terminal Leave remain correctly associated with the Totality chapter.

Mission Events can communicate conditions such as:

NEXT

ACTIVE

TARGET

CHAPTER COMPLETE

This keeps operational detail available without turning the public Journey into a project-management chart.

06 // Unlock State

ReclamationDay.net is designed to reveal itself over time.

Not every section needs to exist publicly from the beginning.

Unlock State uses the resolved phase to determine which content destinations are available.

The current progression is:

Phase	Content Available
0	Field Notes
1	Project Quantum Leap
2	Reclamation Log
6	Twenty Years
7	Reclamation Day
99	The Future Is Bright

This means the website itself participates in the countdown.

As milestones are reached, the archive becomes larger.

The visitor does not merely read about progress.

The structure of the site changes because progress occurred.

07 // Field Notes

Field Notes provide the flexible record between the larger milestones.

They can document:

• experiments
• discoveries
• side quests
• project decisions
• artifacts
• places
• observations
• changes in direction

Field Notes do not need to become Journey milestones or permanent navigation sections.

They are the working record of the journey ahead.

This gives the site room for small stories without allowing those stories to overwhelm the larger architecture.

08 // Data Before Presentation

The timeline and its meaning should live in structured data wherever practical.

The current Hugo architecture separates important definitions into data files rather than embedding every date and state directly into templates.

The model includes:

MILESTONES
Fixed Journey milestones and the persistent final state.

DERIVED STATES
Time-bound presentation states between fixed milestones.

MISSION EVENTS
Operational transition activity linked to Journey chapters.

UNLOCKS
Content availability associated with system phases.

Templates render the interface.

JavaScript resolves the current state.

CSS expresses that state visually.

This separation makes the system easier to reason about and reduces the chance that presentation code quietly becomes the authoritative timeline.

09 // Theme Engine

Display State selects a semantic visual theme.

The current theme sequence is:

QUANTUM

FIRST LIGHT

APPROACHING TOTALITY

TOTALITY

RETURNING LIGHT

SUNRISE

DAYLIGHT

The themes use semantic CSS variables rather than requiring each component to know specific colors.

Components can ask for concepts such as:

• primary
• secondary
• heritage
• text
• muted
• line
• surface
• glow
• focus

The theme decides what those concepts look like.

This allows the entire site to move through the eclipse progression without rebuilding individual components for every phase.

10 // Local Date Simulator

A countdown that cannot be tested in the future is difficult to trust.

The local development environment therefore supports simulated dates through the URL.

For example:

?date=2027-05-04

allows the site to behave as though the calendar has reached Totality.

The simulator preserves the current time of day while replacing the calendar date.

It is restricted to local development.

This makes it possible to test:

• milestone boundaries
• derived states
• Mission Events
• theme changes
• content unlocks
• Reclamation Day
• the persistent future state

without changing the computer’s system clock or editing authoritative timeline data.

The simulator is a development tool, not part of the public narrative.

11 // Reclamation Day

01 NOV 2027 receives special treatment.

For the entire calendar day, the digital twin remains in Phase 7.

The system reports:

MISSION COMPLETE

RECLAMATION COMPLETE

The countdown displays:

000 DAYS / 00 HRS / 00 MIN / 00 SEC

All five Journey milestones are complete.

Mission Events disappear.

The Reclamation Day archive becomes available.

The system does not immediately skip past the objective simply because the clock has crossed midnight at the beginning of the day.

Reclamation Day gets its full day.

12 // Time Reclaimed

Beginning 02 NOV 2027, the digital twin enters Phase 99.

There is no next Journey milestone.

There is no new countdown.

The primary instrument becomes:

TIME RECLAIMED

The persistent display uses:

YEARS / DAYS / HRS / MIN

The calculation remains anchored to 01 NOV 2027.

The site also unlocks its final destination:

The Future Is Bright.

This is the point where the architecture changes from a countdown system into a persistent archive.

The website has reached its destination without reaching its end.

13 // Digital and Physical Truth

The digital twin currently contains the more mature implementation of the Project Quantum Leap state model.

That should not make the website the permanent source of truth for the physical artifact.

The long-term objective is a shared authoritative specification from which both systems can derive the information they need.

That specification should define concepts such as:

• milestone identifiers
• milestone dates
• phase numbers
• derived-state boundaries
• state names
• theme identities
• Reclamation Day behavior
• Time Reclaimed behavior

The physical firmware and the website can then implement those rules in ways appropriate to their own environments.

The goal is not identical code.

The goal is identical truth.

14 // Design Principle

Project Quantum Leap deliberately separates meaning from presentation.

Journey State answers where the transition stands.

Display State answers how the current moment should be expressed.

Mission Events answer what requires attention.

Unlock State answers what the archive is ready to reveal.

The theme engine determines how that state should look.

The physical artifact will eventually translate the same meaning into light, display, and interaction.

Different interfaces.

Different capabilities.

One timeline.

One state model.

One Reclamation Day.

The digital twin does not imitate the artifact.

They tell the same story.