Complete static AstroBrain edition
The complete evidence story, without WebGL
Six composed states preserve the full case study for reduced motion, renderer fallback, printing, indexing, and conventional reading.
01 / 06
A living sky. An unresolved night.
Can this rig image this sky tonight?
- Scheduling window · fixture
- 2026-07-02 · 03:00–08:00 · 300 UTC date · UTC interval · minutes. The requested scheduling interval uses the recorded start, end, and duration. Window length is not planned exposure integration. Limitation: Reviewed planning-export window reused as a deterministic calculation input.
- Target · fixture
- NGC 7000 · North America Nebula catalog target. The deterministic case uses a named deep-sky target. The target identity is known; its apparent size is not supplied. Limitation: Rounded catalog coordinate for ephemeris spot checks.
02 / 06
From Andromeda to your horizon.
Where is tonight’s target in the local sky?
- Observer frame · calculated
- 32.2226; −110.9747; 728 degrees north; degrees east; meters. The site frame fixes latitude, longitude, and elevation. The observer frame exists, but the target cannot enter it without date-corrected coordinates. Limitation: Representative reference coordinate, not a private observing site.
- Horizon profile · fixture
- 4 azimuth/altitude points. The authored points close continuously across north. The profile validates interpolation; it is not a survey of the Tucson skyline. Limitation: Authored validation profile, not a survey of the Tucson skyline.
Scientific proof · Coordinate-frame proof
Status: calculated
Value: 32.2226; −110.9747; 728 degrees north; degrees east; meters
Source: AstroBrain services/ephemeris/fixtures.ts — REFERENCE_OBSERVER
Version: BUILD-007-HUS-36-reference-observer
Equation: H = LST − 15α; sin h = sin φ sin δ + cos φ cos δ cos H
Equation in words: Hour angle equals local sidereal angle minus fifteen times right ascension; altitude follows the spherical relation between latitude, declination, and hour angle.
- J2000 right ascension · fixture
- 20.9833 hours
- J2000 declination · fixture
- 44.3333 degrees
- observer latitude · fixture
- 32.2226 degrees north
- window start · fixture
- 2026-07-02T03:00:00.000Z UTC instant
- Result
- Missing · No checked apparent-of-date coordinate is supplied, so target altitude and azimuth remain missing.
Units: hours; degrees; ISO 8601 UTC instant
Assumptions: Right ascension uses hours and longitude is east-positive. UTC is the planning approximation to UT1 in the local helper.
Approximation: The local helper computes mean sidereal time and spherical horizontal geometry without refraction.
Limitation: Catalog J2000 is not substituted for precession, nutation, aberration, parallax, and refraction in this representative result.
Proof source: AstroBrain science documentation §§6.1–6.2; science.ts coordinate functions · missing
Version and tests: Target fixture MVP-005-E.2.6; coordinate edge cases are covered by astrobrainObservatoryScience.test.ts.
Scientific proof · Cyclic horizon and quality-floor proof
Status: fixture
Value: 4 azimuth/altitude points
Source: AstroBrain services/location/horizon-csv-parser.test.ts §4.1
Version: horizon-cardinal-cyclic-v1
Equation: h_effective(A) = max(30°, h_horizon(A))
Equation in words: The effective altitude floor equals the greater of thirty degrees and the interpolated local horizon altitude at the target azimuth.
- west horizon point · fixture
- 15 degrees altitude at 270°
- north horizon point · fixture
- 10 degrees altitude at 0°
- seam-check azimuth · calculated
- 315 degrees
- interpolated horizon at 315°
- 12.5 degrees altitude · calculated
Units: degrees azimuth; degrees altitude; seconds
Assumptions: Horizon points are globally increasing in azimuth and close cyclically across north. The checked interpolation is separate from target clearance, which requires target azimuth.
Approximation: The profile uses straight-line interpolation between authored points and one-minute target sampling.
Limitation: The four-point fixture is not surveyed terrain; target clearance remains missing because apparent-of-date geometry is absent.
Proof source: AstroBrain science documentation §§6.6 and 7.1–7.3; science.ts cyclic interpolation · calculated
Version and tests: Horizon version horizon-cardinal-cyclic-v1; seam and validation cases are covered by astrobrainObservatoryScience.test.ts.
Implementation proof · Coordinate service boundary
- Status
- implemented
- Value and units
- 32.2226; −110.9747; 728 degrees north; degrees east; meters
- Source
- AstroBrain services/ephemeris/fixtures.ts — REFERENCE_OBSERVER
- Version
- science.ts typed functions plus MVP-005-E.2.6 and astrobrainObservatoryScience.test.ts coordinate cases.
- Limitation
- Representative reference coordinate, not a private observing site.
- Architecture owner
- Catalog source versions and ephemeris service
- Typed input
- Equatorial input { rightAscensionHours, declinationDeg, observer latitudeDeg, longitudeDeg, instant }
- Typed output
- HorizontalCoordinate { altitudeDeg, azimuthDeg, hourAngleDeg } or explicit missing evidence before projection
- Provider boundary
- The reviewed product path assigns of-date astronomy to the ephemeris service; the presentation helper performs deterministic local geometry only.
- Persistence boundary
- Catalog source version and Session target/site versions persist separately from calculated samples.
- Failure behavior
- Invalid ranges throw validation errors; absent apparent-of-date evidence leaves all local target samples missing.
- Privacy and security
- Exact site coordinates remain owner-private and are not exposed by public/shared transfer objects.
Implementation proof · Location and horizon boundary
- Status
- local-first
- Value and units
- 4 azimuth/altitude points
- Source
- AstroBrain services/location/horizon-csv-parser.test.ts §4.1
- Version
- horizon-cardinal-cyclic-v1 and science/projection seam, ordering, cadence, and missing-target tests.
- Limitation
- Authored validation profile, not a survey of the Tucson skyline.
- Architecture owner
- Location domain, horizon versions, and deterministic horizon projection
- Typed input
- CyclicHorizon { interpolation: cyclic-linear, points[] } plus target azimuth samples
- Typed output
- Horizon altitude, effective floor, and nullable above-floor result for each UTC sample
- Provider boundary
- Horizon interpolation is local deterministic geometry and needs no external provider.
- Persistence boundary
- Local-first locations and horizon profiles can later become owner-scoped, versioned records.
- Failure behavior
- Too few, unordered, duplicated, or out-of-range points fail validation; missing target azimuth leaves clearance null.
- Privacy and security
- Opaque location identifiers, rather than coordinates, belong in tool URLs; public records cannot disclose exact private sites.
03 / 06
Evidence changes the night.
Which evidence narrows the usable night?
- Apparent-of-date coordinate · missing
- Value missing. The representative case has no checked apparent-of-date coordinate. Target altitude and azimuth remain unresolved. Limitation: The fixture does not contain a checked apparent-of-date coordinate; the direct J2000 projection is explicitly limited.
- Weather provider state · unavailable
- Value missing. No provider snapshot is attached to this deterministic case. Cloud, wind, humidity, and seeing cannot support a weather judgment. Limitation: No provider snapshot is attached to this deterministic case study.
Scientific proof · Atmospheric evidence proof
Status: missing
Value: Missing hours right ascension; degrees declination
Source: Representative observing decision fixture — evidence domain not supplied
Version: astrobrain-observatory-projection-v1
Equation: S_weather = 1 − mean(c_i / 100)
Equation in words: The weather component equals one minus the mean cloud-cover fraction across the requested samples.
- start cloud cover · unavailable
- missing percent
- end cloud cover · unavailable
- missing percent
- Moon evidence · missing
- missing degrees and illumination fraction
- Sun evidence · missing
- missing degrees altitude
- Result
- Missing · Weather score, astronomical darkness, and target–Moon interference cannot be calculated from this fixture.
Units: percent; meters per second; arcseconds; UTC instant
Assumptions: Cloud values must be complete finite percentages from 0 to 100. Missing weather is not equivalent to a clear sky.
Approximation: A cloud fraction is a planning component, not a guarantee of seeing, transparency, or local cloud timing.
Limitation: There is no provider snapshot, solar coordinate, Moon coordinate, illumination, or angular-separation evidence in the case.
Proof source: AstroBrain science documentation §§6.3, 6.5, 9.3, 19.1, and 21; projection.ts weather mapping · unavailable
Version and tests: Weather fixture weather-unavailable-v1; missing-provider preservation is covered by astrobrainObservatoryScience.test.ts.
Implementation proof · Weather policy and provenance boundary
- Status
- provider-derived
- Value and units
- Missing hours right ascension; degrees declination
- Source
- Representative observing decision fixture — evidence domain not supplied
- Version
- weather-unavailable-v1 plus fixture and science tests that preserve null provider records and WEATHER_UNAVAILABLE.
- Limitation
- The fixture does not contain a checked apparent-of-date coordinate; the direct J2000 projection is explicitly limited.
- Architecture owner
- Weather provider adapter, policy gate, cache, freshness, and provenance envelope
- Typed input
- Privacy-transformed site cell, UTC window, provider policy, and cache context
- Typed output
- Timestamped weather evidence records with units, status, source, version, and limitation
- Provider boundary
- External weather access receives an approximate 10 km, 20 km, or 50 km cell rather than the exact private coordinate.
- Persistence boundary
- Versioned weather snapshots are separate from the owner’s exact location and from the local draft.
- Failure behavior
- Disabled or unavailable service returns a labeled unavailable/degraded branch; no missing cloud value becomes zero.
- Privacy and security
- Provider calls use the privacy cell, telemetry rejects raw coordinates, and caches cannot cross site/night/privacy contexts.
04 / 06
The night lands on the sensor.
What does this instrument actually frame?
- Angular field · calculated
- 2.540057 × 1.697128 degrees. Rectilinear width and height are calculated from the fixture rig. Fit remains unresolved because target size and rotation are absent. Limitation: Pinhole/rectilinear approximation; distortion, vignetting, field curvature, and spacing error are excluded.
- Exposure walls · missing
- Value missing. The reviewed case lacks the physical inputs for both exposure bounds. No sub-exposure duration or operating band is reported. Limitation: No pixel pitch, read noise, full well, sky rate, star-peak rate, or workflow constraints exist in the reviewed fixture.
Scientific proof · Rectilinear field-of-view proof
Status: calculated
Value: 2.540057 × 1.697128 degrees
Source: AstroBrain services/scoring/framing-f001.test.ts — RIG; rectilinear FOV equation
Version: rig-f001
Equation: θ = 2 atan(s / 2f)
Equation in words: Field angle equals two times the arctangent of sensor size divided by two times focal length.
- sensor width · fixture
- 23.5 millimeters
- sensor height · fixture
- 15.7 millimeters
- focal length · fixture
- 530 millimeters
- horizontal × vertical field
- 2.540057 × 1.697128 degrees · calculated
Units: millimeters; degrees
Assumptions: Sensor and focal-length dimensions are positive finite values in the same length unit. Width and height are calculated independently with a rectilinear projection.
Approximation: The equation treats the system as a pinhole/rectilinear optical geometry.
Limitation: Distortion, vignetting, field curvature, tilt, spacing error, target size, and rotation are not included.
Proof source: AstroBrain science documentation §8.2; science.ts fieldOfViewDeg; projection.ts optical dimensions · calculated
Version and tests: Rig version rig-f001; the representative values and invalid inputs are covered by astrobrainObservatoryScience.test.ts.
Scientific proof · Exposure operating-band proof
Status: missing
Value: Missing seconds
Source: Representative observing decision fixture — evidence domain not supplied
Version: astrobrain-observatory-projection-v1
Equation: t_low = max(C RN² / K, η_min o / (1 − η_min)); t_high = min(FW h / (S_p + K), FW f_s / K)
Equation in words: The lower exposure wall is the greater noise or efficiency bound; the upper wall is the lesser saturation or sky-well bound.
- read noise · missing
- missing electrons
- sky rate · missing
- missing electrons per pixel per second
- full well · missing
- missing electrons
- workflow overhead · missing
- missing seconds
- Result
- Missing · Neither exposure wall can be calculated, so no clean operating band or compromise duration is reported.
Units: electrons; electrons per pixel per second; seconds; dimensionless fraction
Assumptions: Rates and capacities must be positive; overhead is non-negative; fractional limits lie strictly between zero and one. The selected binning and camera mode must match the physical workflow.
Approximation: The band balances a read-noise planning model, workflow efficiency, saturation, and sky-well limits.
Limitation: A calculated band would still exclude pattern noise, gradients, calibration error, tracking loss, and sensor-mode variation.
Proof source: AstroBrain science documentation §§13.1–13.11; science.ts exposureOperatingBand · missing
Version and tests: Projection version astrobrain-observatory-projection-v1; formula and collision cases are covered by astrobrainObservatoryScience.test.ts.
Implementation proof · Rig geometry boundary
- Status
- implemented
- Value and units
- 2.540057 × 1.697128 degrees
- Source
- AstroBrain services/scoring/framing-f001.test.ts — RIG; rectilinear FOV equation
- Version
- rig-f001, projection optical records, and field-of-view formula/validation tests in astrobrainObservatoryScience.test.ts.
- Limitation
- Pinhole/rectilinear approximation; distortion, vignetting, field curvature, and spacing error are excluded.
- Architecture owner
- Equipment versions and field-of-view geometry service
- Typed input
- Positive finite sensor width/height and focal length in millimeters
- Typed output
- Horizontal and vertical EvidenceRecord<number> values in degrees
- Provider boundary
- Field-of-view calculation is pure local geometry; approved imagery remains a separate display provider boundary.
- Persistence boundary
- The rig version supplies calculation inputs; a Session snapshot links that version rather than copying mutable current equipment.
- Failure behavior
- Zero, negative, or non-finite dimensions are rejected; absent target size prevents a framing-fit result.
- Privacy and security
- Owner-scoped rigs require authorization for server mutation; identifiers alone do not grant access.
Implementation proof · Exposure recipe boundary
- Status
- preconditioned
- Value and units
- Missing seconds
- Source
- Representative observing decision fixture — evidence domain not supplied
- Version
- science.ts ExposureBandInput/ExposureBand and operating-band validation/collision tests.
- Limitation
- No pixel pitch, read noise, full well, sky rate, star-peak rate, or workflow constraints exist in the reviewed fixture.
- Architecture owner
- Recipe service and validated exposure calculation
- Typed input
- ExposureBandInput with read noise, rates, full well, overhead, headroom, sky-well, and efficiency constraints
- Typed output
- ExposureBand with named lower/upper walls, clean flag, compromise, and reason codes
- Provider boundary
- The deterministic band has no provider dependency once checked camera, workflow, and sky inputs are supplied.
- Persistence boundary
- Tool drafts may be local-first or owner-scoped; a confirmed recipe belongs with a version-linked plan context.
- Failure behavior
- Invalid physical inputs throw; conflicting walls return NO_CLEAN_EXPOSURE_BAND; incomplete fixture inputs produce missing evidence.
- Privacy and security
- State-changing recipe or draft routes require validation and the configured same-origin request gate.
05 / 06
The recommendation reveals its construction.
How is the recommendation constructed?
- Score output · calculated
- 0; 0.15 points; evidence-completeness index. No score component applies, so the display fallback is zero and completeness is low. The zero is not a poor-target verdict or success probability. Limitation: Later calculations must expose omissions and hard-rejection reason codes.
- Domain ownership map · calculated
- 9 physical-to-software mappings. Each evidence layer has a named service or persistence owner. One unavailable provider domain does not erase unrelated evidence. Limitation: not currently claimed: Provider, map, identity, database, or network failure degrades the affected branch and must not produce a false saved or favorable state.
Scientific proof · Explainable score proof
Status: calculated
Value: 0; 0.15 points; evidence-completeness index
Source: AstroBrain complete feature and science documentation §10.3
Version: score-model-visible-v0
Equation: S = 100 × Σ(w_i c_i) / Σ(w_i), over applied components only
Equation in words: The target score equals one hundred times the weighted sum of supported components divided by their applied weights.
- applied components · calculated
- 0 count
- weather component · unavailable
- missing normalized score [0,1]
- other components · missing
- missing normalized score [0,1]
- display fallback with no applied component
- 0 points [0,100] · calculated
Units: points [0,100]; normalized score [0,1]; dimensionless weight
Assumptions: Only finite supported component values in [0,1] enter the weighted mean. A maximum altitude below 30° is the sole hard rejection and is not established here.
Approximation: The seven-component model is a documented decision heuristic, with omitted weights renormalized.
Limitation: The zero is not evidence that NGC 7000 is poor; every component is omitted and the confidence index is 0.15.
Proof source: AstroBrain science documentation §§10.1–10.9; science.ts scoreTarget · calculated
Version and tests: Model version score-model-visible-v0; omissions and reason codes are covered by astrobrainObservatoryScience.test.ts.
Scientific proof · Evidence-completeness proof under domain failure
Status: calculated
Value: 9 physical-to-software mappings
Source: AstroBrain Evidence Observatory design §6.9
Version: astrobrain-observatory-projection-v1
Equation: C_e = clamp(1 − 0.25 W_d − 0.10 N_o, 0, 1)
Equation in words: Evidence completeness equals one minus weather and omission penalties, clamped between zero and one.
- weather degraded indicator · calculated
- 1 binary indicator
- omitted non-weather components · calculated
- 6 count
- evidence-completeness index
- 0.15 normalized index [0,1] · calculated
Units: normalized index [0,1]; binary indicator; count
Assumptions: Unavailable weather degrades the result without supplying a favorable value. Each missing non-weather component applies the current model’s 0.10 completeness deduction.
Approximation: The index is a presentation of evidence coverage under the current visible score model.
Limitation: The index is not a probability of clear skies, successful capture, or image quality.
Proof source: science.ts scoreTarget confidence calculation; AstroBrain science documentation §§10 and 21 · calculated
Version and tests: Model version score-model-visible-v0; unavailable-weather isolation is covered by astrobrainObservatoryScience.test.ts.
Implementation proof · Scoring and reason-code boundary
- Status
- modeled estimate
- Value and units
- 0; 0.15 points; evidence-completeness index
- Source
- AstroBrain complete feature and science documentation §10.3
- Version
- score-model-visible-v0 plus component, hard-floor, omission, weather, and confidence tests.
- Limitation
- Later calculations must expose omissions and hard-rejection reason codes.
- Architecture owner
- Scoring model version, model card, score vector, omissions, and reason codes
- Typed input
- ScoreTargetInput with nullable geometry/darkness and seven nullable component values
- Typed output
- ScoreResult with score, rejection, interpretation, completeness, component applications, and reasons
- Provider boundary
- Weather may enter through its adapter; all other component values arrive through named domain services rather than an opaque ranker.
- Persistence boundary
- Recommendation runs can retain model version, provenance envelope, context snapshot, score vector, and exclusions.
- Failure behavior
- Unsupported values are rejected; unavailable fields withdraw; no applied component returns a degraded zero with MISSING_EVIDENCE.
- Privacy and security
- Scientific score inputs exclude paid influence and unverified preference signals; owner context remains scoped.
Implementation proof · Application ownership boundary
- Status
- not currently claimed
- Value and units
- 9 physical-to-software mappings
- Source
- AstroBrain Evidence Observatory design §6.9
- Version
- projection.ts ownership map v1 and documentation §§17–21; implementation depth outside current tests is not currently claimed.
- Limitation
- not currently claimed: Provider, map, identity, database, or network failure degrades the affected branch and must not produce a false saved or favorable state.
- Architecture owner
- Next.js interface, validated application APIs, domain services, local stores, and owner-scoped database
- Typed input
- Validated request context and typed domain payload with source/version references
- Typed output
- Evidence envelope or an explicit loading, missing, unavailable, stale, degraded, conflict, or error state
- Provider boundary
- Weather and approved sky displays are constrained adapters; identity is optional for core local use and required for owned cloud data.
- Persistence boundary
- Browser-local drafts and Workers sit outside PostgreSQL/PostGIS; validated APIs mediate owned persistence and migration.
- Failure behavior
- Provider, map, identity, database, or network failure degrades the affected branch and must not produce a false saved or favorable state.
- Privacy and security
- Same-origin mutation gates, owner scoping, redacted allowlisted telemetry, and route-scoped content security policy protect boundaries.
- Catalog and coordinate frames
- Catalog schema, source versions, ephemeris service · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Site, horizon, privacy cell
- Location domain, horizon versions, privacy transformation · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Moon, weather, and freshness
- Provider adapter, policy gate, cache, provenance envelope · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Optics, sampling, and back focus
- Equipment versions, FOV and focal-plane services · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Exposure operating band
- Recipe service and validated server calculation · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Target score
- Scoring model version, model card, score vector, omissions, reason codes · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Active draft
- Browser-local store or owner-scoped tool/Session API · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Historical plan
- PostgreSQL Session, immutable context snapshots, revisions · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
- Captured result
- Browser Worker, aggregate FITS metadata, outcome and quality summaries · AstroBrain Evidence Observatory design §6.9 · astrobrain-observatory-projection-v1
06 / 06
Plan the night. Know why.
What does the evidence establish—and withhold?
- Angular field · calculated
- 2.540057 × 1.697128 degrees. Rectilinear width and height are calculated from the fixture rig. Fit remains unresolved because target size and rotation are absent. Limitation: Pinhole/rectilinear approximation; distortion, vignetting, field curvature, and spacing error are excluded.
- Weather provider state · unavailable
- Value missing. No provider snapshot is attached to this deterministic case. Cloud, wind, humidity, and seeing cannot support a weather judgment. Limitation: No provider snapshot is attached to this deterministic case study.
Scientific proof · Planned-versus-actual duration proof
Status: calculated
Value: 2.540057 × 1.697128 degrees
Source: AstroBrain services/scoring/framing-f001.test.ts — RIG; rectilinear FOV equation
Version: rig-f001
Equation: ΔT = T_actual − T_planned
Equation in words: Duration difference equals actual captured integration minus planned integration.
- scheduling window duration · fixture
- 300 minutes
- planned integration · missing
- missing minutes
- actual captured integration · missing
- missing minutes
- Result
- Missing · Planned and actual integration are both missing, so their duration difference remains unresolved.
Units: minutes
Assumptions: Planned and actual integration must refer to compatible target and Session context. An actual value enters only after explicit aggregate confirmation.
Approximation: Duration comparison records quantity only; it does not measure calibration or image quality.
Limitation: The representative Session is an authored snapshot, not evidence of capture or a saved observing outcome.
Proof source: AstroBrain science documentation §§4.9–4.10 and 16.3; fixture.ts Session snapshot · missing
Version and tests: Session snapshot session-snapshot-representative-v1; reference-link validation is covered by astrobrainObservatoryFixture.test.ts.
Implementation proof · Session snapshot and revision boundary
- Status
- local-first
- Value and units
- 2.540057 × 1.697128 degrees
- Source
- AstroBrain services/scoring/framing-f001.test.ts — RIG; rectilinear FOV equation
- Version
- session-snapshot-representative-v1 references six source versions; fixture validation tests enforce linkage and immutability.
- Limitation
- Pinhole/rectilinear approximation; distortion, vignetting, field curvature, and spacing error are excluded.
- Architecture owner
- Planning Session, immutable context snapshots, revisions, and aggregate outcome records
- Typed input
- Version-linked target, site, rig, horizon, weather, model, night, intent, and optional confirmed outcome aggregate
- Typed output
- Owner-scoped Session snapshot with lifecycle, revision, conflict, and outcome state
- Provider boundary
- Local browser parsing can produce approved aggregate metadata; only confirmed aggregates cross into owned Session records.
- Persistence boundary
- Anonymous drafts remain local-first until explicit migration; PostgreSQL holds owner-scoped Sessions, snapshots, revisions, and outcomes.
- Failure behavior
- Conflicting writes are rejected for reconciliation; partial migration leaves failed records local; too-small quality samples are withheld.
- Privacy and security
- Pixels, filenames, free-form file content, exact coordinates, and secrets stay outside telemetry and canonical aggregate records.
Ten technical topic areas
Target
- Status
- fixture
- Value
- NGC 7000 · North America Nebula
- Units
- catalog target
- Source
- AstroBrain services/ephemeris/fixtures.ts — SIMBAD J2000 / Stellarium catalog snapshot
- Version
- MVP-005-E.2.6
- Limitation
- Rounded catalog coordinate for ephemeris spot checks.
Scheduling window
- Status
- fixture
- Value
- 2026-07-02 · 03:00–08:00 · 300
- Units
- UTC date · UTC interval · minutes
- Source
- AstroBrain specs/251-plan-popcard-redesign/evidence-r2/astrobrain-ngc-7000-north-america-nebula-2026-07-02.json
- Captured at / freshness
- 2026-07-02T23:11:25.589Z
- Version
- night-window-2026-07-02T03:00Z-300m
- Limitation
- Reviewed planning-export window reused as a deterministic calculation input.
Observer frame
- Status
- calculated
- Value
- 32.2226; −110.9747; 728
- Units
- degrees north; degrees east; meters
- Source
- AstroBrain services/ephemeris/fixtures.ts — REFERENCE_OBSERVER
- Version
- BUILD-007-HUS-36-reference-observer
- Limitation
- Representative reference coordinate, not a private observing site.
Horizon profile
- Status
- fixture
- Value
- 4
- Units
- azimuth/altitude points
- Source
- AstroBrain services/location/horizon-csv-parser.test.ts §4.1
- Version
- horizon-cardinal-cyclic-v1
- Limitation
- Authored validation profile, not a survey of the Tucson skyline.
Apparent-of-date coordinate
- Status
- missing
- Value
- Missing
- Units
- hours right ascension; degrees declination
- Source
- Representative observing decision fixture — evidence domain not supplied
- Version
- astrobrain-observatory-projection-v1
- Limitation
- The fixture does not contain a checked apparent-of-date coordinate; the direct J2000 projection is explicitly limited.
Weather provider state
- Status
- unavailable
- Value
- Missing
- Units
- provider snapshot
- Source
- AstroBrain complete feature and science documentation §§4.2 and 22
- Version
- weather-unavailable-v1
- Limitation
- No provider snapshot is attached to this deterministic case study.
Angular field
- Status
- calculated
- Value
- 2.540057 × 1.697128
- Units
- degrees
- Source
- AstroBrain services/scoring/framing-f001.test.ts — RIG; rectilinear FOV equation
- Version
- rig-f001
- Limitation
- Pinhole/rectilinear approximation; distortion, vignetting, field curvature, and spacing error are excluded.
Exposure walls
- Status
- missing
- Value
- Missing
- Units
- seconds
- Source
- Representative observing decision fixture — evidence domain not supplied
- Version
- astrobrain-observatory-projection-v1
- Limitation
- No pixel pitch, read noise, full well, sky rate, star-peak rate, or workflow constraints exist in the reviewed fixture.
Score output
- Status
- calculated
- Value
- 0; 0.15
- Units
- points; evidence-completeness index
- Source
- AstroBrain complete feature and science documentation §10.3
- Version
- score-model-visible-v0
- Limitation
- Later calculations must expose omissions and hard-rejection reason codes.
Domain ownership map
- Status
- calculated
- Value
- 9
- Units
- physical-to-software mappings
- Source
- AstroBrain Evidence Observatory design §6.9
- Version
- astrobrain-observatory-projection-v1
- Limitation
- not currently claimed: Provider, map, identity, database, or network failure degrades the affected branch and must not produce a false saved or favorable state.