1) Normalize the moment
We validate date/time formats, handle missing time cases, and prepare inputs for timezone conversion.
Our Method
How it works
Memento Astra is built like a tool, not a mood board: you provide a recorded moment (date, time, and place), and the engine computes placements, houses, angles, and derived signatures. From that chart data, it produces a threshold reading, structured interpretation focused on transition, closure, and what endures.
- Data-first computation
- Location + timezone resolved
- Structured reading output
Overview
Input → compute → extract → interpret.
The pipeline is intentionally explicit. The goal is to produce a repeatable chart and a readable interpretation, so if you change the time window, location precision, or house system later, you can compare outputs without guessing what changed.
2) Resolve the place
We turn a human place string into coordinates (lat/lon), and derive the correct timezone for that location.
3) Compute the chart
We compute planetary positions, angles, houses, and derived signatures (aspects, clusters, emphasis).
Pipeline steps in plain language
Normalize the moment
Validate date/time formats, handle missing time cases, and prepare inputs for timezone conversion.
Resolve the place
Turn a human place string into coordinates (lat/lon), and derive the correct timezone for that location.
Compute the chart
Compute planetary positions, angles, houses, and derived signatures (aspects, clusters, emphasis).
Assemble the threshold reading
Generate a structured interpretation focused on transition, closure, and what remains from computed features.
What you enter
The tool accepts human input, then makes it precise.
Date
A calendar date (YYYY-MM-DD). This anchors the computation and determines which ephemeris range is used. If you only know the date, you can still generate a chart by testing a time window later.
Time (optional but recommended)
A clock time (HH:MM). Time affects angles and houses heavily. If you don’t know it, the system can run “sensitivity” by testing multiple times across a window and comparing what moves.
Location text
A city/region string like “London, England” or “Austin, Texas”. The system resolves this to latitude/longitude and applies the correct timezone for that place on that date.
Precision notes
If you later add optional controls (house system, orb sizes, tropical/sidereal), this page’s flow stays the same: inputs become normalized parameters that generate a repeatable chart object.
What gets computed
The chart is not an image first. It’s data first.
Internally, the engine produces a chart object: positions, angles, house cusps, and derived features. The UI can render this as a wheel later, but the reading is generated from the structured results.
Placements
Planetary longitudes (and optionally speed/retrograde flags) form the baseline signature of the sky.
Houses + angles
Ascendant/Descendant and MC/IC are computed from time + location, then house cusps are derived from the house system.
Aspects + clusters
Tight aspects, conjunction chains, and stelliums are detected to find compression points where meaning concentrates.
How the threshold reading is produced
Interpretation is structured, not improvised.
The death-time chart isn’t used to predict death. It’s used to describe a boundary: the geometry of entry/exit (angles), where meaning concentrates (house emphasis), and what is compressed into the moment (clusters/aspects). The reading is assembled from these measurable features.
Angles as crossing
Ascendant/Descendant and MC/IC are read as axes of passage: entry/exit, descent/ascent, private/public closure.
House emphasis as closure
Loaded houses are treated as where the system concentrates meaning at the end-state: inheritance, remainder, release.
Compression points
Tight configurations are treated as concentrated signatures, not “good/bad”. The question is: what becomes unavoidable here?
Birth chart comparison (optional, but powerful)
If you generate both charts, you can compare recurring signatures: repeated angles, repeated house emphasis, repeated planetary relationships. Repeats can suggest continuity; reversals can suggest release; closure patterns can suggest resolution. The comparison is meant to be readable, not mystical.
Privacy, safety, and what this is not
Clear boundaries make the tool usable.
Not medical or forensic
The reading is symbolic and reflective. It does not determine cause of death, responsibility, or medical outcomes.
Data minimization
Only collect what you need to compute the chart: date, time, and place. Add optional fields only if they improve outputs.
Time uncertainty support
Unknown time is common. A time-window mode is expected behavior, not an error case.
FAQ
Common questions about method and accuracy.
They move quickly relative to clock time. If the recorded time is off by minutes, angles can shift noticeably, which changes the reading structure.
Yes. Placements can still describe the sky’s baseline signature. But for a threshold reading, you’ll usually want to test a time window to understand angle/house sensitivity.
You can generate any chart data, but the method and language on this site are tuned for transition and closure. Use the birth chart tool for baseline work.
A structured chart object (data-first) that can be rendered visually, plus a reading composed from computed features like angles, house emphasis, and tight configurations.