Measured
Produced from an observation or computation with a stated method, source, and time context.
BeamDesk keeps source, method, epoch, and uncertainty close to consequential outputs. Trust comes from visible boundaries—not from flattening every input into one confident-looking value.
A label is not a promise of equal certainty. It tells the reader how the value entered the system and which follow-up question to ask before relying on it.
Produced from an observation or computation with a stated method, source, and time context.
Supported by a public or access-controlled record whose citation remains attached.
Produced by BeamDesk modelling or an explicit assumption, rather than retrieved as fact.
Incomplete, bounded by unresolved conditions, or not yet offered for reliance.
An orbital score changes when the registered fleet or elements change. BeamDesk therefore treats fleet identity and epoch as part of the result, not as background implementation detail.
Coverage, valuation, and matching outputs retain the fleet epoch used to compute them. Scores from different epochs should not be compared as though the sky were unchanged.
When a required real fleet is missing, fleet-dependent coverage and scoring refuse the request. Unrelated marketplace routes can remain available without silently mixing mock and real data.
The public listing API omits owner identity and exact parcel boundaries. It rounds parcel centroids to two decimal degrees—about one kilometre—so an integration can find regional capacity without exposing a contactable property.
Listing documents are encrypted at rest with AES-256-GCM and have no plaintext storage fallback. Metadata listing and document reads are separate; content access is membership or internal-role checked and recorded in the audit log.
Rated power describes the active design condition. Average delivery incorporates how often geometry and schedule make that condition available. BeamDesk labels the basis so the two are not substituted.
Standards and exposure screens expose assumptions and cited editions. They do not replace site measurement, regulator review, licensing, or jurisdiction-specific advice.
Applicable limits, allocations, approvals, and evidence requirements depend on place, frequency, project design, and current rules. Unresolved conditions remain visible as constraints.
Report a security issue privately, without secrets in a public issue.
Use the configured security contact for suspected vulnerabilities or data-exposure concerns. Do not include credentials, API keys, session tokens, sign-in links, or sensitive documents in an initial report.