Notice the change. Keep the context.

A funding call opens with a deadline and a set of eligibility criteria. A supplier changes its terms. A regulation is amended. A competitor drops a price. None of these arrive in your inbox.

Planning notice

Before

Community workshop

Applications close

Now

Community workshop

Applications close

Source and previous version kept
Follow the sourceKeep watch on the things that matter.
Keep the evidenceReturn to what actually changed.

Illustrative comparison · example dates

The situation

Every organization depends on facts it does not own, published by parties who have no obligation to tell it when they change. Noticing is somebody's informal responsibility until that person is busy, and then noticing stops happening at exactly the moment it matters.

How this usually goes

  • Monitoring is a browser bookmark and good intentions.

  • Someone builds a script, it breaks quietly, and its silence is read as no news.

  • The opportunity is found after the deadline, or the rule change after the breach.

  • When something is caught, there is no record of what the source said before, so the claim is unprovable.

What happens here

  • 1. The subject is registered, not the mechanics

    Someone states what should be watched and how often, in terms of the thing itself. Scheduling, retries, rate discipline, and failure handling belong to the collection runtime.

  • 2. Failure is visible

    A run that could not complete is recorded as a failed run. Silence is never allowed to look like stability, which is the defect that makes most homemade monitoring worse than none.

  • 3. Evidence is kept as observed

    What the source said, when, and where it came from, stored so that a later claim can be checked against the thing rather than against a summary of it.

  • 4. Changes become findings

    Raw observations are scored into opportunities, matches, and obligations by rules that can be inspected and argued with, rather than by judgment applied privately.

  • 5. Findings leave as events

    An alert publishes to the shared backbone, so foresight work, procurement, compliance, finance, or a governed automation can each act on it without a private integration.

From finding to action

An opportunity with evidence attached is already most of an application: the criteria as published, the date they were published, and what the organization has that matches. The same pipeline that catches a tender in time is the one that can show, months later, exactly what the rules said on the day the decision was made.

Which parts of the system