Primary Directions Constitutional Alignment

Purpose

This document records the constitutional status of the major doctrine-owning subsystems inside Moira's primary-directions engine.

It exists to answer one question clearly:

• which internal subsystems are aligned enough for Phase 10 hardening, and which still need packet cleanup before top-level freeze?

Alignment Rule

An internal primary-directions subsystem is constitutionally aligned when:

• its current admitted surface is stated explicitly
• its phase language does not contradict the top-level packet
• its public policy boundary is visible
• its validation expectations are visible enough to support hardening

Subsystem Status

Methods

• current state:
  • explicit method doctrine exists
  • sovereignty status is explicit
  • consumer runtime excludes non-verified Porphyry
• alignment judgment:
  • aligned through P10 on the current admitted surface
• remaining work:
  • keep the backend standard and truth cards consistent with the admitted method set

Spaces

• current state:
  • In Mundo and In Zodiaco are admitted
  • Field Plane remains explicitly deferred
• alignment judgment:
  • aligned through P10
• remaining work:
  • none required before freeze beyond packet consistency

Converse Doctrine

• current state:
  • Direct and Traditional converse are admitted
  • Neo-converse remains research-only
• alignment judgment:
  • aligned through P10
• remaining work:
  • none required before freeze beyond keeping Neo-converse outside the admitted surface

Keys

• current state:
  • Ptolemy, Naibod, Cardan, and Solar are admitted explicitly
• alignment judgment:
  • aligned through P10
• remaining work:
  • update any stale standards that still speak of an older admitted trio

Relations

• current state:
  • conjunction, opposition, zodiacal aspect, parallel, contra-parallel, rapt parallel, antiscion, and contra-antiscion are explicit
• alignment judgment:
  • aligned through P10
• remaining work:
  • keep branch presets and truth cards explicit about active relation sets

Targets

• current state:
  • base families are explicit
  • narrow derived families are relation-gated and preset-gated
• alignment judgment:
  • aligned through P10 on the admitted recoverable surface
• remaining work:
  • maintain the target-family matrix as the governing frontier boundary

Perfections

• current state:
  • mundane, zodiacal longitude, and zodiacal projected perfection are explicit
• alignment judgment:
  • aligned through P10
• remaining work:
  • ensure the backend standard names all three current perfection surfaces

Latitude Doctrine

• current state:
  • zodiacal latitude doctrines are explicit and used in admitted branches
• alignment judgment:
  • aligned through P10
• remaining work:
  • keep field_plane excluded until its separate doctrine is recoverable

Latitude Sources

• current state:
  • admitted latitude-source families are explicit
• alignment judgment:
  • aligned through P10
• remaining work:
  • none beyond consistent documentation

Branch Presets

• current state:
  • named presets now select the documented runtime surfaces directly
• alignment judgment:
  • aligned through P10
• remaining work:
  • ensure top-level doctrine and standard treat presets as part of the constitutional surface, not convenience only

Validation Surface

• current state:
  • targeted tests exist
  • fixture-backed validation exists for admitted narrow families
  • curated public API checks exist
• alignment judgment:
  • substantively aligned for P10
• remaining work:
  • update the top-level backend standard so its validation codex reflects the actual subsystem breadth

Top-Level Judgment

Primary directions is now constitutionally aligned across its internal doctrine-owning subsystems on the current admitted recoverable surface.

What had remained out of alignment was mainly the packet narrative:

• stale narrow-branch freeze language
• stale backend standard scope
• stale top-level phase claims

That alignment work is now complete for the current freeze surface.

Policy Consequence

The correct policy line is:

Primary directions is baseline-complete on the currently recoverable doctrinal surface, and its internal doctrine-owning subsystems are aligned enough for constitutional freeze. Final Phase 11 and Phase 12 closure on the current admitted surface now rests on packet consistency, not on new feature breadth.