# Candidate rules and ambiguity register This register belongs to the [2026-10-22 research packet](README.md). `R01`-`R30` identify candidate rule families; they are not thirty admitted runtime predicates. `A01`-`A25` identify decisions or defects that prevent unqualified promotion. Primary pages are linked through the [source inventory](SOURCE_INVENTORY.md) and individual records in [packet.json](https://github.com/TheDaniel166/moira/blob/main/wiki/05_research/horary/lilly_core_2026/packet.json). ## Evidence contract Keep these stages separate: source located, passage visually checked, operationally specified, independently fixture-checked, implemented, validated, admitted. This packet reaches the first two stages for selected passages. The existing v1 admission is a separate historical contract. Every future atomic rule needs author/edition and exact passage, proposition, required inputs, context, preconditions, exceptions, evaluation epoch, dependencies, precedence, missing-input behavior and independent fixtures. Every conclusion must cite its supporting and opposing witnesses. No numeric confidence or universal affirmative/negative score follows from this register. An epoch is one of: question, last separation, intermediate contact, final contact, or explicitly unspecified by the source. A source that leaves an epoch unspecified does not license quietly choosing the initial chart. ## Candidate rule families | ID | Original pages | Compact source proposition | Required evidence and limit | |---|---|---|---| | R01 | 35, 39-42, 47 | Erection depends on the stated date, clock and local ephemeris procedure. P.41 explicitly converts a morning to hours after the preceding noon. | Literal date/time; calendar, year start, clock origin, locality, conversion receipt. Never treat printed P.M. automatically as modern civil PM. | | R02 | 47-56 | Houses have distinct topics, angular/succedent/cadent condition and source-specific strength. | Caller-confirmed question facts, actual cusp/placement geometry and topic passage; a house label is not a complete judgement. | | R03 | 127-128 | A related person's house becomes their first; other houses are counted from it. Who asks can change the perspective. | Explicit entity/relationship path and inclusive count, with the radical anchor retained. | | R04 | 49, 123-124 | The querent is represented by the Ascendant/lord; the thing demanded by its appropriate house/lord. Other planets can contribute. | Question context, cusp-sign rulers, descriptive/co-significator evidence; do not silently replace a collided principal. | | R05 | 124 | Moon is co-significator of the querent; Lilly rejects making its last separated planet co-significator by that fact alone. | Moon's roles and sequence independent of the principal pair. The following next-applying/co-quesited discussion needs contextual resolution. | | R06 | 104, 112, 115 | Dignity and peregrinity depend on specific essential dignities at a place; reception also enters the fortitude table. | Versioned Lilly table, sect and degree bounds; do not substitute a generic term/triplicity table or turn fortitude into probability. | | R07 | 107, 110 | Planetary full orbs have two printed alternatives; contact range uses the sum of their halves. | Named selected table and exact boundary policy. Current fixed values are not the sole table allowed by this source. | | R08 | 107-109 | Application has direct/direct, retrograde/retrograde and mixed-motion forms; partile, dexter/sinister and sign-beholding are distinct notions. | Directed separation, relative motion, aspect branch, orb and sign relation. Planetary weight is not automatically instantaneous speed. | | R09 | 110 | Separation begins at six arcminutes in the description, but complete separation is beyond the combined moieties. | Distinguish exact root, partile status, initial separation and full departure from an orb. | | R10 | 112 | Reception is described through mutual dignity, with examples in several bases, and can assist without an aspect or through adverse aspects. | Directed dignity relations, mutuality, basis, context and epoch; mechanism-specific reception requirements must remain distinct. | | R11 | 112, 122 | VOC concerns separation followed by no further application during the sign; p.122 qualifies the consequence by principal strength and signs. | Source definition of application, lunar sequence/sign boundary, and separately encoded exceptions; no automatic universal denial. | | R12 | 113-114 | Combustion is described as corporal proximity in the same sign within 8 degrees 30 minutes; beams and cazimi have distinct thresholds. | Sun/planet longitudes and signs, direction if relevant, endpoint policy; record the apparent inconsistent numerical example. | | R13 | 121-122 | Hour agreement can concern lord identity, triplicity or nature; the question and erection context matter. | Bound question-time/location receipt, day/night hour, sign lord/triplicity/nature and the source examples. | | R14 | 122 | Early/late Ascendant cautions include descriptive/age exceptions; the late caution also distinguishes known-event figures. | Degree, caller-supplied age/description and figure purpose; lack of context is not proof that an exception fails. | | R15 | 122 | Late Moon and Via Combusta are cautions with source qualifications. VOC is mitigated in named signs and by strong principals. | Moon sign/degree, strength evidence and source hedge; avoid treating all cautions as strict prohibitions. | | R16 | 122-123 | Saturn and seventh-house/lord warnings concern different risks; the artist/seventh caution depends on question context. | Actual placements/condition and whether the matter concerns the seventh. Keep judgement reliability and matter difficulty separate. | | R17 | 123 | Balanced fortunate and unfortunate testimonies counsel deferral; combust Ascendant lord and other conditions add cautions. | Source-defined testimony types, not a count of arbitrary votes or a fabricated confidence threshold. | | R18 | 125 | Conjunction can perfect under conditions of placement, strength/motion and no interruption; house class modifies the account. | Exact contact plus role-specific condition and intervening events. Contact alone is not the complete proposition. | | R19 | 125 | Sextile/trine perfection is qualified by good houses, dignity and absence of intervening malefic testimony. | Qualifiers and their epochs; distinguish the astronomical aspect from the source judgement. | | R20 | 125 | Square perfection is possible with dignity and suitable houses. | Explicit source-conditioned route; neither unconditional success nor unconditional failure follows from square alone. | | R21 | 125 | Opposition requires additional reception/house/Moon conditions in this discussion and can lead to regret or expense. | Mutual domicile reception, house and Moon sequence evidence; completion and desirability are separate propositions. | | R22 | 111, 126 | Translation joins significators through a lighter intermediary; the fuller perfection passage adds reception and contact/history conditions. | Two directed legs, source receiving translator in house/triplicity/term, no intervening contact, principal relationship history and epochs. | | R23 | 126 | Collection concerns principals that do not behold one another, both contacting a heavier collector which each receives. | Both principal-to-collector applications, directed reception by each principal, heaviness, chronology and beholding definition. | | R24 | 110-111 | Prohibition is an intervening action preventing the intended completion; the source distinguishes bodily and aspectual forms. | Intended application and relevant third-party sequence; do not assume every intervening contact is prohibition. | | R25 | 111 | Refranation interrupts an intended application by reversal before completion. | Application, station/reversal and failure to complete; an actual later exact aspect is not a necessary historical premise. | | R26 | 112-113 | Frustration describes an intended bodily conjunction defeated when the heavier significator first joins another. | Conjunction-specific intended and intervening relationships; do not generalize automatically to every aspect. | | R27 | 126-127 | Dwelling in the relevant house is attributed to earlier authorities, but Lilly declines to rely on it without the Moon carrying the virtue. | Preserve the author's rejection/qualification; do not add an unconditional seventh success mechanism. | | R28 | 125 | Angular/succedent/cadent contexts modify speed/ease of accomplishment in the general perfection discussion. | Qualitative timing only here. An exact aspect timestamp does not determine symbolic weeks, months or years. | | R29 | 48, 113-115 | House strength, Hayz, oriental/occidental condition, besiegement and the fortitude table supply distinct condition evidence. | Separate definitions, sect, body group and table entries. Table scores and ordered comparisons are not one interchangeable judgement scale. | | R30 | 491 | Book III recommends exact Regiomontanus construction for nativities and describes it as more scrupulous than ordinary questions need. | Auxiliary scope evidence; it does not impose one universal horary house-method default. | ## Ambiguities and dispositions All records remain open for the new executable tranche unless a disposition below is expressly limited to catalogue/source handling. None changes v1. | ID / type | Issue and alternatives | Packet disposition / closure evidence | |---|---|---| | A01 / historical input | Noon-origin hours, AM/PM wording, Julian/Gregorian calendar and year-start style are separate axes. | Preserve raw strings. Per-case conversion must explain date rollover, year and locality before a JD/UT value is allowed; use E03 as an independent clock fixture. | | A02 / computational policy | Source houses, current house API policy and boundary/placement rules need a named contract. P.491 does not settle all ordinary-question defaults. | Preserve supplied house policy; no silent method substitution. Document planet/cusp boundary and turning behavior separately. | | A03 / role model | Two entities can have one planetary lord; Moon and other source roles can overlap. | Preserve collisions and candidate roles. Require a source-specific alternative rule rather than inventing a replacement significator. | | A04 / table identity | Labels such as Ptolemaic, Egyptian or traditional can conceal different cells, sect handling or endpoint conventions. | Bind the actual p.104 table and double-enter every cell needed by fixtures. Current policy already names Lilly; old validation prose is stale. | | A05 / genuine source alternatives | P.107 prints two orb sets; p.110's Saturn/Jupiter example uses the second. The current fixed table mixes values from these alternatives. | Preserve all three tables below as separately identified data. Selecting a future table needs an explicit profile decision and paired boundary fixtures. | | A06 / definition versus numerical tolerance | Six-arcminute separation, partile equality, orbital contact and a solver's root tolerance answer different questions. | Specify separate fields and endpoint tests; never use a historical arc threshold as a root-finding error tolerance. | | A07 / terminology | Lighter/heavier can mean traditional planetary order; the implementation uses absolute instantaneous speed. Stations can change their relation. | Collate mechanism examples and practice; specify which notion each mechanism requires, including direct/retrograde motion. | | A08 / reception semantics | Mutual reception, directed reception and mechanism-specific bases differ; current generic and perfection APIs use incompatible receiver vocabulary. | Define host as dignity ruler and guest as occupant in plain terms. Explicit adapters and same-/mixed-basis tests precede reuse. | | A09 / doctrine scope | P.112 permits reception to assist even without an aspect; the broad statement does not fully operationalize every outcome. | Keep a reception-without-aspect candidate route, unadmitted until context and counterexamples are collated. Do not infer universal success. | | A10 / lunar definition | P.112's application during a sign can be read through orb/application or exact-completion criteria; these differ near an ingress. | Preserve alternatives; specify event universe, bounds and what counts as application. The generic VOC helper is not automatically Lilly's definition. | | A11 / qualitative exception | P.122's strong principals and sign exceptions do not supply a universal numeric strength threshold. | Encode named qualitative evidence and unknown context. A threshold needs source/practice support, not an arbitrary score. | | A12 / solar policy | Same-sign combustion differs from a distance-only band, especially across a sign boundary; threshold inclusivity is not fully formalized. | Test equal distance in same/different signs; maintain source and geometric evidence separately. Cazimi/beams need their own endpoint decisions. | | A13 / apparent printed inconsistency | P.113 defines 8 degrees 30 minutes but appears to call Jupiter 28 Aries with Sun 18 Aries combust. | Retain literal readings; collate alternate photograph before proposing an erratum. Do not silently change 28 to 26 or widen the threshold. | | A14 / context and force | Early/late exceptions, artist/seventh warnings and Via Combusta's qualified attribution resist universal boolean denial. | Require context inputs and distinguish caution, exception, unknown and not applicable. Preserve the source hedge. | | A15 / authorial stance | P.124 rejects the Moon's last-separated planet as co-querent; the ensuing next-applying/co-quesited passage needs contextual reading. | Record those as different propositions. Check worked practice before admitting an automatic new role. | | A16 / judgement conditions | Good/friendly houses, strong planets, malefic intervention and opposition regret need definitions and scope. | Separate R18-R21; give every qualifier a predicate or typed unresolved state. An exact contact cannot stand in for all of them. | | A17 / translation scope and epoch | P.111 gives a structural definition; p.126 adds principal-history and reception conditions. When must reception/strength hold? | Keep both source contexts. Test history, allowed bases, direction, intervening contacts and initial versus event-time changes. | | A18 / collection scope and epoch | Not beholding may concern sign relation rather than present orb; reception of the collector and heavier status need explicit epochs. | Preserve the source's reception direction. Compare sign/aspect alternatives and changing dignity before the last contact. | | A19 / implementation admission gap | Current blockers require an eligible actual future pair contact. A reversal can prevent the contact altogether. | Specify intended application independently from completed event search. Add blocked/no-exact fixtures before expanding admission. No repair is made here. | | A20 / implementation admission gap | Current prior-event filters exclude events within the advertised one-second tie band before the tie predicate examines them. | Add independent exact/near-simultaneous station, ingress and third-contact fixtures. Treat this as a code gap, not a historical ambiguity. | | A21 / completeness and coverage | Current witnesses retain the first translation/collection candidate; a 31-day boundary is a safety limit, not doctrine. | Future output must preserve all candidates, dependencies and unresolved frontier. Do not chain windows while discarding cross-boundary state. | | A22 / attribution | A catalogue that lists the dwelling shortcut without Lilly's rejection would misattribute earlier doctrine to him. | Source handling resolved: record as rejected/qualified in Lilly. Any positive mechanism still requires Moon evidence under the admitted rule. | | A23 / timing | Event time, qualitative speed, symbolic units and a reported historical duration have different evidence. | No universal degree-to-unit conversion in the core. Later timing admission must state context, alternatives and uncertainty. | | A24 / historical corpus | Printed coordinates, modern reconstructions, author-reported outcomes and independent outcomes are different records. Fish years differ; some epochs are absent. | Null normalized fields, record variants and source qualification; separate reused/hypothetical/event cases and exclude leakage from predictive sets. | | A25 / condition aggregation | P.48 orders house strength; p.115 gives grouped point values and extra conditions. Their granularity and purpose differ. | Keep ordered comparison and tabulated fortitude separate. Double-enter the table before any computation; never turn its sum into a universal verdict. | ## Orb-table receipt (A05) All entries are **full orbs in degrees**, not already halved moieties. | Body | First printed set, p.107 | Second printed set, p.107 | Current fixed constant | |---|---:|---:|---:| | Saturn | 10 | 9 | 10 | | Jupiter | 12 | 9 | 12 | | Mars | 7.5 | 7 | 7 | | Sun | 17 | 15 | 15 | | Venus | 8 | 7 | 7 | | Mercury | 7 | 7 | 7 | | Moon | 12.5 | 12 | 12 | Combined contact range is `(full_orb_A + full_orb_B) / 2`. P.110's Saturn/Jupiter example halves nine and nine, giving nine degrees; the current constants give eleven. The current table remains a fixed existing policy. This packet does not rename it, change it or imply that the source requires one unqualified replacement. ## Current implementation seams (read-only audit) Inspected at the baseline in [README](README.md). These are code findings, not tests rerun in this documentation task. | Owner | Current behavior | New admission consequence | |---|---|---| | `moira/horary.py`: time adapter, house resolution, significators | Explicit time receipts and radical/turned assignments; stable v1 evidence-only scope | Retain contract; broader roles/context need additive admission | | `moira/horary.py`: `_considerations` | Six bounded considerations; Moon assigned but no independent Moon completion route | R05/R11/R14-R17 require separately specified additions | | `moira/classical_perfection.py`: `_current_relation`, `eligible_direct` | In-moiety application plus exact trace; all five aspect kinds share this geometric eligibility | Add source-conditioned R18-R21 above the event layer, without claiming current output is a yes/no judgement | | Same: `_reception_bases` | Host/guest helper recognizes five Lilly bases; translation restricts to house/triplicity/term; collection tests each principal receiving collector | Preserve direction, expose basis/epoch; generic reception requires an adapter | | Same: `_prior_interruptions`, `third_aspects`, `tie` | Strictly-before filtering precedes tie detection | A20 needs focused regression evidence; no fix in this packet | | Same: `eligible_direct` gates blocker witnesses | A missing later exact pair event suppresses a blocker witness even for intended application | A19 requires no-exact refranation/blocked application cases | | Same: `translations[0]`, `collections[0]` | Only the first successful candidate becomes its kind's witness | A21 requires all-path evidence for a broader reasoning product | | Same: fixed `LillyPerfectionPolicy` | 31-day cap, initial-chart condition checks, ingress indeterminate, named Lilly table identity | State epochs and bounded coverage explicitly; these are operational policies | | `moira/dignities_types.py` and dignity reception service | Generic reception covers domicile/exaltation; receiver vocabulary differs | Do not reuse as a five-basis directed graph without semantic conversion | | `moira/void_of_course.py` | Generic lunar connection/window machinery exists | Useful event substrate; not source admission of one Lilly VOC interpretation | | Solar proximity truth and horary solar receipt | Geometric distance-band evidence feeds the caution; no same-sign condition in that check | R12 needs a source-qualified condition layer | Existing `tests/unit/test_classical_perfection.py` and `tests/unit/test_horary.py` verify the bounded implementation, including orientation/search regressions. They do not by themselves validate every new source proposition in this packet. The source-owned pp.442-445 fixture is assignment evidence; it is not a full numerical or outcome golden. ## Independent fixture specification | Proposed family | Positive fixture | Negative/control | Boundary/adversarial fixture | |---|---|---|---| | Time/roles | E03 noon conversion; explicit turned relationship | Missing locality/clock; inappropriate role substitution | Date/year rollover, shared ruler, uncertain cusp | | Orbs/separation | P.110's printed Jupiter/Saturn example under its named set | Same geometry outside selected summed moiety | Each printed table, six arcminutes, exact contact, wraparound | | Reception | Explicit host/guest placements with a named table/sect | Reverse direction or disallowed translation basis | Mixed mutuality, dignity endpoint, dignity change before contact | | Moon/VOC | Precisely selected R11 interpretation and exception | A further qualifying application under that interpretation | Aspect before/after ingress; orb entry without in-sign exactitude | | Solar condition | Same-sign 8-degree separation | Same separation across sign boundary | 8 degrees 30 minutes, 17 minutes, 17 degrees, applying/separating | | Aspect judgement | Source-qualified square/opposition completion | Remove one required qualifier without changing exact event | Completion with regret; unknown strength/friendly-house meaning | | Translation/collection | P.111 numerical teaching structure; p.126 full conditions | Wrong receiver, intervening contact, missing history | Multiple simultaneous routes, state change between legs | | Blocking | Intended application reversed before contact | Irrelevant third contact; faster/slower alternative | No later exact pair event; tie within/equal/outside tolerance | | Search | Complete declared interval with all candidates | Incomplete input trace labelled unresolved | Event at each edge, station/ingress at contact, cross-window route | These are proposed fixture designs, not fabricated historical readings or passing tests. Historical case promotion follows the [catalogue contract](WORKED_CASES.md#fixture-promotion-contract). Numerical, doctrinal, compatibility and predictive validation must keep separate receipts.