Trust · Provenance and boundaries

Know what a number is before you act on it.

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.

Provenance system

Evidence classes stay visible.

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.

Measured

Measured

Produced from an observation or computation with a stated method, source, and time context.

Documented

Documented

Supported by a public or access-controlled record whose citation remains attached.

Estimated

Estimated

Produced by BeamDesk modelling or an explicit assumption, rather than retrieved as fact.

Provisional

Provisional or constrained

Incomplete, bounded by unresolved conditions, or not yet offered for reliance.

Orbital data

Comparable only inside the same sky.

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.

Fleet epochs

Every match belongs to an epoch

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.

Provider degradation

Unavailable is a valid answer

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.

Privacy and documents

Public discovery stops before private evidence begins.

Public parcel data

Approximate enough to discover

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.

Document storage

Encrypted, authorized, and audited

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.

Encryption key continuity matters: changing or losing the configured document key makes existing encrypted uploads unreadable.
Interpretation boundaries

Design values, time averages, and legal conclusions are different things.

Power basis

Rated is not average

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.

Screening

A constraint result is not a permit

Standards and exposure screens expose assumptions and cited editions. They do not replace site measurement, regulator review, licensing, or jurisdiction-specific advice.

Uncertainty

Regulation can change

Applicable limits, allocations, approvals, and evidence requirements depend on place, frequency, project design, and current rules. Unresolved conditions remain visible as constraints.

Security contact
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.

Operational trust

Carry the source and the boundary into every decision.

Request access to evaluate how BeamDesk presents provenance, constraints, and degraded data in the operating workflow.
Trust and provenance — BeamDesk