A calendar built on evidence, not guesses.
Tiercord's construction-event system is a purpose-built deterministic data pipeline. It does not ask an LLM to interpret, summarize or invent event facts.
The daily verification chain
- Step 1
Curate credible sources
Only first-party construction associations, safety associations and public agencies enter the registry. General event aggregators and scraped social posts are excluded.
- Step 2
Read explicit data
Adapters parse JSON-LD Event records, iCalendar, RSS/Atom, semantic time elements and Open Graph metadata. Every extracted field has a traceable rule.
- Step 3
Score professional value
An evidence hierarchy reads the event title before structured keywords, summary and description. Exact phrase rules score construction relevance, professional intent and format, while recreational, social-only, unrelated and generic office-training titles are vetoed.
- Step 4
Keep one useful record
The next date in a repeating course series is retained, then stable identifiers, title/date/location fingerprints and token similarity merge duplicates. All original source links remain attached.
- Step 5
Monitor every daily run
Run ledgers capture pages, candidates, accepted records, rejections and bounded warnings. A failed source never deletes previously published events.
What gets published
- A specific title and valid event date
- A supported province, or an online event clearly tied to one
- An official HTTPS source URL
- Event-specific evidence of professional construction value
- A canonical category, attendance format and stable fingerprint
- Only the next upcoming date from a repeated course series
What stays out
- Recreational tournaments and association social outings
- Social-only parties, appreciation events and fundraisers
- Generic office-software classes without a construction application
- Unrelated listings and generic calendar pages
- Facts, availability or promotional claims the organizer did not publish
Operational safeguards
Safe fetching
Host allowlists, HTTPS-only requests, redirect revalidation, private-network rejection, robots handling, response-size limits and timeouts.
Durable history
Every source run records counts, warnings and errors. Event provenance and subscription delivery each have their own idempotency ledger.
Failure escalation
The first degraded source creates a staff warning. Repeated failures escalate to critical, and recovery is recorded explicitly.
Subscriber privacy
Addresses are envelope-encrypted, looked up through a keyed blind index, activated only after confirmation and suppressible in one click.