The Stack
Five layers, one thesis.
Each layer builds on the one below it. The time model makes the availability engine possible. The availability engine makes coordination possible. The coordination layer makes the suite possible. The suite makes the network accessible.
Time Model
The Rheba date-time library
Intent-preserving time encoding. No epoch seconds, no timezone drift. The foundation everything else is built on.
Research
The Case Against Unix Time
Why modern scheduling software still models human time wrong, and what a better foundation looks like.
SDK Direction
Build surfaces and API
105 API endpoints. The availability engine, group coordination, and temporal infrastructure — being prepared for external access.
Coordination Layer
Rheba Core
Where groups, identity, availability, and coordination converge. The system the suite feeds.
Applications
The app suite
10 free tools that exercise the SDK. Working examples of what can be built on the shared architecture.
Start anywhere. The layers connect.
Whether you start with the time model, the API, the suite, or the research — each path leads into the same system.