<aside> <img src="/icons/reorder_gray.svg" alt="/icons/reorder_gray.svg" width="40px" />
Navigation
</aside>
Worldlines and Spacetime Topology
Sign Up for Early Access: https://docs.google.com/forms/d/e/1FAIpQLSd5WkVDKyDVKDPjNosGChn8CH7C9KJ-5ad6hhyHNzkzFOvfEQ/viewform?usp=sf_link
Socials: X, Discord, IG, YouTube
Contact Us: [email protected]
As Circaevum is a tool to highlight natural cycles, this is a place to consider a framework for a somewhat automated, cyclical software development process.
Okay, main approach is to come up with a very high-level plan for each development cycle. For now, we will structure this as 1 year. In this year, we will define overarching goals that we want to achieve. The goal for 2024 has been to develop a version of Circaevum for the Apple Vision Pro, and that is nearing completion.
Some high-levels goals for 2025 would be:
The general plan is to align these developments with the seasons as follows:
Activities:
Outcome: A comprehensive project roadmap and a prepared team, ready to embark on development.
Activities:
Outcome: Significant advancement in project development, with core functionalities progressing steadily.
Activities:
Outcome: A polished product, thoroughly tested and well-documented, ready for deployment.
Activities:
Outcome: A rejuvenated team with valuable insights, ready to plan for the upcoming year.
Given this approach, I’m currently in the Wrapping-Up phase of the Apple Vision Pro build. I should have deployed it by now, but here we are. I give myself until the end of the year to wrap it up, and will spend the remainder of Winter sharing it, getting some users, and assembling a team for the 2025 cycle. If I can squeeze in the deployment of it for the MIT VR Hackathon in January, perfect!