Calculator roadmap with the same A-grade standard applied to every next phase

Why this phase exists

This keeps future calculators from falling back into one-off page builds, duplicated inputs, or repeated exact-chart calls for the same verified birth data.

quality check

Every new calculator family must ship with clear metadata, related links, FAQ structure, reusable input primitives, and exact-vs-manual honesty.

Why this phase exists

This is the exact-data backbone for higher-intent readers who need real chart math instead of editorial approximations.

quality check

No chart route should guess Moon, Rising, houses, or aspects from date-only logic. Saved-chart reuse must be in place before broad rollout.

Why this phase exists

This unlocks deeper content without repeatedly spending API credits for the same user chart.

quality check

Interpretive routes must consume verified placements and clearly label what is interpretive versus what is exact chart structure.

Why this phase exists

Compatibility is a strong search and repeat-visit lane, but it only stays trustworthy if the product separates quick reads from exact two-chart analysis.

quality check

Every relationship route must disclose whether it uses Sun-sign logic, known placements, or full synastry data.

Why this phase exists

These routes create repeat visits and stronger retention, but only if rate limits, caching, and precision boundaries are handled carefully.

quality check

Time-sensitive routes must handle 429s cleanly, cache verified responses where appropriate, and state exact date assumptions explicitly.

Why this phase exists

Advanced tools deepen authority and organic reach, but they are also the easiest place to lose clarity if the UX becomes opaque.

quality check

Advanced routes must still present plain-English summaries, trustworthy inputs, and strong education blocks for readers who want technical clarity.

Why this phase exists

A-grade traffic acquisition fails quickly without operational confidence, especially on API-backed paths.

quality check

Exact-chart routes need contract coverage, usage tracking, and production-grade failure handling before broad promotion.

Why this phase exists

This phase captures obvious calculator demand like free natal charts, Midheaven sign, Descendant sign, dominant modality, and Big 3 compatibility without compromising the exact-data trust model.

quality check

Every Phase 9 route must reuse an existing exact or saved-chart workflow, declare honest accuracy boundaries, and avoid inventing shortcut math for birth-time-sensitive placements.

Why this phase exists

Solar Return pages are a strong repeat-use annual cluster, but they only stay trustworthy if all variants inherit one exact annual chart workflow instead of fragmenting into separate approximations.

quality check

Every annual route must reuse the same saved-chart-plus-Solar-Return engine, keep the selected city and year visible, and avoid event-certainty language that overclaims beyond the annual chart.

Why this phase exists

Transit pages create strong repeat-use timing demand, but the route family only stays trustworthy if each variant reuses the same exact current-sky workflow instead of splitting into generic horoscope copy.

quality check

Every Phase 11 route must show the selected city and timestamp clearly, reuse the saved-chart layer for personal pages, and keep planet-specific transit claims bounded to exact current chart structure.

Why this phase exists

Relationship traffic converts well when the site stays grounded, but it only stays trustworthy if higher-intensity labels like karmic or twin flame are anchored to exact chart comparison and clear realism checks.

quality check

Every Phase 12 route must reuse the saved dual-chart workflow, disclose exact-chart dependence clearly, and avoid manipulative certainty in soulmate, karmic, or twin-flame language.

Why this phase exists

Progressions deepen authority for readers who need chapter-level timing, but they only stay trustworthy if every route reuses one exact secondary-progressions engine instead of drifting into generic self-help copy.

quality check

Every Phase 13 route must show the target date and city clearly, reuse the saved natal-chart layer, and keep progressed-chart claims bounded to medium-range developmental timing rather than fake event certainty.

Why this phase exists

Moon-focused pages drive repeat-use timing demand for readers who revisit lunar tools often, but they only stay trustworthy if monthly moon planning and lunar return pages inherit exact endpoints instead of drifting into generic moon mysticism.

quality check

Every Phase 14 route must keep the exact endpoint or monthly data source visible, use city-based location support where timezone matters, and avoid presenting symbolic moon timing as guaranteed event certainty.

Why this phase exists

Long-cycle timing pages are high-intent astrology searches, but they only stay trustworthy if return and cycle-event dates are derived from exact provider-backed chart probes instead of generic age tables.

quality check

Every Phase 15 route must disclose the search date and localized city clearly, keep cycle-event claims bounded, and reuse the same exact server-side search engine for future return and angle-event routes.

Why this phase exists

Traditional astrology pages widen authority for serious readers, but they only stay trustworthy if lot formulas, sect logic, and profection rules are applied exactly instead of being blurred into modern inspirational copy.

quality check

Every Phase 16 route must either use one verified natal chart for exact lot math or require a clearly known Rising sign for manual timing logic, and it must disclose where formulas reverse between day and night charts.

