Treat research as a source lifecycle
OSINT runtime separates source discovery, qualification, ingestion and revalidation. Its documented behavior applies scoped policy, idempotent receipts, suppression filtering and evidence-backed assertions before projecting eligible facts into knowledge. Start with the source manifest and the policy that makes the source usable for the selected purpose. A recently discovered URL and an eligible, versioned evidence source are different states; preserve that difference in both the interface and downstream agent context.
Keep evidence and replay attached
Lifecycle mutations are revision-fenced and produce append-only receipts tied to the resulting source manifest. Lease and request bindings let durable workers resume interrupted work and recognize a committed transition. Knowledge projections retain source versions, evidence locators, grant references, purpose and index generation. Query receipts bind returned facts back to evidence and policy decisions. This provides a concrete review path: inspect the assertion, its selected source revision and the authority under which it entered the result set.
Separate application planning from effects
JobApplicationRuntime owns candidate-authorized lifecycle, field proposals, effect fences and replay. Its headless entry provides orchestration without requiring a UI module. The documented default is confirmation for each application; unsupported interactive challenges have no automatic bypass. Browser sessions, email, credentials, persistence and runtime execution remain injected boundaries. The candidate-private contracts and deletion-worker semantics make consent and recovery part of the same lifecycle instead of an afterthought in a connector.
Follow a practical path.
Inspect a source-backed fact
Follow discovery to qualification and ingestion, then inspect the fact’s source version, evidence locator and permitted purpose. Check how suppression, revalidation and source changes affect later retrieval.
Trace an application proposal
Locate the candidate scope, proposed field values and evidence, confirmation step and exact reserved effect. Identify the selected browser/email provider boundary before interpreting a proposal as a submitted application.
Review ambiguous completion
Inspect how a timed-out external action is reconciled using its existing receipt or fence. Verify the owning source’s deletion and retention flow separately from ordinary retry behavior; a repeated click should not be assumed to mean a safe repeat effect.