Current production contract
Production available · 78 calculations
Electional timing decisions, without hidden scoring weights
Two date modes: standard civil inputs cover 1800–2200. All 77 date-bearing operations also accept explicit historical inputs from 1000 BCE (BC) to 2500 CE (AD), with a chosen calendar and, for timed calculations, UT1 or a fixed UT1 offset. Date-only numerology requires an explicit year-digit convention. Place search is date-independent. Each tool retains its search, geometry, derived-date and export limits; historical iCalendar is not supported. The ordinary date-string examples below describe standard mode. Historical input guide and current schemas.
Cosmic Ephemeris turns sampled electional repair evidence into an exact hardening decision audit. It preserves competing tradeoffs, measures worst-case regret across uncertain failure budgets, and returns every tie.
- Availability
- Current
- Production
- 78 calculations
- Evidence
- Exact sampled integers
- New licenses
- None
Direct answer
What is an electional hardening regret audit?
It is a deterministic comparison of how much protection each criterion-repair hardening profile leaves on the table when the number of simultaneous repair failures is unknown. At each analyzed failure budget, Cosmic Ephemeris finds the best observed avoided loss, subtracts every profile's avoided loss, and reports that exact difference as regret. The profiles with the smallest worst regret across all budgets are the minimax-regret ties.
Live request boundary
Call the endpoint from a trusted backend
Send POST https://api.cosmicephemeris.com/api/astro/electional-criterion-repair-hardening-regret-audit from Node.js 22+ or another server runtime. Keep COSMICEPHEMERIS_KEY private; never put it in browser code, URLs, prompts, or analytics. Civil dates must stay within 1800-01-01 through 2200-12-31.
curl --fail --request POST \
--url https://api.cosmicephemeris.com/api/astro/electional-criterion-repair-hardening-regret-audit \
--header "Authorization: Bearer $COSMICEPHEMERIS_KEY" \
--header "Content-Type: application/json" \
--data '{"start_utc":"2026-10-04T00:00:00Z","end_utc":"2026-10-05T00:00:00Z","location":{"lat":40.7128,"lon":-74.006},"profile":{"zodiac":"tropical"},"filters":{"moon_signs":["Aquarius","Pisces"],"mercury_motion":"direct"}}'
Transparent by construction
A reliability audit, not another opaque score
| Question | Typical ranked output | Cosmic Ephemeris contract |
|---|---|---|
| How are tradeoffs combined? | Configured or undocumented weights | No weights; each failure budget remains visible |
| What happens to ties? | Often reduced to one displayed winner | Every tied benchmark and minimax profile is returned |
| Can the result be checked? | A final score may hide intermediate evidence | Exact integer regret, budget witnesses, and profile IDs |
| Is it advice? | May be presented as a recommended window | No ranking of times, prediction, interpretation, or recommendation |
Evidence pipeline
How the live audit reaches minimax regret
- 01Sample the declared criteria
Reuse the strict seven-grid, at-most-seven-day electional evidence boundary.
- 02Prove minimal repairs
Retain exact cross-grid criterion relaxations and their recovered observations.
- 03Model hardening profiles
Protect one repair at a time and preserve every unique avoided-loss vector.
- 04Minimize worst regret
Compare profiles budget by budget and return all least-maximum-regret ties.
Bounded and auditable
The exact analysis ceiling
The regret layer reuses the preceding hardening hierarchy and performs no additional chart calculation. A maximum-tie synthetic acceptance case emitted all 19,600 references and 70 minimax ties in about 0.7 ms on the acceptance host.
Answer-ready response
What a consumer can inspect
The source contract exposes separate budget benchmarks and per-profile regret certificates. This abbreviated shape is the deterministic subset returned for the request above.
{
"regret_status": "zero_maximum_regret_hardening_profile_observed",
"hardening_budget_benchmarks": [
{
"unavailable_repair_count": 0,
"maximum_avoided_worst_case_observation_count": 0,
"best_hardening_profile_ids": ["hardening_profile_001"]
}
],
"hardening_profile_regrets": [
{
"hardening_profile_id": "hardening_profile_001",
"maximum_regret_observation_count": 0,
"maximum_regret_failure_budgets": [0],
"minimax_regret": true
}
],
"minimax_regret_hardening_profile_ids": ["hardening_profile_001"]
}
Truthful availability
What is—and is not—available today
Production available: the live API, current OpenAPI and Postman contracts, published Node and Python SDKs, and the 42-operation n8n connector.
Verification boundary: production acceptance covered all 78 routes, public authentication boundaries, and a receipt-signed calculation with exact one-unit accounting. These checks do not guarantee search-engine placement or third-party citations.
Method limits
What the evidence does not claim
- It does not prove the best continuous instant between sampled times.
- It does not assign probabilities to failure budgets or preferences to criteria.
- It does not establish that hardening causes an outcome outside the returned model.
- It does not interpret astrology, predict events, or recommend a date.
- It does not claim universal market uniqueness; the competitive review is limited to cited public product material.
Questions and answers
Electional reliability API FAQ
Is the electional hardening regret endpoint live?
Yes. The endpoint is live as part of the 78-calculation API. Production acceptance verified its authentication boundary, signed-receipt path, one-unit accounting, and cleanup behavior.
What does minimax regret mean in this audit?
For each analyzed failure budget, the audit compares a hardening profile with the best observed profile at that same budget. Regret is the exact difference in avoided worst-case sampled observation loss. Minimax profiles have the smallest maximum regret across all analyzed budgets, and every tie is returned.
Does the audit rank electional times or recommend a date?
No. It audits the robustness of sampled criterion-repair hardening profiles. It applies no probabilities, preference weights, quality score, interpretation, prediction, or recommendation.
Does this research add a licensed dataset or dependency?
No. The regret layer is original Cosmic Ephemeris source using standard-library integer comparisons and existing bounded evidence. It adds no dataset, package, catalog license, third-party code, or request-time network source.