🕰️ Aeon Architecture Index – 4 + 1 Series

Aeon orchestrates temporal logic across the WhittakerTech ecosystem.
Each subsystem below defines its own 4 + 1 architecture — focusing on one facet of time: persistence, recurrence, caching, mutation, or orchestration.

---

📚 Table of Contents

File	Title	Summary
AEON_PERIOD.md	Period & Time Arithmetic	Core math layer — defines shift, grow, scale, and period operators.
AEON_TIMESTAMP.md	Timestamps & Persistence	Polymorphic schedule persistence for host models.
AEON_RECURRENCE.md	Recurrence Adapter	Bridges Aeon JSON rules and IceCube schedules.
AEON_TIMEKEEPER.md	Querying & Temporal DSL	Public API for querying events and ranges.
AEON_CACHEWINDOW.md	Cache Windows	Expands query ranges with temporal buffers.
AEON_CACHEMANAGER.md	Cache Management	Handles Redis storage, memoization, and invalidation.
AEON_CACHEINVALIDATION.md	Cache Invalidation Rules	Refreshes caches when timestamps mutate.
AEON_REFRESHER.md	Dynamic Refresh Service	Periodic background prewarming and recalculation.
AEON_MUTATOR.md	Mutation Semantics	Defines “Change This / All / Future” behaviors.
AEON_DEEPCLONE.md	Deep Cloning Service	Clones timestamps and attached records safely.
AEON_EXCEPTIONMANAGER.md	Recurrence Exceptions	Handles inclusion/exclusion rules for recurring events.
AEON_SCHEDULABLE.md	Model Concern & DSL	Adds has_one_schedule :symbol for host models.
AEON_WORKER.md	Legacy Worker Bridge	Sidekiq/Redis orchestration compatibility.
AEON_INTEGRATION_NOTES.md	Integration Surfaces	Defines Aeon’s adapter contracts and engine I/O sockets.

---

🧩 Aeon Layer Map

graph TD
  subgraph Model Layer
    A1[Aeon::Period]
    A2[Aeon::Timestamp]
    A3[Aeon::RecurrenceAdapter]
  end
  subgraph Query Layer
    B1[Aeon::PeriodQuery]
    B2[Aeon::Timekeeper]
  end
  subgraph Cache Layer
    C1[Aeon::CacheWindow]
    C2[Aeon::CacheManager]
    C3[Aeon::CacheInvalidation]
    C4[Aeon::Refresher]
  end
  subgraph Mutation Layer
    D1[Aeon::Mutator]
    D2[Aeon::DeepCloneService]
    D3[Aeon::ExceptionManager]
  end
  subgraph Integration Layer
    E1[Aeon::Schedulable]
    E2[Aeon::Worker]
    E3[Aeon::IntegrationSurfaces]
  end
  A1 --> B1
  A2 --> B2
  B2 --> C1
  C1 --> C2
  C2 --> C3
  C3 --> C4
  C4 --> D1
  D1 --> D2
  D2 --> D3
  D3 --> E1
  E1 --> E2
  E2 --> E3

---

🧠 Development Guidelines

1. Isolation:
   Each component’s 4 + 1 doc should stand alone and integrate through defined adapters.
2. Consistency:
   Every document includes:
3. Logical View
4. Process View
5. Development View
6. Physical View
7. Scenarios (+ Security & Observability if relevant)
8. Language:
   Concise technical English with Aeon’s humanistic tone — calm, timeless, and precise.
9. Schema Fragments:
   Use minimal code fences for model and service definitions.
10. Cross-References:
    Use explicit links between 4 + 1 docs to illustrate engine interaction.
11. Integration Philosophy:
    Aeon exposes interfaces, not dependencies — metrics, validation, and jobs are optional adapters injected via configuration.

---

🪞 Author’s Note

Aeon began as a clock.
It became a calendar.
Now it keeps the rhythm of creation —
a quiet pulse beneath every WhittakerTech system.

— WhittakerTech Temporal Systems Architecture Team

---