A worldwide directory of systems thinking, cybernetics, complexity, system dynamics, and systemic design events, maintained by Benjamin P Taylor. Inspired by Nick Ananin’s systems events map.
Public hosted edition: https://systems-events-map.redquadrant-0856.chatgpt.site
GitHub Pages edition (once enabled): https://antlerboy.github.io/systemsmap/
The hosted edition reads the daily event data and subscription feeds directly from this repository.
- Search by topic, organisation, country, date range, and attendance format.
- Explore published physical locations. Online and unknown-location events remain in the list.
- Subscribe to all events, an organisation, a subject, or online events through ICS feeds.
- Download a filtered selection or an individual event.
- Submit an event, public calendar feed, or website through the on-page form to the public GitHub review queue.
- Collect sources daily at 04:23 UTC and after changes to main. GitHub may delay scheduled runs.
- Publish source health, provenance, collection timestamps, and discovered source candidates.
Worldwide is the scope, not a completeness claim. The register includes SCiO, ISSS, CybSoc, ASC, IFSR, and Systems Innovation, plus scientific and practitioner organisations. Some sources are blocked, private, undated, or require additional parsing. The site distinguishes sources yielding events from sources merely checked. Coverage remains biased towards public structured data. Original titles and languages are retained.
City pins are approximate; unknown venues are never guessed. Dates without times are exported as date-only entries and labelled accordingly. Timed entries lacking a time zone are omitted from calendar feeds. Source errors can still propagate; follow the source links before booking. Recurring events are expanded to an 18-month horizon, preserving daylight-saving changes, exceptions, and cancellations. Missing listings are marked for rechecking, never assumed cancelled.
Subscriptions refresh when the receiving calendar app polls. Downloaded ICS files are snapshots. Calendar UIDs remain stable across title and date changes; SEQUENCE and LAST-MODIFIED track changes. Cancelled events remain marked CANCELLED. Events are retained for 90 days after their date.
The on-page form prepares a structured GitHub issue. A GitHub account is required and submission is completed on GitHub; an unsent proposal is never claimed as received. Include only public information.
The owner reviews the source, dates, time zone, access, and scope. Apply the approved label to a valid structured submission to add it automatically. Only approval by the repository owner triggers this path. Events without dates must be completed before approval. Accepted feeds and pages join the daily scan. Corrections can be supplied through issues or pull requests.
data/sources.json is the reviewed register. scripts/collect.py handles ICS (including public Google and Teamup feeds), JSON-LD events, and selected organisation-specific HTML. data/discovered-sources.json records links found on source pages for review. data/approved-events.json, when present, holds reviewed manual events. Failed sources keep their previously collected events with a warning.
The collector honours robots rules, bounds requests and concurrency, checks redirects, rejects nonpublic target addresses in production, and never executes page content. No paid search API is required.
python -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/python -m unittest discover -s tests -v
.venv/bin/python scripts/collect.py
.venv/bin/python scripts/validate.pydist is the complete static site. The workflow validates data and publishes through GitHub Pages. Initial activation may require selecting GitHub Actions under Settings → Pages. GitHub may disable scheduled workflows after prolonged repository inactivity. The interface flags collections older than two days.
Leaflet 1.9.4 is vendored with its BSD-2-Clause licence. World boundaries derive from Natural Earth public-domain data, distributed through johan/world.geo.json. Boundaries are illustrative. No advertising, analytics, or personal data storage is included. GitHub receives issue submissions. Organisers remain the authoritative sources; no endorsement is implied.