Data Confidence Help

• validated: bundled row passed project validation checks at load time (dataset integrity in this app)—not third-party certification of your facility values.
• reference-derived: derived from cited sources but still context-dependent.
• illustrative: demonstration/training value, not operationally verified.
• user-supplied: entered by user; requires source documentation.
• placeholder: temporary value requiring replacement before operational reliance.

Confidence labels are transparency signals. They do not automatically convert screening tools into certified analysis engines.

Illustrative and placeholder values should not be used for operational dose assignment or formal compliance decisions.

User-supplied entries require source notes so reports preserve where/why values were selected.

Optional reference IDs (lowercase slug style where enforced) tie a value to a worksheet, procedure paragraph, dataset row, or internal tracking code. They do not replace full citations, but they keep exports greppable and consistent across JSON and Markdown.

Structured reference objects in reports summarize title, organization, URL (when present), and confidence. They explain what was consulted—not that an external body endorsed the screening result.

Nuclide half-lives, decay descriptions, illustrative gamma constants, and similar fields come from validated rows bundled with the app (for example public/data/nuclides.json). Calculators may add a stable nuclide id and catalog symbol to exports when your selection matches that dataset.

If a row is missing a value your procedure needs (for example no tabulated gamma constant), enter a user-supplied value and document the source in the report notes or reference fields—exports should remain traceable.

Bundled values are the fields stored on each catalog row (half-life, listed photon energies, tabulated gamma constants where present, and optional confidence or provenance notes). User-supplied values are anything you type in the workspace—overrides of a tabulated constant, screening numbers carried over when you change nuclide, or coefficients pasted from your own reference set.

Missing optional catalog fields do not always block every tool: for example decay math can still use a bundled half-life when photon energies are not listed, while point-source screening may require you to supply and document a gamma constant when the row has none. Each calculator and export path applies its own readiness rules.

When a value is manual or retained (not implied to be the catalog constant for the selected nuclide), treat it like any other user-supplied input: add a short source note so JSON, Markdown, or copied summaries stay traceable—especially when exports are gated until that documentation exists.