Why this phase exists

This phase fills the broad educational backlog that supports beginner search demand, internal linking, and lower-friction conversion into exact chart routes.

quality check

Every Phase 17 route must reuse the shared sign, house, or planet profile layer, stay honest about manual-versus-exact boundaries, and avoid duplicating editorial logic across long-tail pages.

Why this phase exists

This phase targets practical readers who want chart-backed guidance for work, self-care, money habits, and purpose questions without drifting into fake certainty or generic inspiration.

quality check

Every Phase 18 route must reuse the same verified saved-chart interpretation layer, keep medical and financial boundaries explicit, and frame outputs as practical guidance rather than guaranteed outcomes.

Why this phase exists

This phase fills a high-volume lifestyle and beginner search lane, but it only stays trustworthy if symbolic pages show exact lunar anchors where possible and keep the interpretation layer clearly bounded.

quality check

Every Phase 19 route must label symbolic boundaries explicitly, reuse the monthly lunar or saved-chart foundation instead of inventing fake personal timing, and keep beginner summaries simpler without abandoning exact chart support underneath them.

Why this phase exists

This phase closes the remaining advanced utility gap for QA, support, migrations, and expert readers without weakening the provider-safe architecture or exact-chart honesty model.

quality check

Every Phase 20 route must stay provider-safe, avoid exposing secrets, reuse the exact-chart workflow, and make clear whether it is for end-user interpretation, export, or debugging.

Why this phase exists

This phase closes obvious DOCX gaps quickly without inventing a second architecture or pretending near-duplicate search surfaces need new chart math.

quality check

Every Phase 21 route must reuse an existing trustworthy engine, stay honest about whether it is exact or manual, and avoid shipping thin redirect pages with broken metadata or missing registry support.

Why this phase exists

This phase captures broad horoscope search demand without collapsing exact personal timing into fake generic copy. It separates sign guidance from real chart-backed forecasting.

quality check

Every Phase 22 route must disclose whether it is sign-based or exact, reuse the existing transit or saved-chart stack when personal timing is claimed, and avoid dressing manual horoscope text up as exact astrology math.

Why this phase exists

This phase deepens repeat-use monthly timing demand, but it only stays trustworthy if every route reuses the same exact lunar-return chart instead of drifting into generic moon-mood copy.

quality check

Every Phase 23 route must show the return date and selected city, reuse the shared lunar-return engine, and keep monthly guidance framed as emphasis and pacing rather than guaranteed events.

Why this phase exists

This phase expands repeat-use transit demand without inventing a second transit engine. It packages the same exact checkpoint and live-sky stack into clearer entry routes for different timing intents.

quality check

Every Phase 24 route must keep the selected city and timing assumptions visible, reuse the existing exact transit workflows, and avoid pretending sampled checkpoints are broader than the visible window allows.

Why this phase exists

This phase fills a major relationship search lane beyond synastry alone, but it only stays trustworthy if relationship-chart and relationship-timing routes keep exact two-chart math visible instead of collapsing into vague soulmate copy.

quality check

Every Phase 25 route must reuse the verified dual-chart workflow, label whether it is composite, Davison, transit-based, or progression-based, and avoid presenting relationship timing as certainty or permission to ignore real-world safety and judgment.

Why this phase exists

This phase closes a high-intent educational and analysis gap between simple house explainers and advanced timing pages. It only stays trustworthy if structural summaries are derived from verified chart math rather than vague personality copy.

quality check

Every Phase 26 route must reuse the shared exact-chart structure layer, separate educational summaries from exact house- and angle-dependent claims, and keep house-system or birth-time fragility visible where it matters.

Why this phase exists

This phase closes a large beginner and long-tail search gap by turning existing sign, Moon, house, and exact-chart systems into clearer entry routes without weakening the accuracy boundaries.

quality check

Every Phase 27 route must reuse the existing sign, Moon, horoscope, or exact-chart workflows, keep manual-versus-exact boundaries explicit, and avoid turning beginner search-intent pages into fake chart-math shortcuts.

Why this phase exists

This phase closes the remaining numerology backlog for identity, naming, and low-friction self-development demand without introducing fake astrology dependencies or hidden API lookups.

quality check

Every Phase 28 route must reuse deterministic numerology formulas, keep interpretation practical and non-fatalistic, and clearly separate symbolic guidance from legal, financial, parenting, or mental-health claims.

Why this phase exists

This phase deepens the classical-astrology layer for advanced readers, but it only stays trustworthy if each route keeps the exact chart separate from the historical rule tables applied to it.

quality check

Every Phase 29 route must declare the traditional rule set it uses, keep the chart math exact, avoid mixing rival historical systems without saying so, and stay honest about where the later high-risk timing methods are still not live.

