Public updates · Source boundaries

How public updates are checked

Auctrix uses two scheduled workflows to keep public information inside configured sources, evidence, and publishing rules.

This source-check method is separate from Auctrix’s consulting methodology, Frame → Align → Deliver.

Weekly snapshots

Monday · 09:00 UTC

Fintech and open-source source checks.

Bounded content

Daily · 07:00 UTC

Runs only when the owner-enabled policy, active topics, and active sources are in place.

Two scheduled workflows

Each publication path has its own evidence gate.

Monday · 09:00 UTC

Fintech and open-source snapshots

The weekly check uses each snapshot’s configured source and allowed domains. A result must be attributable; competing results must agree before one source is selected.

Each result must be attributable to a configured source and stay within that snapshot’s allowed domains.
The source page must load over HTTPS and contain readable content with the configured evidence term or terms.
The source content must be fresh at check time (no older than eight days) and complete rather than truncated.

When a source is unavailable, ambiguous, conflicting, stale, unreadable, or outside its boundary, the snapshot is reported as unavailable. That check does not create a new verified claim.

Daily · 07:00 UTC

Bounded informational and educational content

This workflow runs only when automatic publishing is enabled by the owner and at least one active topic and source are configured. Source evidence must be current (within eight days), readable, served over HTTPS, and within the approved source boundary.

The source must be current, readable, available over HTTPS, and inside its approved host or exact-URL boundary.
A draft is created from that source and validated as bounded informational or educational content.
Failed source evidence stays unpublished. A sensitive-flagged draft waits for explicit owner approval; other eligible verified items may publish automatically.

Visible source information

Readers can follow the source on each surface.

Fintech and open-source snapshots

The /fintech surface

Each snapshot shows its status, last-check date, source publication date when one is available, and a link to the source.

View snapshots

Published bounded content

The /updates surface

Each update shows its topic, content type, and a link to its supporting source. The Updates surface does not display a check timestamp or evidence excerpt.

View verified updates

Consulting methodology: Frame → Align → Deliver Return to Verified Updates