Horoscope stemmatics

Status: Anticipated · untested

Status is derived only from the shepherd-authored triage/prediction data above -- community submissions and claims are a separate overlay and can never change it (see the participation panel below).

This is a proposed connection between two domains, generated by a language model. It is not an article and not evidence: it sits below the evidence/publication boundary. A quantitative prediction and a named kill-dataset are attached (when registered) so the claim stays falsifiable rather than merely evocative.

Claim (verbatim)

Horoscope stemmatics. Stemmatics — reconstructing the family tree of manuscripts from shared copying errors — is here fused with computational astronomy. A dated horoscope is a calculation: the astrologer looked up planetary positions in one specific physical copy of a set of astronomical tables and worked from whatever numbers that copy contained, corruptions included. So every computational error in a surviving horoscope is inherited from the particular table copy used, just as a textual error is inherited from an exemplar. Recompute the astronomy for each dated horoscope — modern ephemerides say exactly what the correct entries were — and the residual errors fingerprint the table copies behind them. Horoscopes sharing an error pattern used the same copy or its descendants, so clustering the errors reconstructs the copy-tree of the tables themselves, including lost copies no library holds.

Prediction clause (verbatim)

For each surviving dated horoscope, recompute the true planetary positions for its date with modern ephemerides and extract the error vector of its stated positions; cluster horoscopes by shared error patterns and compare the groupings with what is independently known of table recensions and provenance. Primary clause: horoscopes group into distinct shared-error families well above chance agreement, and where table recensions are independently identifiable the clusters align with them in a clear majority of assignable cases; error patterns that prove idiosyncratic noise, admitting no stable clustering, kill the conjecture. The verdict follows the primary clause.

Kill-dataset (verbatim)

recompute and cluster.

Nobody has run this test. The kill-data is named above. If you can run it — or you know the paper that already settles it — claim the kill or submit the prior. Kills and priors are credited here, by name, as they come in.

In the atlas

This conjecture is bridged, as an L1 lead, onto these Inferpedia subject pages.

Provenance

Run: Imported conversation (verbatim harvest) · model: claude-fable-5

Origin: operator conversation with Claude Fable 5 at max effort, conducted 2026-07-03, relayed verbatim by the operator into the shepherd session on 2026-07-04. No ModelRun exists for the original generation (it happened outside the pipeline); this transcript file is the canonical capture. Transcript path: docs/generated/conjecture_harvest_fablemax_20260703.md. Model (operator-attested, not pipeline-recorded): claude-fable-5. Novelty disclaimer (verbatim, load-bearing -- rule 4): "Same caveat as before, doubled: at 100 items across all of archaeology and history, some of these will have cousins in the literature I can't check. What I can guarantee is the format — each links two things not normally linked, and each names the dataset or measurement that would kill it."

Novelty / leakage triage

anticipated in the literature — this exact test has never been run

Both halves exist separately: recomputation-based error dating of astronomical texts (Almagest speed/error methods) and philological transmission studies of table traditions (van Dalen; Maragha-to-Trebizond parameter tracking). The join — recomputing a horoscope corpus and clustering error patterns into a stemma of the underlying tables — was not located.

van Dalen 1993, 'Ancient and Mediaeval Astronomical Tables' — Table-transmission methodology
'Astronomical Refutation of the New Chronology' (arXiv 2504.12962) — Recomputation-error dating, single text

Predictions

No prediction registered yet.

Weigh in

No community feedback yet.

Add your take

Posted immediately (spam is removed). Community feedback is never an adjudicated verdict and never changes this conjecture's triage label or status above.