Why this phase exists

This phase closes the core traditional-lots backlog for advanced readers, but it only stays trustworthy if each route keeps symbolic lot work separate from medical, financial, or mortality claims.

quality check

Every Phase 30 route must use a defensible traditional formula, keep the natal chart exact, state its historical scope honestly, and avoid overclaiming outcomes in health, wealth, career, or death topics.

Why this phase exists

This phase is what keeps the remaining backlog honest. It separates what the active provider really supports from what the repo has actually normalized, so future exact routes do not drift into guesswork.

quality check

Every Phase 31 asset must distinguish repo-live contracts from provider-documented surfaces, mark schema gaps explicitly, and identify which backlog routes are still blocked on contract checks or a second provider.

Why this phase exists

This phase turns the provider-normalized geography contracts into a true location library without pretending the user has to read raw line maps or undocumented provider payloads directly.

quality check

Every Phase 32 route must reuse the existing normalized geography contracts, keep city comparisons honest about scope, and avoid map-style certainty that outruns the actual line or relocation data available.

Why this phase exists

This phase expands exact eclipse coverage while keeping a hard boundary between verified calendar data and still-unverified natal impact or eclipse-analysis payloads.

quality check

Every Phase 33 route must stay anchored to the normalized eclipse list contract unless a deeper eclipse-analysis payload is actually verified, and it must never fake natal impact from date-only eclipse data.

Why this phase exists

This phase closes the supportable special-point and fixed-star backlog without pretending the repo already has verified contracts for Juno or the broader asteroid family.

quality check

Every Phase 34 route must either come directly from the verified natal payload, be transparently derived from a trusted exact axis, or use the verified fixed-stars contract, while unsupported asteroid and minor-body pages remain blocked until contract-tested.

Why this phase exists

This phase closes a major repeat-visit traffic lane, but it only stays trustworthy if daily-sky, retrograde, and current-status pages use exact provider-backed data instead of generic evergreen astrology copy.

quality check

Every Phase 35 route must stay inside the normalized live-sky or verified natal-chart contracts, keep timestamps and city context visible, and defer ingress, ephemeris, shadow-period, or admin-gated station surfaces that the current provider access level cannot support honestly.

Why this phase exists

This phase closes a major expert-intent search lane, but it only stays trustworthy if question charts stay tied to one real moment and the rectification routes stay framed as stability checks rather than magical minute-finding machines.

quality check

Every Phase 36 route must keep the exact event or birth timestamp visible, reuse verified chart math, and clearly distinguish bounded chart-stability checks from provider-native rectification surfaces that are still not normalized.

Why this phase exists

This phase closes a practical timing lane for readers who want cleaner dates for launches, rituals, planning resets, and chosen moments, but it only stays trustworthy if shortlist logic remains bounded and exact chart math is never faked.

quality check

Every Phase 37 route must show whether it is shortlist-style symbolic timing, deterministic local planetary-hour math, or one exact chosen event chart, and it must avoid promising perfect dates or guaranteed outcomes.

Why this phase exists

This phase closes the remaining practical self-development lane, but it only stays trustworthy if career, money, Chiron, karma, purpose, and forecast pages remain grounded in exact chart structure instead of promising destiny, wealth, treatment, or guaranteed outcomes.

quality check

Every Phase 38 route must clearly separate exact chart structure from the interpretive layer, keep symbolic purpose or karmic language bounded, and avoid presenting money, wellness, promotion, or healing pages as financial, medical, or fate-level certainty.

Why this phase exists

This phase closes a real expert-intent backlog cluster for technical readers, but it only stays trustworthy if every page is clearly presented as a derived chart-analysis layer rather than a new predictive engine.

quality check

Every Phase 39 route must derive its math from the verified natal chart payload already in the repo, keep midpoint and harmonic claims bounded, and avoid pretending these technical layers are stronger than the natal chart that created them.

Why this phase exists

This phase closes a practical daily-timing lane, but it only stays trustworthy if ephemeris, ingress, and shadow pages are explicit about being bounded search surfaces rather than pretending the provider's locked premium ephemeris or station-phase endpoints are publicly available.

quality check

Every Phase 40 route must show exact local date or time context, derive its timing from the working planet-snapshot or retrograde-period contracts, and clearly label any bounded search scope instead of implying unlimited premium ephemeris access.

Why this phase exists

This closes a high-intent backlog cluster without fake minor-body chart math. It gives asteroid search demand a transparent exact-status answer and directs readers to real live alternatives.

quality check

Every Phase 41 route must show the last verified contract date, explain the exact block reason, and point users to currently supported exact or saved-chart alternatives instead of inventing Juno, Vesta, Eros, or Psyche placements.