gethumandesign.com

The cycles of one saved person's life, dated from the ephemeris (Pro). The Saturn return (around 28–30, again 58–59 and 87–88), the Uranus opposition (38–44), the Kiron return (50–51), the nodal returns (every ~18.6 years) and the yearly Solar return. A return is the moment the body is back where it stood at their birth; the Uranus opposition is Uranus halfway round. Without `cycle`: the timeline — every occurrence with its exact passes, age and status, one call for the whole life. With `cycle`: that cycle's chart, cast at the exact moment and read against theirs — Cross, Profile, Nodes, and the channels it completes with the natal chart. The chart needs an exact birth time; the timeline does not. Every date is computed from the ephemeris; an age does not give one. An occurrence past 2053 has an approximate age and no date. Times come back already in `timezone`, with the zone named. A cycle is a phase that begins and ends, not a verdict: type, strategy and authority stay the natal chart's. read_skill('cycles') is the guide to reading a cycle chart, and the result names the knowledge-base page for it.

get_cycles

List all groups with their members (Pro feature).

list_groups

List the people saved in the user's account, with the birth data that tells them apart. Each row carries the person_id that update_person takes — the sentinel 'me' for the account holder, the row id for everyone else — and the birth date and place, which is how to ask the user which person they mean when a name alone does not settle it. The time of day is not included; get_person_design has it.

list_people

One of this app's written guides to a Human Design topic, by name. The guides on this server, and the questions each covers: - about-gethumandesign: The product, the company and the FAQ. Load when asked about price, free limits, refunds, cancelling, referrals, installing on a phone, chart accuracy, who to email, or our languages. - app-links: Links into the web app, the tool that does each job here, and what only the app does. Load when asked where or how to do something. - cycles: Returns and life stages with get_cycles — Saturn, Uranus opposition, Kiron, nodal, Solar — and reading a cycle chart. - global-cycle-2027: 2027 and the global cycles: Planning giving way to the Sleeping Phoenix, what it means for a chart, Raves. - lilith-chiron: Black Moon Lilith and Chiron in a chart (Pro). Load for Lilith, Chiron, the wounded healer or the dark feminine. - privacy-and-terms: The published privacy policy and terms of service, word for word. Load before answering anything about what we collect, who processes it, retention, deletion, AI training, cancellation, refunds or liability. - rave-mandala: Which gate a degree or zodiac position falls in, where gates begin and end, how line, colour, tone and base are cut, the Design date, and why another calculator disagrees. - transits: Reading the sky, now or in any past year: get_transits and its family. Load for a planet in a gate, who it affects most, a gate's next entry, the Rave New Year.

read_skill

Create or update a group in one call (Pro feature). Declarative upsert: an existing group's members are replaced by member_names; otherwise the group is created with them.

save_group

Save a new person's birth data so their chart can be fetched later with get_person_design. is_me is required on every call and has no default — true for the account holder, false for anyone else. With is_me=true this becomes the account holder's own chart and the call answers with it — one call sets the account up and tells you their design; it also clears the flag on any previous 'me'. For the user themselves prefer it over calculate_chart, which remembers nothing. Ask how sure the user is of the birth time and pass birth_time_confidence; an unknown time is still worth saving, as 'unknown'. Create-only: an existing name fails and reports what is stored; relay that rather than retrying. Correcting someone already saved is update_person (or set_birth_time for their birth time alone), never a second save.

save_person

Send product feedback about the gethumandesign product to its team. In the user's words, lightly cleaned up. Send directly when they asked you to pass it on; when you are the one offering, show the message first and send after they confirm. The team reads everything and replies to the account email when needed; the user gets a copy by email. Does not consume the request quota.

send_feedback

Correct a saved person's birth time, and how sure the user is of it. How a placeholder or half-remembered time becomes a real one without the user leaving the conversation. Only the time and its confidence change; date, place, name and the 'me' marker stay as saved. Take the confidence from what the user said, and call this only for a time they gave you; to try a time out, call compare_birth_times, which changes nothing. Answers with the payoff: an 'exact' time returns the refreshed chart, an approximate one returns the birth-day sweep re-scored against the new time. Either way the result carries a `birth_time_change` block: say what moved and what held.

set_birth_time

The transit field laid over one saved person's bodygraph, now or on a given day (Pro). The sky is one field, the same for everyone; get_transits reads it alone, and this tool reads it against one chart. Answers with every planet's gate and line, the channels the sky completes in that person's chart, which centers those define, and the moment each one ends. The tool for any question about how the transits land for somebody — "what is going on for me today", how a moment affects a saved person. Positions are computed for the moment asked about: the sky moves, a chart does not, and a remembered position is wrong within hours. Needs an exact birth time. Half the gates of a chart move inside an uncertain hour, so a person whose time is remembered or unknown is refused by name, and the refusal says why. Every timestamp in the result is already on the reader's own local clock with the zone named; `timezone` sets which clock that is. In Human Design a transit is weather, not instructions. Type, strategy, authority and profile are cast at birth and no planet moves them, a transit is not a prediction, and the decision stays with the person's own authority.

get_person_transits

Correct a person already saved: their name, birth data, or which of them is the account holder. Call it whenever the user says a saved record is wrong — "that is not my chart", "that was my child's", a corrected birth date, or the name they want to be called. Addressed by person_id ('me', or an id from list_people), never by name: two people on one account can share a name, and the row that is wrong nearly always carries the user's own. Pass only the fields that change. Everything else stays exactly as saved, and the result names what moved and what held — say that and no more. is_me=true makes this person the account holder and clears the marker wherever it was, which is the fix when the account holds the wrong person entirely. Answers with the payoff when birth data moved: the refreshed chart for an 'exact' time, the birth-day sweep for an approximate one. Birth data includes the confidence — a time that just became 'exact' is a chart that just became readable — so a confidence-only correction comes back with the chart too. A rename alone returns the confirmation and no chart. To change only a birth time, prefer set_birth_time, which reports how much of the chart that time settles.

update_person