Skip to content

savard_a_admission_failure_note

Jump to bottom
TheDaniel166 edited this page Oct 15, 2026 · 4 revisions

Savard-A Admission Failure Note

Status: not admitted

Purpose:

  • record why Savard-A fails Moira's current house-admission gate
  • prevent future drift from "interesting candidate" into implicit admission
  • preserve a clear re-entry path if stronger doctrine is later assembled

Decision

Savard-A is not admitted into Moira at this time.

This is not a judgment that the system is unreal or unworthy of study. It is a judgment that the current source packet does not yet satisfy the repository's admission standard for a new house system.

Governing Failure

The candidate fails on source sufficiency and derivation ownership.

More specifically:

  1. The governing geometry is only partially recoverable from the available packet.
  2. The recovered primary exposition is comparative and terse, not a stable formal derivation.
  3. The naming/provenance chain is explicitly corrective and software-mediated.
  4. A clean-room implementation attempted now would carry high Swiss-lineage risk, because software behavior would inevitably bear too much of the proof burden.

What Was Recovered

The current source packet is documented in:

That packet establishes:

  • Savard-A is a distinct modern software-recognized system
  • Astrolog and Swiss/Astrodienst operationalize it
  • John Savard's own page describes a Campanus-adjacent geometry using declination-parallel structure rather than direct prime-vertical trisection

That packet does not establish strongly enough:

  • a fully explicit mathematical construction
  • branch doctrine
  • singularity doctrine
  • polar doctrine
  • a historically secure Albategnius attribution

Failure Against Moira Admission Criteria

1. Ontology ownership: fails

We do not yet have a stable Moira-owned governing object.

Current recovered wording suggests a family resemblance:

  • prime-vertical related
  • declination-parallel mediated
  • horizon-anchored great-circle projection

But that is still not precise enough to say:

  • what the exact division object is
  • which derived points are first-class
  • which great circles are canonical
  • whether equivalent constructions really are equivalent in all cases

2. Derivation ownership: fails

We do not yet have a derivation that can be defended without leaning on software summaries or table outputs.

Savard's page is valuable, but still explanatory rather than exact. It leaves enough ambiguity that the implementation would need reconstruction decisions not frozen by source.

3. Structural ownership: blocked

Because the derivation is underdetermined, any implementation now would be at serious risk of unconsciously inheriting Swiss/Astrolog structure:

  • helper boundaries
  • branch selection
  • polar behavior
  • projection sequence
  • cusp assembly order

That is exactly the kind of failure the Swiss-smell rules were written to stop.

4. Policy ownership: fails

No explicit branch doctrine is yet assembled for:

  • ambiguous constructions
  • degeneracies
  • projection edge cases
  • polar/high-latitude behavior

Without that, any implementation would be forced to invent policy while coding.

5. Validation ownership: fails

External tables exist, but they are not enough.

If implemented now, the proof posture would collapse into:

  • "matches Savard-A tables"
  • "matches Astrolog"
  • "matches Swiss"

That is corroboration only. It is not sufficient primary proof under Moira's ownership standard.

Provenance Failure

The candidate also fails historical/provenance stability.

Current truth:

  • the system is now honestly called Savard-A
  • the old Albategnius attribution is not trustworthy
  • the name correction itself arose through modern software-community review

This does not disqualify the method forever, but it means Moira must not admit it under a false classical aura.

Why This Is A Failure Note And Not A Rejection Forever

The failure is conditional, not permanent.

The system may become admissible later if the doctrine packet improves enough. At present, however, the honest status is:

  • plausible candidate
  • insufficiently frozen
  • not ready for code

Re-entry Conditions

Savard-A may be reconsidered only if all of the following are completed:

  1. Reconstruct the governing geometry in exact Moira terms from the recovered Savard exposition.
  2. Identify and freeze every ambiguity left unresolved by the Savard page.
  3. Declare branch, singularity, and polar doctrine before implementation.
  4. Show a derivation path that does not require Swiss/Astrolog executable shape to fill in missing mathematics.
  5. Only then draft a formal admission doctrine and runtime design note.

Operational Consequence

No code implementation should begin from this packet alone.

If future work resumes, it must begin with a doctrine reconstruction note, not with constants.py or houses.py.

Sources

Clone this wiki locally