> ## Documentation Index > Fetch the complete documentation index at: https://recurr.dev/docs/llms.txt > Use this file to discover all available pages before exploring further. # Kairos decisioning > How Recurr chooses which subscribers move, what path they see, and when the program should scale. Kairos is Recurr's decisioning engine. It sits inside Nostos and Oikos. In Nostos, it helps decide which subscribers are ready to see a migration path, what offer framing they should receive, when follow-up should happen, and whether the next cohort should scale, pause, or adjust. In Oikos, the same decisioning loop keeps running across the connected web book: acquire, retain, grow, and win back. It also keeps deciding when each newer store cohort is ready to migrate, so migration continues alongside the web-book motions rather than ending when the first waves do. ## What Kairos decides Cohort and subscriber signals help decide who should move now and who should wait. Offer, message, surface, and follow-up cadence are matched to the subscriber and cohort. The program expands only when uptake, billing health, support signal, and churn risk stay inside agreed guardrails. After migration, the same loop chooses approved lifecycle motions across the web book. ## Tenure matters Recurr does not try to move every new store subscriber immediately. New subscribers can be fragile. They may still be forming the habit, deciding whether the product is worth keeping, or approaching an early churn point. Kairos uses tenure as one input so newer store cohorts can mature before they see a web-billing path. That ongoing movement of newer store cohorts is **ascension**: the same migration logic applied over time, once a cohort has enough stability to move safely. It is migration, and it carries the same 5% of what we move. ## Offer discipline Recurr's posture is price parity, not web discounting. Offers can still be used, but they are limited-scope sweeteners for the right subscriber path: to reduce inertia, make the switch feel fair, or protect a sensitive moment. The goal is to move the billing relationship without teaching subscribers that web means a permanently cheaper product. See [Offer strategy](/docs/framework/offer-strategy) for the Nostos-specific version of this decision. ## Signal inputs Kairos is informed by subscriber and cohort signals from the customer's stack and from Recurr surfaces. Those signals can include tenure, plan, billing rail, renewal timing, product engagement, message engagement, checkout outcomes, payment outcomes, support signal, and churn risk. See [Analytics and subscriber signals](/docs/integration/analytics-signals) for the integration view. ## Why it is hard to copy with point tools Point tools can segment, send, test, bill, or report. Kairos connects those jobs to the commercial outcome. It reads subscriber and cohort signals, chooses from approved motions, runs the path through Recurr surfaces, and learns from what happens: movement, payment, support, churn risk, and future lifecycle outcomes.