Source-validity definitions describe when explicitly qualified observations may support a native decision. They preserve original observation time and lifecycle, including withdrawal and supersession. Ordinary spreadsheet columns or a recent page refresh do not establish this authority.
Define and challenge the validity rule
Use the Source validity definition workflow for the agreed observation contract and completeness meaning. Enter independent expected examples with complete observation and source-state inputs. Times are whole UTC Unix seconds used as deliberate case facts, not live production observations.
Cover ages just below, exactly at and just above the limit. Add withdrawal, supersession, incomplete or missing observations, expired data and tighter native source restrictions. Supply expected eligibility, refusal reasons in the required order and expected age independently of the rule.
Save expected examples and Verify saved examples. Inspect the complete proof and obtain the independent definition review before using that exact revision in a product binding.
Bind exact enrolled sources
From the requirement, use Use a source-validity definition and inspect the selected native target and draft. Choose the reviewed definition and enrolled observation sources. Review complete binding, including source contract, registration revision, definition identity and native context.
Save the reviewed binding into a native draft through the explicit supported action. It cannot silently invent a missing native source policy or alter unrelated rules. A changed source, registration or draft can require current rebinding before qualification and publication.
Preserve native safeguards
Complete the native independent cases, proof, review and release. The organisational rule adds restrictions. It cannot relax source permissions, freshness, error states, restore holds or the product's own conditions.
An invalid or withdrawn observation should block the qualified work, rather than becoming a successful empty result. Original replay does not renew observation age. After restore, preserve original timestamps and lifecycle and follow the source product's current enrolment and recovery requirements. Use Activate and recover original requests for uncertain binding commands.