moira

Generated Physical Heliacal-Visibility API Inventory

Generated from current object identity and moira_server.app.create_app().openapi() by scripts/generate_physical_visibility_inventory.py. Do not edit this file by hand.

Python object identity

Symbol moira.heliacal owner moira root moira.facade moira.sky.visibility
PhysicalVisibilityStatus yes yes yes yes
PhysicalVisibilityEvidenceState yes yes yes yes
PhysicalVisibilityPhase yes yes yes yes
PhysicalVisibilityCrossingDirection yes yes yes yes
PhysicalVisibilityBoundarySource yes yes yes yes
PhysicalEventTimeSemantics yes yes yes yes
PhysicalBackgroundScope yes yes yes yes
PhysicalBackgroundComponentKind yes yes yes yes
PhysicalAtmosphereInput yes yes yes yes
PhysicalDirectionalBackground yes yes yes yes
PhysicalModeledBackgroundComponent yes yes yes yes
PhysicalSqmBackground yes yes yes yes
PhysicalBortleBackground yes yes yes yes
PhysicalHorizonSample yes yes yes yes
PhysicalHorizonProfile yes yes yes yes
PhysicalVisibilityPolicy yes yes yes yes
VisibilityComponentReceipt yes yes yes yes
PhysicalAtmosphereReceipt yes yes yes yes
PhysicalValidityDomainReceipt yes yes yes yes
PhysicalObserverProtocolReceipt yes yes yes yes
PhysicalBackgroundReceipt yes yes yes yes
PhysicalTargetReceipt yes yes yes yes
PhysicalThresholdReceipt yes yes yes yes
PhysicalVisibilityErrorBudgetReceipt yes yes yes yes
PhysicalVisibilityAssessment yes yes yes yes
PhysicalVisibilitySearchPolicy yes yes yes yes
PhysicalObservationWindowReceipt yes yes yes yes
PhysicalEventSolverReceipt yes yes yes yes
PhysicalEventSensitivityReceipt yes yes yes yes
PhysicalHorizonReceipt yes yes yes yes
PhysicalEphemerisReceipt yes yes yes yes
PhysicalVisibilityEventResult yes yes yes yes
VisibilityDataPackConfig yes yes yes yes
VisibilityDataPackReceipt yes yes yes yes
physical_visibility_assessment yes yes yes yes
physical_visibility_event yes yes yes yes

Facade methods

Both methods require data_pack_config as a keyword-only input. The event method also keeps the complete search policy keyword-only.

Dedicated REST operations

Method Path Operation ID Request schema Response schema
POST /v1/visibility/physical-assessment physical_visibility_assessment_route_v1_visibility_physical_assessment_post PhysicalVisibilityAssessmentRequest PhysicalVisibilityAssessmentResponse
POST /v1/visibility/physical-event physical_visibility_event_route_v1_visibility_physical_event_post PhysicalVisibilityEventRequest PhysicalVisibilityEventResponse

Server-owned pack configuration:

An unconfigured physical route returns the standard HTTP 503 server_not_configured error envelope. Physical request schemas contain no directory or data-pack path.

Preserved legacy REST operations

Method Path Operation ID
POST /v1/visibility/assessment visibility_assessment_route_v1_visibility_assessment_post
POST /v1/visibility/tonight visibility_tonight_route_v1_visibility_tonight_post
POST /v1/heliacal/visibility-event general_visibility_event_route_v1_heliacal_visibility_event_post

Private native substrate

These underscore-prefixed bindings are private implementation details. They do not own policy, pack admission, typed failures, event semantics, or result construction.

Explicitly absent public surfaces

No confidence score, client-supplied data-pack path request field, runtime libRadtran/MYSTIC operation, automatic downloader, site-specific experimental moonlight surface, or legacy-default replacement appears in the public inventory.