Kolovrat Archaic Rhythm System

Linear calendars assume every week of the year is the same. They aren't — not biologically, not strategically, not operationally. Kolovrat Zhyttia replaces the January-to-December grid with a cyclical operating system: solar year anchored to the winter solstice, twelve lunar stages plus Tysha (silence), four archetypal phases, all rendered as a navigable 3D orbit.

The problem it solves

Linear calendars assume time is a neutral container and that constant productivity is virtue. Biology disagrees: serotonin, cortisol, and melatonin shift with photoperiod, so a person in December is physiologically not the same person in June. Strategists know it too — scaling in a consolidation quarter destroys the business the previous quarter just built; pushing expansion through a Harvest month wastes the capital that should be banked. But the tools used to plan a year (Google Calendar, Notion, Asana) are flat grids that treat December and June as interchangeable and reduce the year's actual structure — its phases, peaks, and required pauses — to invisible noise.

The cost is concrete. Operators burn out trying to maintain June-level intensity in December and call it discipline. Founders push expansion when the cycle calls for harvest and lose six to nine months of compounding to retroactive cleanup. Retreat programs teach this rhythm over five intensive days and watch participants drift back to linear thinking inside thirty when they return to a calendar that doesn't model it. Kolovrat Zhyttia exists because the underlying doctrine is well-developed but had no daily-use software surface — nothing that holds the cycle between retreats and translates it into a planning interface a participant actually opens every morning.

Who needs this most

• Founders and operators who participated in a Totem Architect retreat (Level I: Totem Initiation or Level II: Architecture of Power) and need a tool that keeps the cyclical doctrine alive between sessions — the moment it hurts is the Monday after the retreat ends, when last week's clarity meets a flat Google Calendar and a Slack queue.
• Entrepreneurs and strategists running 12-to-36-month strategic horizons who already think in seasons (sow, build, harvest, integrate) and feel the friction of a linear calendar overriding that judgment — the moment it hurts is quarterly review, when the calendar says "behind on growth" and the cycle says "this quarter was supposed to consolidate."
• Retreat program operators and small coaching practices running cycle-aware methodologies (Slavic, Jungian, ritual-anchored, somatic) for communities of 50 to 500 verified members — the moment it hurts is the 30-day follow-up call when the operator discovers the participant returned to linear thinking by week two.

The solution — in plain terms

Kolovrat Zhyttia presents the year as a living orbit, not a list. The 365 days of a solar year are drawn as a 3D path around a central gravitational ball; lunar cycles ripple as a sinusoidal wave along that orbit; the four solar points — winter solstice, spring equinox, summer solstice, autumn equinox — anchor the four archetypal seasons of action: Farmer, Warrior, Emperor, Sage. A sun marker shows today. A moon marker shows the current phase. The user navigates by rotating the orbit, zooming into a single lunar cycle, or stepping forward into next quarter's archetypal phase.

Beneath the visualization is a structured planning surface. Each of the twelve lunar stages — Formation, Strategy, Launch, Breakthrough, Growth, Power, Expansion, Consolidation, Harvest, Affirmation, Securing, Experience — carries its own intention, vectors, resources, and goals. Tysha (Silence) is a floating transitional period the user defines themselves, not a fixed calendar date; it follows the body and the year, not the spreadsheet. Events can be pinned to specific dates, to a moon-day relative to the lunar cycle, or to a fuzzy zone the user nudges into position. A God Architect admin role manages community-wide events, retreat announcements, and verification of Totem Architect program graduates.

The software keeps a long memory. Past cycles dim into a spiral below the current orbit; future cycles fade upward. The Mission Axis — the year's central intention — runs as a vertical spine through all of them, so a single multi-year arc is visible in one view. The doctrine learned at the retreat becomes a daily visual structure, not a notebook the participant rereads twice and forgets.

Value delivered — what you get

• Replaces the linear calendar with a cycle-aware planning surface — the year is structured by solstices, equinoxes, and lunar new moons; the tool refuses to pretend that December and June are the same kind of week.
• Holds retreat doctrine between programs — the 30-day follow-up stops depending on the participant's personal discipline; the app opens to a cycle that's already drawn, with the stage and phase named in the user's language.
• Removes the planning ambiguity around archetypal phases — every lunar stage carries its own intention, vector, resource budget, and goal list, so the operator stops guessing whether this is a Strategy month or a Harvest month.
• Collapses three to five SaaS subscriptions into one self-hosted surface — calendar, journal, retreat content viewer, community notifications, and goal tracker live in a single Docker stack on the operator's own VPS.
• Runs with no external dependencies in the critical path — ten years of pre-computed astronomical data (2025–2035) ship inside the container; no API keys, no usage caps, no third-party SaaS to break the cycle when a vendor changes its terms.
• Bilingual stage naming (English / Ukrainian) end-to-end — Slavic archaic terminology (Становлення, Стратегія, Запуск, Тиша) sits alongside translated equivalents, so the cultural roots stay legible without locking out non-Ukrainian participants.

