A clear trail back to the source.

Jobs are metadata with a source trail.

The workspace consumes registered public-source metadata. It displays the employer, source ID, original posting, application link, location and discipline, plus known posting and check dates. We do not republish full job descriptions. No unsupported JobPosting structured data is emitted.

Coverage is explicit

Imported means a source is registered for metadata import. Directory-only means we link to the official careers page without adding job rows. Unavailable means the source could not be checked successfully; retained job metadata can still be shown with a warning. Counts are computed from valid open rows in the job dataset, never a directory entry’s reported job_count.

Dates mean different things

Posted is the employer-supplied publication date, if known. First seen is when the import first recorded the job. Last checked is the record’s source-check time. Dataset generated is when the file was assembled. These are not interchangeable. This frontend flags checks older than 72 hours as older snapshots, and missing or future timestamps as unknown or needing verification. This threshold is a UI caution, not evidence that a job is closed.

Failures and omissions

An unavailable file shows an honest fallback to official directories. A source failure does not close its vacancies. A saved ID absent from a later import is unavailable here, not necessarily closed with the employer. Imports can omit roles and employers; this site makes no worldwide-completeness or uninterrupted-refresh promise.

Intelligence and policy

Items use short attributed summaries with primary-source links, publisher, publication date, document type, and available effective-date or jurisdiction context. News, rules, proposals, and guidance stay distinct. The feed is selective; “rule” alone does not establish legal applicability. Request a correction with the record ID and source.

Registered careers sources