Where it delivers outsized value

• Retreat-led personal development programs — programs where the methodology is cyclical (Slavic, Jungian, ritual-anchored, somatic) but participants return to linear tooling after each session and erode the work between retreats.
• Solo founders and small leadership teams running multi-year strategic horizons — operators for whom the difference between a Power quarter and a Harvest quarter is a real operational choice with money attached, not a metaphor.
• Community-led practitioner ecosystems of 50–500 verified members — small communities where one admin needs to push retreat announcements, gate course content by participation level, and see an aggregate position of the community across the cycle without paying for a full LMS or community platform.

Distinctive features — why this over the alternatives

• 3D orbital visualization with spiral memory — the year is drawn as a navigable orbit, with past and future cycles dimmed as spirals above and below; the user perceives their position in a multi-year arc, not just this month.
• Pre-scraped 10-year astronomical data inside the container — moon phases, solstices, and equinoxes for 2025–2035 ship as static JSON; no runtime API calls, no quota risk, no failure mode when the network drops.
• User-defined Tysha (Silence) boundaries — the silent transitional period between cycles isn't a fixed calendar date; the user sets when their own Tysha begins and ends, mirroring how Slavic time-keeping actually worked.
• Archetype-driven UI theming from a user-uploaded image — palette extraction from a single archetype image drives particle colors, orbit glow, and accent tones across the whole app, so the user's personal symbol becomes the visual language of their workspace.
• Two-tier program-graduate verification — the God Architect admin role approves or rejects each user's claimed Totem Architect level (Level I or Level II), gating ecosystem content accordingly without forcing the operator into a public access-control product.
• Notion-style non-annoying notifications — moon phase transitions, phase changes, and admin announcements arrive as a corner-dot or quiet toast, never a push popup; the app refuses to behave like a productivity surface that interrupts the user.

Under the hood — built to last

The platform runs on Next.js 14, React 18, and TypeScript 5.6 on the application side, with PostgreSQL 16 behind Prisma 5.22 as the system of record — proven, well-supported components that will still be standard in five years. The 3D orbit is rendered with Three.js r169 via @react-three/fiber, code-split out of the main bundle so first paint stays light even on a phone. The whole stack ships as a Docker Compose service: one app container, one Postgres container, an Nginx reverse proxy in front. No SaaS lives in the critical path — astronomy data is bundled, authentication runs locally via NextAuth.js v5, uploads stay on a mounted volume. A community of 100–500 active members runs comfortably on a single small VPS.

Current maturity

Kolovrat Zhyttia is feature-complete across its core surfaces. Orbit view, lunar cycle view, phase view, journal, goals, events, profile, ecosystem, admin panel, notifications, calendar, and bilingual settings are all implemented end-to-end. The codebase is roughly 14,300 lines of TypeScript across 47 React components and 31 API routes; the Prisma schema covers thirteen models with full relations; ten years of astronomical data is pre-computed and bundled with the container. Initial database migration landed 2026-03-11; the most recent migration (user-configurable timezone) landed 2026-03-18. The current focus is operational hardening — completing the timezone refactor across the moon views, finalizing pre-launch polish, and pairing the first retreat cohort to the platform. The software was built end-to-end before being put in front of paying users; the retreat program it accompanies is the channel that opens the user base.

Roadmap — what's next

The next milestone is paired with the first Totem Architect retreat cohort to use the platform end-to-end: participants register, get verified into Level I, live their 60-day post-retreat integration inside the orbit, and feed back the friction points. From there the roadmap splits along two business tracks. The community-tenancy track adds mentor/guide roles (a middle tier between God Architect and regular user), in-app course content viewers gated by Totem Level, and event RSVP for retreat applications — each unlocking a new revenue line for the program operator. The platform-extension track opens reflection questionnaires at phase transitions, opt-in browser push notifications, and fractal zoom from year down to day, expanding the surface for standalone operators who never plan to attend a retreat.

The longer arc is a Level III tier (System Architect) and a multi-year mega-cycle view — three, seven, and twelve-year spirals built on the existing SpiralLayers 3D component — positioning Kolovrat Zhyttia as a life-long operating surface rather than a one-year planner.

Working with the architect

Kolovrat Zhyttia is available in three engagement modes. A retreat-program operator can commission a custom build modeled on the Kolovrat methodology, branded to their own program with their own cycle language and archetypal vocabulary. A coaching practice or distributed leadership team can take ecosystem tenancy — a verified instance, hosted by the architect, that runs the community inside the existing platform with their own ecosystem items, verification flow, and gated content. A leader running an equivalent cycle-aware methodology can engage in strategic advisory on the underlying doctrine: how to translate a retreat curriculum into a daily-use software surface that holds the work between sessions. Reach out via sintegrium.io or LinkedIn for a 30-minute scoping call.

---

Built by Yurii Staryk · Solution Ecosystem Architect